The table below shows the combinations of the versions and products that support data linkage recovery via unload log files. For a product whose source system is not Datareplicator, see the applicable product documentation.

Table 9-10 Combinations of the versions and products that support data linkage recovery via unload log files

Target system		Source system
		Datareplicator
		06-01 or earlier	06-01-/A or later#
Datareplicator	04-00-/O or later	N	Y
	05-03-/D or later	N	Y
	06-01-/A or later#	N	Y
	07-00 or later and 08-00 or later	N	Y
	Other	N	N
XDM/DS	08-00-A	N	Y
	08-02 or later	N	Y
	Other	N	N

Y: Supports data linkage recovery via unload log files.

N: Does not support data linkage recovery via unload log files.

#

When the target of the logmrg command is a HiRDB large file, HiRDB Datareplicator version 06-02 or later supports data linkage recovery via unload log files.

Because data linkage recovery requires use of HiRDB's unload log files, all unload log files containing log information to be restored must be available.

The following table describes the causes of nonconforming data linkage and for each the applicability of data linkage recovery via unload log files (source system).

Table 9-11 Causes of nonconforming data linkage and applicability of data linkage recovery via unload log files (source system)

Product	Cause of nonconforming data linkage			Applicability	Recovery range
Source Datareplicator	Operation error	Linkage stop instruction (definition change)	pd_rpl_init_start operand value was changed from Y to N.	Applicable	All BESs
			pd_rpl_hdepath operand was disabled.	Not applicable#	--
			System log file became full while the pd_log_rpl_no_standby_file_opr operand was set to continue.	Applicable	All BESs in the unit that contains the BES in which the system log file became full
		Linkage stop instruction (wrong command input interval)	pdrplstop command was executed.	Applicable	All BESs
			pdlogchg -R command was executed.	Applicable	BES on which the command was executed
		Source Datareplicator was initialized		Applicable	All BESs
		Queue file became full due to execution of a large transaction.		Application not required (can be recovered by adding a queue)	--
		Source table definition was changed (DROP or CREATE TABLE). After execution, the extraction definition preprocess was not executed.		Not applicable#	--
		Database was updated in the no-log mode.		Not applicable#	--
	Error	Hardware	Disk error occurred on a file, such as a queue file.	Applicable	BES where the error occurred
		Software	Process was terminated.	Application not required (can be recovered by re-run)	BES where the process was terminated

#

You must use HiRDB Dataextractor or XDM/XT for recovery.

The following table describes the causes of nonconforming data linkage and for each the applicability of data linkage recovery via unload log files (target system).

Table 9-12 Causes of nonconforming data linkage and applicability of data linkage recovery via unload log files (target system)

Product	Cause of nonconforming data linkage			Applicability	Recovery range
Target Datareplicator	Operation error	Target Datareplicator was initialized.		Applicable	Corresponding BES
		Queue file became full due to execution of a large transaction.		Application not required (can be recovered when a queue is added by initialization)	--
	Error	Hardware	Disk error occurred on a file, such as a queue file.	Applicable	Corresponding BES
		Software	Process was terminated.	Application not required (can be recovered by re-run)	BES where the process was terminated
Target XDM/DS	Operation error	Target XDM/DS was initialized.		Applicable	Corresponding BES
		Queue file became full due to execution of a large transaction.		Application not required (can be recovered by adding a data set)	--
	Error	Hardware	Disk error occurred on a file, such as a queue file.	Applicable	Corresponding BES
		Software	Process was terminated.	Application not required (can be recovered by re-run)	--

This subsection describes limitations when data linkage recovery via unload log files is applied.

• Limitations to transactions
  If an unload log file specified as input for the data linkage recovery facility is missing any part of a transaction subject to recovery, that transaction is not recovered. If the start or end of a transaction subject to recovery is missing from the input unload log files, a warning file (named resfile_BES) is output during recovery processing. When such a warning file is output, check its contents and add the appropriate input unload files, if necessary (for details, see 9.6.3 (2) Preparing the unload log files).
  If a range in which data linkage was cancelled on the HiRDB system is excluded from the recovery, a transaction that spans that range is not recovered.
  
• Limitations to the import method at the target
  If either of the following conditions is satisfied, data linkage recovery via unload log files cannot be used, in which case you must use HiRDB Dataextractor or XDM/XT for recovery:
  - The mapping key is updated.
  - The table-based import method is used for import processing. This is not applicable to a version that supports the import-suppress facility in the target system. For details about the import-suppress facility, see 9.6.8 How to suppress import when the table-based import method is used for import processing at the target system.
  
• Limitations to uninstallation
  If you uninstall Datareplicator while the facility for performing data linkage recovery via unload log files has been set up, you will not be able to set up the data linkage recovery facility when Datareplicator is re-installed. When you uninstall Datareplicator, make sure that any setup of the facility for performing data linkage recovery via unload log files has been cancelled.
  

• If the mapping key has been updated and a COMMIT error or a system error occurs during the target Datareplicator's last import processing, the first transaction to be recovered might result in an SQL error (SQLCODE is 100 or -803).
  If this occurs, you can continue the processing by using the skip_sqlcode operand in the import environment definition. However, you must remember to delete this operand promptly after recovery processing has been completed.
  
• If commitment_method = fxa_sqle is specified in the import system definition and the target Datareplicator terminates with an error or is terminated forcibly by hdsstop -t force, an undetermined transaction might remain in HiRDB. Use HiRDB's pdrbk command to determine the transaction, and then perform recovery processing.