2.3.28 Operands related to HiRDB Datareplicator

142) pd_rpl_init_start = Y | N
Specifies whether or not the HiRDB Datareplicator linkage facility is to be used from the time of HiRDB startup.
Y: Use the HiRDB Datareplicator linkage facility from the time of HiRDB startup.
N: Do not use the HiRDB Datareplicator linkage facility from the time of HiRDB startup.
Operation method
  • When N is specified for this operand, the HiRDB Datareplicator linkage facility can be used by entering the pdrplstart command.
  • The pdrplstop command is entered to stop the HiRDB Datareplicator linkage facility.
  • When data linkage has been stopped by entering the pdrplstop command, HiRDB Datareplicator linkage can be restarted by entering the pdrplstart command. However, before the pdrplstart command is entered, the target database must be re-created based on the extracted database.
143) pd_rpl_reflect_mode = server | uap
This operand is applicable to a HiRDB/Parallel Server.
Specifies uap in order to use HiRDB Datareplicator's target transaction synchronization facility. If you do not use the target transaction synchronization facility, there is no need to specify this operand. For details about the target transaction synchronization facility, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
server: Incorporates transactions for each HiRDB server.
uap: Incorporates transactions for each UAP.
Condition
When you specify this operand, you must also specify the pd_rpl_hdepath operand. If the pd_rpl_hdepath operand is omitted, this operand is ignored.
Notes
When uap is specified, the amount of update log information increases. In such a case, refer to the HiRDB Version 8 Installation and Design Guide and re-estimate the total size of the system log files.
Relationship to other operands
If you specify uap in this operand, re-estimate the value of the pd_log_max_data_size operand.
144) pd_log_rpl_no_standby_file_opr = stop | continue
Specifies the action to be taken when a swap request is received when not all of the system log files can be created at the swapping destination because system log extraction by HiRDB Datareplicator using the HiRDB Datareplicator linkage facility has not been completed.
stop: Stop the HiRDB unit forcibly.
continue: Stop HiRDB Datareplicator linkage and continue operation with HiRDB only.
Condition
Specification of this operand is valid only if Y is specified for the pd_rpl_init_start operand or if the pdrplstart command has been entered and the HiRDB Datareplicator linkage facility is being used. In the case of a HiRDB/Parallel Server, this operand is not valid for front-end servers and dictionary servers.
Notes
  • When stop (the default value) is specified for this operand and the HiRDB unit is terminated forcibly, the HiRDB unit must be restarted after it has been confirmed that the log file being extracted on the HiRDB Datareplicator side has moved to another file (i.e., at least one file has been extracted completely). Even if the HiRDB unit is restarted immediately after the forced termination, HiRDB will recognize the abnormal status and forcibly terminate the HiRDB unit again if there is no swap target file.
  • When continue is specified for this operand and HiRDB Datareplicator linkage is stopped, a mismatch will occur between the extracted database and the target database on the HiRDB Datareplicator side. Therefore, it is necessary to re-create the target database.