HiRDB Datareplicator enables the user to extract data automatically and incorporate it into a HiRDB database when another HiRDB database is updated. To use HiRDB Datareplicator, you specify the following operands in the HiRDB system common definitions:
- pd_rpl_init_start operand
This operand specifies whether to use the HiRDB Datareplicator linkage facility from the time of HiRDB startup.
- pd_rpl_hdepath operand
This operand specifies the name of the HiRDB Datareplicator directory where data is extracted. This directory name must be the one that has been specified in the HDEPATH environment variable for the HiRDB Datareplicator where data is extracted.
- pd_log_rpl_no_standby_file_opr operand
This operand specifies the desired operation in the event a swap request is issued while the HiRDB Datareplicator linkage facility is being used, and none of the system log files can be swapped because extraction of system log information at the HiRDB Datareplicator has not been completed.
For details about the system environment definition and how to use HiRDB Datareplicator to perform data replication, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
- Notes
- If you are using a HiRDB facility not supported by HiRDB Datareplicator, you might not be able to use the data linkage facility. For details, see the HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
- When a recovery-unnecessary front-end server is used
Because a recovery-unnecessary front-end server cannot execute import processing using the two-phase commitment method for the synchronization point processing method (enabled when fxa_sqle is specified in the import system definition commitment_method operand) of the target HiRDB Datareplicator, you need to use a front-end server other than the recovery-unnecessary front-end server. For details, see 9.1.4 Recovery-unnecessary front-end server.