2.2.34 Operands related to HiRDB Datareplicator
- 165) pd_rpl_init_start = Y | N
- Specifies whether 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.
- Notes
- When Real Time SAN Replication based on the log-only synchronous method is used, the HiRDB Datareplicator linkage facility cannot be used at the log application site. If Y is specified in this operand, the KFPS04689-W message is displayed.
- 166) pd_rpl_reflect_mode = server | uap
- This operand is applicable only to a HiRDB parallel server configuration.
- 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 9 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.
- Effects on individual estimation formulas
- If the value of the pd_rpl_reflect_mode operand is changed, the following estimation formulas are affected:
- HiRDB Version 9 Installation and Design Guide:
- Formulas for shared memory used by a unit controller under Estimating the memory size required for a HiRDB parallel server configuration
- Determining the size of system log files
- 167) 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 configuration, 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 (meaning that 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.
- 168) pd_rpl_func_control = BACKWARD_CUTOFF_UPDATE | NONE
- ~<identifier>
- Specifies the facility to be run by the source HiRDB when the HiRDB Datareplicator linkage facility is used.
- BACKWARD_CUTOFF_UPDATE:
- Performs backward cutoff/update of BLOB data and BINARY data. For details about backward cutoff/update of BLOB and BINARY data, see the HiRDB Version 9 UAP Development Guide.
- NONE:
- Does not perform backward cutoff/update of BLOB data and BINARY data.
- Specification guidelines
- BACKWARD_CUTOFF_UPDATE can be specified as follows.
pd_rpl_hdepath operand specified in unit control information definition? | Source HiRDB Datareplicator version | BACKWARD_CUTOFF_UPDATE specification |
---|
Yes | 08-01 or later | #1 |
08-00 or earlier | Not permitted#2 |
No | -- | Permitted |
Legend:
--: Not applicable
#1: See Data linkage in tables that use BLOB and BINARY types in the manual HiRDB Datareplicator Version 8 Description, User's Guide and Operator's Guide.
#2: Specify NONE for this operand.
If the conditions above are not satisfied, do not specify BACKWARD_CUTOFF_UPDATE. If it is specified anyway, the results of backward cutoff/update of BLOB and BINARY data in an extracted table in the source database will not be imported into the target database.
- If the pd_rpl_hdepath operand is specified and the version of the source Datareplicator is 08-00 or earlier, specify NONE for this operand.
- Notes
- Identifiers might be specified using either upper-case or lower-case letters.
- If an identifier is specified more than once, the result is the same as if it had been specified only once.
- If NONE is specified after BACKWARD_CUTOFF_UPDATE had been specified, check whether all the update logs were completely imported prior to the change in the specification. If the operand specification is modified while there remain update logs that have not been imported, problems might arise, such as SQL execution counts that do not match between the source and target databases.
- If NONE is specified after a stored procedure, stored function, or trigger was defined and BACKWARD_CUTOFF_UPDATE had been specified, re-create ALTER PROCEDURE, ALTER ROUTINE, or ALTER TRIGGER, respectively. If you do not, an error will result when the stored procedure, stored function, or trigger is executed. However, there is no need to re-create if no backward cutoff/update of BLOB or BINARY data had yet been performed. For details about ALTER PROCEDURE, ALTER ROUTINE, and ALTER TRIGGER, see the manual HiRDB Version 9 SQL Reference.
- If BACKWARD_CUTOFF_UPDATE is specified after a stored procedure, stored function, or trigger has been defined and NONE had been specified, re-create ALTER PROCEDURE, ALTER ROUTINE, or ALTER TRIGGER, respectively. Not re-creating will not result in an error, but backward cutoff/update of BLOB and BINARY data will not be performed.