HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide

[Contents][Glossary][Index][Back][Next]

6.5.7 Notes on handling when syncterm=true is specified

The following notes on Datareplicator operation apply when syncterm=true is specified in the extraction system definition.

Organization of this subsection
(1) Terminating Datareplicator before synchronized termination with HiRDB
(2) Restarting Datareplicator after synchronous termination
(3) Operation when communication has not been established with the target Datareplicator

(1) Terminating Datareplicator before synchronized termination with HiRDB

When you specify syncterm=true, Datareplicator continues processing up to the synchronization point (detection of HiRDB normal termination log) and then terminates itself automatically. If the source HiRDB is a parallel server and is terminated by a command issued by the user or due to an error before Datareplicator reaches a synchronization point, some servers might have reached the synchronization point, but some might not. If you restart data linkage by specifying syncterm=true in such a case, extraction processing might be terminated before the most recent synchronization point is reached because the synchronization point identified by each server is different. When you specify syncterm=true, you must be sure to execute Datareplicator up to the synchronization point (restart only Datareplicator and allow all servers to reach the most recent synchronization point).

(2) Restarting Datareplicator after synchronous termination

When you specify syncterm=true and Datareplicator terminates synchronously with the HiRDB, you must start HiRDB and start HiRDB Datareplicator linkage before restarting Datareplicator with the syncterm=true specification. If restarted while data linkage is inactive at the HiRDB, Datareplicator will terminate itself automatically.

(3) Operation when communication has not been established with the target Datareplicator

When you specify syncterm=true but communication has not been established with the target Datareplicator, transmission processing will not stop because it cannot send update information in the extraction information queue file to the target Datareplicator even if the HiRDB terminates normally. In such a case, when the target Datareplicator is started and communication is established, the transmission process stops automatically when it finishes sending all update information.