pdrplstop (Stop HiRDB Datareplicator linkage)

Function

The pdrplstop command stops HiRDB Datareplicator linkage.

Executor

HiRDB administrator

Format

pdrplstop [-f]

Option

Specifies that HiRDB Datareplicator linkage is to be stopped forcibly regardless of the system log extraction status. When this option is specified, the command stops HiRDB Datareplicator linkage even if there are inactive units.

Rules

  1. The pdrplstop command can be executed only while HiRDB is active.
  2. The pdrplstop command must be executed at the server machine that contains the single server or where the system manager is located.
  3. To execute the pdrplstop command, the HiRDB directory name should be set in the PDDIR environment variable. If the directory name is not set, no error message is output if a command error occurs.
  4. The pdrplstop command with no option specified terminates HiRDB Datareplicator linkage once extraction by HiRDB Datareplicator of system log information has been completed. This command results in an error if there is an inactive unit. However, if all such inactive units are one that were not started due to reduced activation, the command terminates HiRDB Datareplicator linkage on the active units. For the units that have not been started due to reduced activation, the command terminates their HiRDB Datareplicator linkage the next time the units are started and extraction of system log information is completed.
  5. If data is to be extracted from a HiRDB/Parallel Server, you can execute the pdrplstop -f command, even when other units are inactive, as long as the unit containing the system manager is active. For a unit that is inactive during execution of the pdrplstop -f command, the HiRDB Datareplicator linkage is cancelled the next time the unit is started.
  6. An error results if the pdrplstop command is entered while HiRDB Datareplicator linkage is not executing.

Notes

  1. The result of the pdrplstop command can be checked on the basis of the return code from execution of the command or by checking for error messages. The following table describes the return codes from execution of the command:
    Return codeTermination statusDescription
    0Normal termination
    • When the -f option is omitted:
      HiRDB Datareplicator linkage was stopped.
    • When the -f option is specified:
      Termination of HiRDB Datareplicator linkage was instructed.
    4Abnormal terminationThe command was unable to stop HiRDB Datareplicator linkage for one of the following reasons:
    • Some units were inactive (except ones that had not been started due to reduced activation)
    • Some log information was not extracted by HiRDB Datareplicator.
    8Abnormal terminationThe command was unable to stop HiRDB Datareplicator linkage due to an error, or the pdrplstop command was executed illegally.
  2. The pdrplstop command does not check the HiRDB server subject to HiRDB Datareplicator linkage for active transactions. Therefore, before executing the pdrplstop command, make sure that there are no active transactions.
  3. If the source database to be extracted is updated during or after execution of the pdrplstop command, inconsistency occurs in the data between the source and target databases. The same also applies if the pdrplstop -f command is executed while there are active transactions or some log information has not been extracted for the source database.
    If inconsistency occurs in the data between the source and target databases, execute the pdrplstop command to terminate HiRDB Datareplicator linkage. Use the pdls -d rpl command to make sure that HiRDB Datareplicator linkage has stopped on all units, and then re-create the target database before restarting HiRDB Datareplicator linkage. For details about re-creating the target database, see the manual HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
  4. Once you have entered the pdrplstop command, do not enter the pdrplstart, pdrplstop, or pdstop command until the pdrplstop command processing terminates.
  5. With a HiRDB/Parallel Server that consists of multiple units, normal termination of the pdrplstop -f command does not mean that HiRDB Datareplicator linkage has ended on all units. Once the pdrplstop command has terminated normally, use the pdls command (-d rpl) to make sure that HiRDB Datareplicator linkage has ended on all units.
  6. Once you have started HiRDB Datareplicator linkage, make sure that you use the pdrplstop command to stop it even if the reason for stopping the linkage is a missing database due to an error in the HiRDB system definitions.
  7. If you are executing the pdrplstop command in order to restart HiRDB Datareplicator linkage, do not update the target database while HiRDB Datareplicator linkage is stopped. If you do, conformity will be lost between the databases. However, reorganization of a database that does not accompany logical updating of data does not cause inconsistency of data between databases even if it is executed while HiRDB Datareplicator linkage is stopped.
  8. The table below describes the conditions and whether or not the pdrplstop command can be executed. If inconsistency occurs between the databases, you must re-create the target database.
    Condition during execution of the pdrplstop commandWhether or not executable
    -f not specified-f specified
    Unit containing the single server or system manager is inactiveNN
    ActiveThere is unextracted log data after command executionYIYI
    There is no unextracted log dataThere is unextracted log data at an active back-end serverNYI
    There is no unextracted log dataThere is no inactive back-end serverYY
    There are inactive back-end serversUnit contains an inactive back-end server that was not been started because of reduced activationThere is unextracted log data for the inactive back-end serverY1YI2
    There is no unextracted log dataY3Y3
    OtherThere is unextracted log data for the inactive back-end serverNYI2
    There is no unextracted log dataNY3
Legend:
Y: Can be executed without causing inconsistency.
YI: Can be executed, but inconsistency occurs.
N: Cannot be executed (inconsistency does not occur).
1 For a unit that has not been started because of reduced activation, the command ends HiRDB Datareplicator linkage the next time the unit is started and system log data has been extracted.
2 For a unit that has not been started because of reduced activation, the command ends HiRDB Datareplicator linkage the next time the unit is started without waiting for extraction of remaining system log data.
3 For a unit that has not been started because of reduced activation, the command ends HiRDB Datareplicator linkage the next time the unit is started.