The pdorbegin command places specified original RDAREAs and replica RDAREAs of a specified generation in the replica group in online reorganization hold status.
When a table is specified, the command processes all RDAREAs related to that table and places each original RDAREA and the specified generation of replica RDAREAs in the replica group in online reorganization hold status. For details about related RDAREAs, see 2.98 pdrdrefls (Display information about related RDAREAs). To also process the related areas in the constraint definition, specify the -c option. For details, see the description of the -c option.
Once you execute the pdorbegin command, any transaction that accesses an RDAREA in the replica group that contains the specified original RDAREA is placed in wait status until the pdorchg command has executed.
To release online reorganization hold status, specify the -u option.
You can execute the pdorbegin command only when HiRDB Staticizer Option has been installed and the pd_max_reflect_process_count and pd_inner_replica_control operands have both been specified in the system definition.
HiRDB administrator
pdorbegin {-r original-RDAREA-name[,original-RDAREA-name]... |
pdorbegin {-r original-RDAREA-name[,original-RDAREA-name]... |
Specifies the names of RDAREAs that are to be placed in online reorganization hold status.
~<identifier> ((authorization identifier: 1-30, table identifier: 1-30))
Specifies the name of a table that is to be placed in online reorganization hold status.
The command processes the RDAREAs related to the specified table and places each original RDAREA and the specified generation of replica RDAREAs in the replica group in online reorganization hold status.
Authorization identifier in the -t option | PDUSER environment variable setting | Authorization identifier that takes effect |
---|---|---|
Specified | -- | Authorization identifier specified in the -t option |
Omitted | authorization-identifier[/password] | Authorization identifier specified in the PDUSER environment variable |
Not specified | User name specified in the login window | |
Simple authentication keywords were specified in both the authorization identifier and the password |
Specifies servers for which the processing is to be performed. The following guidelines apply to specifying the -s option:
Specifies the generation number of the replica RDAREAs in the replica group that are to be placed in online reorganization hold status.
You cannot specify 0, which is the generation number of original RDAREAs.
Specifies the lock-release wait time in seconds for the online reorganization hold.
When this option is omitted, the command assumes the value of the pd_lck_wait_timeout operand in the system definition. If the value of the pd_lck_wait_timeout operand is 0 in the system definition, the command assumes 3,600.
Specifies that online reorganization hold is to be released. When this option is specified, the -r and -t options must also be specified.
When the processing target includes a shared RDAREA, processing is performed at all back-end servers in the batch mode. If it is not possible to release all the target RDAREAs from online reorganization hold status, an error results. If the shared RDAREA needs to be released from online reorganization hold status for each server for reasons such as a specific back-end server being inactive, you can specify the -s option to release the online reorganization hold.
When you release online reorganization hold, you must specify the same resources as when the processing target was placed in online reorganization hold status (otherwise, an error occurs). The following table shows the relationships between the options specified when the processing target was placed in online reorganization hold status and the options that are specified when it is released from online reorganization hold status:
pdorbegin command options when online reorganization hold is released | pdorbegin command options when the processing target was placed in online reorganization hold status | ||
---|---|---|---|
-r RDAREA | -t table | -t table -c ref | |
-r RDAREA -u | Y# | N | N |
-t table -u | N | Y | N |
-t table -c ref | N | N | Y |
Specifies that the associated RDAREAs in the constraint definition are also to be placed in online reorganization hold status. When you specify this option, you must also specify the -t option. Specifying this option without specifying the -t option results in an error.
Specifies that only the updated columns are to be applied during reflection processing for online reorganization when the pdorend command is executed. For notes about the -e option specification, see the manual HiRDB Version 9 Staticizer Option Description and User's Guide.
Specifies (in minutes) the monitoring interval when the execution time of the pdorbegin command is to be monitored. For guidelines on the value to specify and details about the resulting operation, see the description of the pd_cmd_exec_time operand in the system common definition in the manual HiRDB Version 9 System Definition.
When 0 is specified in this option, the command's execution time is not monitored.
When this option is omitted, the value of the pd_cmd_exec_time operand in the system common definition takes effect.
Processing target | Option | Whether or not executable | Execution range | Command execution format | |||||
---|---|---|---|---|---|---|---|---|---|
-t | -r | -s | -u | -c | |||||
Table | Non-partitioned table (including shared tables for a HiRDB single server configuration) | S | -- | -- | -- | -- | Y | All related RDAREAs#2 | Format 1 |
S | -- | -- | S | -- | Y | ||||
S | -- | S | -- | -- | Y#1 | RDAREAs related to the specified back-end server#2 | |||
S | -- | S | S | -- | Y#1 | ||||
S | -- | -- | -- | S | Y | All related RDAREAs#3 | |||
S | -- | -- | S | S | Y | ||||
S | -- | S | -- | S | Y#1 | All RDAREAs related to the specified back-end server#3 | |||
S | -- | S | S | S | Y#1 | ||||
Row-partitioned table | S | -- | -- | -- | -- | Y | All related RDAREAs#2 | ||
S | -- | -- | S | -- | Y | ||||
S | -- | S | -- | -- | Y#1 | RDAREAs related to the specified back-end server#2 | |||
S | -- | S | S | -- | Y#1 | ||||
S | -- | -- | -- | S | Y | All related RDAREAs#3 | |||
S | -- | -- | S | S | Y | ||||
S | -- | S | -- | S | Y#1 | All RDAREAs related to the specified back-end server#3 | |||
S | -- | S | S | S | Y#1 | ||||
Shared table (applicable to a HiRDB parallel server configuration only) | S | -- | -- | -- | -- | Y | RDAREAs related to all back-end servers#2 | ||
S | -- | -- | S | -- | Y | Format 2 | |||
S | -- | S | -- | -- | N | Not applicable | Format 1 | ||
S | -- | S | S | -- | Y | RDAREAs related to the specified back-end server#2 | Format 2 | ||
S | -- | -- | -- | S | Y | RDAREAs related to all back-end servers#3 | Format 1 | ||
S | -- | -- | S | S | Y | Format 2 | |||
S | -- | S | -- | S | N | Not applicable | Format 1 | ||
S | -- | S | S | S | Y | RDAREAs related to the specified back-end server#3 | Format 2 | ||
RDAREA | Non-shared RDAREA only | -- | S | -- | -- | -- | Y | Only the specified RDAREAs | Format 1 |
-- | S | -- | S | -- | Y | ||||
-- | S | S | -- | -- | N | Not applicable | |||
-- | S | S | S | -- | N | ||||
-- | S | -- | -- | S | N | ||||
Shared RDAREA only | -- | S | -- | -- | -- | Y | All back-end servers | ||
-- | S | -- | S | -- | Y | Format 2 | |||
-- | S | S | -- | -- | N | Not applicable | Format 1 | ||
-- | S | S | S | -- | Y | Specified back-end servers | Format 2 | ||
-- | S | -- | -- | S | N | Not applicable | Format 1 | ||
Both non-shared and shared RDAREAs | -- | S | -- | -- | -- | Y | All back-end servers | ||
-- | S | -- | S | -- | Y | Format 2 | |||
-- | S | S | -- | -- | N | Not applicable | Format 1 | ||
-- | S | S | S | -- | N | Format 2 | |||
-- | S | -- | -- | S | N | Format 1 |