The pdorchg command switches current RDAREAs from original RDAREAs in online reorganization hold status (including RDAREAs that have been placed temporarily in command shutdown status) to replica RDAREAs in online reorganization hold status.

After the pdorchg command is completed, a transaction that was accessing an original RDAREA in online reorganization hold status is released from wait status so that it can access the replica RDAREA in online reorganization hold status.

You can execute the pdorchg 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

pdorchg [-s server-name[,server-name]...][-W execution-monitoring-interval]

(a) -s server-name[,server-name]... ~<identifier> ((1-8))

Specifies the names of the servers that contain replica groups where update processing on the replica RDAREAs is to be applied to the original RDAREAs.

Rules

1. If the -s option is omitted, the command switches the current RDAREAs for all servers that contain RDAREAs in online reorganization hold status.
2. If a duplicate server name is specified, the command eliminates it from processing.
3. You can specify a maximum of 128 server names. If you specify more than 128 server names, the command ignores any excess server names.
4. If you specify in the -t option of the pdorbegin command a table whose rows are partitioned among servers in order to place the table in online reorganization hold status, processing is performed at all applicable servers in the batch mode. Therefore, specify the -s option only when you want to limit the servers on which current swap processing is to be performed.
5. When the processing target includes a shared RDAREA, processing is performed at all back-end servers in the batch mode. Therefore, if the -s option is specified, an error occurs.
6. When both the following conditions are satisfied, execute the pdorchg command with the -s option specified. If the command is executed with the -s option omitted, an error results.
   
   • The pdorbegin command with the -t option specified has been executed (except when a shared table is specified).
   • Some HiRDB units or servers are stopped or stopping.

(b) -W execution-monitoring-interval ~<unsigned integer> ((0 to 3600))

Specifies (in minutes) the monitoring interval when the execution time of the pdorchg 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.

If 0 is specified in this option, the command's execution time is not monitored.

If this option is omitted, the value of the pd_cmd_exec_time operand in the system common definition takes effect.

1. The pdorchg command can be executed only while HiRDB is active.
2. The pdorchg command must be executed at the server machine that contains the single server or where the system manager is located.
3. When you execute the pdorchg command, the data dictionary RDAREA must be in one of the following statuses:
   
   • Open and shutdown release status
   • Open and command shutdown status
4. The unit of processing for the pdorchg command depends on whether RDAREA or table is specified in the pdorbegin command.
   

   When RDAREA is specified:

   The command performs processing for each server. If the command is unable to switch the current RDAREAs from all original RDAREAs in online reorganization hold status to replica RDAREAs in online reorganization hold status at a server, processing for that server results in an error, and the command processes the next server.

   When table is specified:

   The command performs processing for all RDAREAs related to the specified table in the batch mode. If the command is unable to switch the current RDAREAs from all original RDAREAs in online reorganization hold status to replica RDAREAs in online reorganization hold status, an error results.

5. Whether or not the pdorchg command can be executed depends on the status of the RDAREAs. For details, see C.1 RDAREA status transitions.
6. When the processing target includes a shared RDAREA, all back-end servers are processed. If the command is unable to switch the current RDAREAs from all the applicable original RDAREAs in online reorganization hold status to replica RDAREAs, an error occurs.

1. The result of the pdorchg command can be checked with the pdls -d org command or on the basis of the return code. The return codes are as follows:
   0: Normal termination
   4: Warning termination (processing was successful at some servers)
   8: Abnormal termination
   12: Abnormal termination (an event occurred that prevented the command from displaying an error message)
   If the return code is 12, check the error message in the syslogfile at the host where the single server or dictionary server is located, eliminate the cause of the error, and then re-execute the command. If no error message has been output to the syslogfile, contact the customer engineer.
   
2. Execute the pdorchg command after paired volumes are released.