2.99 pdrels (Release RDAREAs from shutdown status)

Organization of this section
(1) Function
(2) Executor
(3) Format
(4) Options
(5) Rules
(6) Notes

(1) Function

The pdrels command releases specified RDAREAs from shutdown status.

(2) Executor

HiRDB administrator

(3) Format

pdrels -r {RDAREA-name[,RDAREA-name]...|ALL} [-q generation-number] [-o][-W execution-monitoring-interval]

(4) Options

(a) -r {RDAREA-name[,RDAREA-name]...|ALL}
-r RDAREA-name ~<identifier> ((1-30))
Specifies the name of an RDAREA that is to be released from shutdown status.
ALL
Specifies that all RDAREAs are to be released from shutdown status, except the master directory RDAREA. When the -q option is specified, the command processes RDAREAs of the same generation.
Rules
  1. The master directory RDAREA cannot be specified.
  2. When a user RDAREA or user LOB RDAREA is specified, the corresponding data dictionary RDAREA must be in one of the following statuses:
    • Open and shutdown release status
    • Open and shutdown status placed by the pdhold command
  3. If you are using the inner replica facility, you can also specify original and replica RDAREA names. In this case, you can specify only user RDAREAs and user LOB RDAREAs.
(b) -q generation-number ~<unsigned integer> ((0-10))

Specifies the generation number of a replica RDAREA.

When you specify this option, specify the original RDAREA name in the -r option. An error results if all the replicas of the specified original RDAREA have been deleted, or if a normal RDAREA (that has no replica RDAREA) is specified.

(c) -o

Specifies that the RDAREA is to be opened after being released from shutdown status. When this specification is omitted, the RDAREA is only released from shutdown status.

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

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

(5) Rules

  1. The pdrels command can be executed only while HiRDB is active.
  2. The pdrels command must be executed at the server machine containing the single server or the server machine where the system manager is located.
  3. The pdrels command locks each specified RDAREA in the PR mode (except when the updatable backup-hold status is released). If another updating transaction is accessing a specified RDAREA, the pdrels command goes onto wait status until the other transaction terminates.
  4. If an RDAREA is placed in synchronization shutdown status, its data becomes inconsistent because the update buffer is discarded, and inconsistent information is written in the RDAREA. If an RDAREA is placed in synchronization shutdown status, you must write consistent data from the applicable replica RDAREA to this RDAREA in synchronization shutdown status. An RDAREA containing inconsistent information cannot be released from shutdown status.
  5. If the pdrels command is executed on a shared RDAREA, all back-end servers are locked. If there can be multiple concurrent accesses to the corresponding RDAREA, global deadlock may occur, resulting in a timeout. If global deadlock has occurred, re-execute the pdrels command.

(6) Notes

  1. The result of the pdrels command can be checked by the pddbls command.
  2. If the contents of the update buffer take effect on the RDAREA on updatable backup-hold (WAIT mode), the command issues a warning message (KFPH00157-W) when releasing the RDAREA from shutdown status.
  3. The following shows the pdrels command's return code:
    0
    Normal termination
    1
    Warning termination
    The contents of the update buffer took effect on the RDAREA on updatable backup-hold (WAIT mode). Shutdown release processing terminated normally.
    4
    Warning termination
    At least one of the specified RDAREAs resulted in an error.
    8
    Abnormal termination
    12
    Abnormal termination
    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.
  4. This command cannot release an RDAREA from error shutdown status unless you recover the RDAREA, nor can it release an RDAREA from synchronization shutdown status unless you replace its data. However, you can release an RDAREA from shutdown status if the status was caused by an input or output error during a read or write operation or by a UAP or utility in the no-log mode.
  5. This command cannot release from command shutdown status an RDAREA that contains a falsification prevented table and is in reload-not-completed data status. When you execute table reloading with pdrorg on such a falsification prevented table, the reload-not-completed data status is released. After that, release the RDAREA from shutdown status.
  6. The pdrels command cannot release an RDAREA from online reorganization hold status.
  7. If hybrid is selected as the processing method for Real Time SAN Replication, executing the pdrels command to release RDAREAs from error shutdown status results in a database synchronization wait for the remote site. This may result in an overhead of 2 seconds or more for each RDAREA specified in the -r option. If the database synchronization wait for the remote site fails, you must recover the remote site's database. For details about the error handling when Real Time SAN Replication is used, see the manual HiRDB Version 9 Disaster Recovery System Configuration and Operation Guide.