The table below shows the possible causes of errors in the source system and the handling methods for such errors. If an inconsistency has occurred between the source and target databases due to an error, the source and target Datareplicators must be initialized. For details about the initialization procedure, see 9.4 Initialization procedure during error recovery.

Table 9-1 Causes of errors and handling methods

Cause of error		Error handling method
Memory shortage (local memory)		Terminate any unneeded processes. Increase the memory size.
Memory shortage (shared memory)		Terminate any unneeded processes that use the shared memory. Increase the memory size.
Shortage of file descriptors		Close any unneeded files. Modify the system parameters (maximum number of file descriptors).
Socket establishment failure		Eliminate the cause of the error on the basis of the detail code from the system call.
Port check error		Eliminate the cause of the error on the basis of the detail code.
Communication line failure		Reconnect the communication line.
Insufficient file space	Extraction information queue file	Send all update information from the extraction information queue file to the target system, and then terminate the source Datareplicator with the hdestop command. Increase the number of files or the file size, initialize the files with the hdestart -i command, then restart Datareplicator with the hdestart command. For details, take the appropriate action from the flowchart Handling procedure when the extraction information queue file is full.
	Status file during extraction processing	Send all update information from the extraction information queue file to the target system, and then terminate the source Datareplicator with the hdestop command. Increase the file size, initialize the file with the hdestart -i command, then restart Datareplicator with the hdestart command.
Invalid medium	Extraction information queue file	If an error occurred in the extraction information queue file only: Eliminate the cause of the error, and then recover the extraction information queue file by using the facility for recovering the extraction information queue file. For details about the facility for recovering the extraction information queue file, see 9.7 Facility for recovering the extraction information queue file. If an error occurred in another file in addition to the extraction information queue file: Eliminate the cause of the error, synchronize the data linkage environments at the source and target, initialize them, then re-create the target database on the basis of the source database.
	Status file during extraction processing	Eliminate the cause of the error, synchronize the data linkage environments at the source and target, initialize them, then re-create the target database on the basis of the source database.
	Data linkage file
	System log file#
	Source database	Use the database recovery utility (pdrstr) to restore the database from its backup copy and the log acquired since the backup was made. If you use any other method to restore the database, synchronize the data linkage environments at the source and target, initialize them, then re-create the target database on the basis of the source database.
Extraction information queue file full		Use the hdestate command to check the status of the transmission process. If it is not running normally, eliminate the cause of the error, then restart the transmission process. To cancel data linkage, such as when you cannot correct the transmission process error, execute forced termination of the source Datareplicator. Then, synchronize the data linkage environments at the source and target, initialize them, and re-create the target database on the basis of the source database For details, take the appropriate action from the flowchart Handling procedure when the extraction information queue file is full. For details about how to handle errors caused by destinations that have become subject to reduced operation because the extraction information queue file became full, see 9.1.4 Procedures for handling errors at the target system.
Invalid update information		Save the status file and extraction information queue file obtained immediately after the invalid update information error occurred, then contact the customer support center. Eliminate the cause of the error, synchronize the data linkage environments at the source and target, initialize them, then re-create the target database on the basis of the source database
Invalid definition information		Correct the definitions for the source system or the source Datareplicator.
SQL error		Eliminate the cause of the error on the basis of the SQLCODE.
Internal conflict		Contact the customer support center.
Machine power interrupt		Restart the machine.
Bus error		Contact the customer support center.
Invalid signal reception (sigkill)		UNIX edition of Datareplicator: If the source Datareplicator received an invalid signal, execute the hdeshmclean command and restart the machine. If the target Datareplicator received an invalid signal, execute the hdsshmclean command and restart the machine. Windows edition of Datareplicator: Restart the machine.

#: If you are using dual system log files, this applies when errors occur in both editions.

Handling procedure when the extraction information queue file is full:

An error message is displayed when the extraction information queue file becomes full. The message that is displayed depends on the process that issues the message, as follows:

• Extraction node master: KFRB00042-E
• Extraction master: KFRB00701-E

The following figure shows the handling procedure when these messages are displayed:

#1

Execute the hdestate command to determine whether transmission processing is underway.

#2

If necessary, eliminate the cause of the termination and use the hdestart -s command to start transmission processing.

#3

From the execution results of the hdestate command, determine how many extraction information queue files have been allocated.

#4

Make a backup in case a registration error occurs in the additional extraction information queue file. For details about the backup method, see 6.4.2(7)(b) Backing up the extraction server status file.

#5

You can register additional extraction information queue files with the hdemodq command. For details about the hdemodq command, see 6.4.2 (6) (b) Command for changing the organization of extraction information queue files (hdemodq command) or the hdemodq command in Chapter 7. Command Syntax.

#6

After the time needed to read the entire extraction information queue files has elapsed (about 1 second per megabyte), execute the hdestate command at each transmission interval (1 minute if the specified value is 0) to check the processing status on the extraction information queue files. If Queue read position indicates the extraction information queue file that follows Queue write position, the full status has not been resolved, in which case add an extraction information queue file.

#7

After the transmission interval has elapsed (1 minute if the specified value is 0), execute the hdestate command at each transmission interval to check the processing status on the extraction information queue. If Queue read position indicates the extraction information queue file that follows Queue write position, the full status has not been resolved, in which case add an extraction information queue file.