![[Contents]](FIGURE/CONTENT.GIF)
HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Processing at the source HiRDB and source Datareplicator depends on the specification of extsuppress in the extraction environment definition. The following table shows the processing at the source HiRDB and source Datareplicator depending on the specification of extsuppress in the extraction environment definition.
Table 6-7 Processing at the source HiRDB and source Datareplicator depending on the specification of extsuppress in the extraction environment definition
| Type of HiRDB server | Specification at the source Datareplicator | Processing at the source HiRDB | Processing after starting the source Datareplicator | |
|---|---|---|---|---|
| extsuppress in the extraction environment definition | Specification in the extraction definition | |||
| MGR FES DS | N/A | N/A | N/A | N/A |
| BES SDS | true | Subject to extraction | Does not specify the extraction status. | Stops processing at this server after issuing a message indicating inconsistent definition. See (1) Handling procedure when true is specified, but the definition to extract the table is to be changed. |
| Not subject to extraction | N/A | Stops processing at this server after issuing a message indicating that the table is not subject to extraction processing. | ||
| false | Subject to extraction | Specifies the extraction status. | Starts data linkage processing. | |
| Not subject to extraction |
|
Stops processing at this server after issuing a message indicating that the table subject to extraction processing is not found. See (2) Notes on a server that contains no table subject to extraction when false is specified. | ||
MGR: System manager
FES: Front-end server
DS: Dictionary server
BES: Back-end server
SDS: Single server
N/A: Not applicable
Subject to extraction: When the corresponding server contains the table specified as being subject to extraction in the extraction definition
Not subject to extraction: When the corresponding server does not contain the table specified as being subject to extraction in the extraction definition
When true is specified and the source Datareplicator processing has stopped due to inconsistent definition, and you want to change the definition to extract the table, modify the extraction environment definition, re-initialize the source Datareplicator (by executing the hdestart -i command), and then start the source Datareplicator.
If you start HiRDB Datareplicator linkage at the source HiRDB before re-initializing the source Datareplicator, conformity between the source and target databases is lost. In such a case, cancel HiRDB Datareplicator linkage, re-create# the target database on the basis of the source database, and then re-initialize the source Datareplicator.
If you specify false and keep executing the HiRDB Datareplicator linkage facility without starting the source Datareplicator after its initialization, the system log file might become full even at a server that contains no table subject to extraction processing. Therefore, when you start HiRDB Datareplicator linkage, be sure to also start the source Datareplicator.
If the system log file becomes full at a server that contains no table subject to extraction processing, the action to be taken by the user depends on the specification of pd_log_rpl_no_standby_file_opr in the system common definition, as shown below:
All rights reserved. Copyright (C) 2007, 2013, Hitachi, Ltd.