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

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

3.7.7 Error handling

The following table lists the errors that might occur while you are using the import transaction synchronization facility and describes the action to be taken for each error.

Table 3-23 Error handling when the import transaction synchronization facility is used

Error Action
Synchronization was not achieved because the hdeevent command was not executed, resulting in the extraction information queue file or import information queue file becoming full. Disable the synchronous import group.
The extraction information queue file has become full for a reason such as a large transaction. Use the data linkage recovery facility to recover data.
Update information and synchronous events for some of the data linkage identifiers were lost for a reason such as a disk failure. Use the data linkage recovery facility to recover data.
A synchronous event for some back-end servers cannot be received due to a communication failure. Wait until the communication failure is recovered, and then receive the remainder.
A synchronous event cannot be received because the import information queue file is full. Disable the synchronous import group, restart the target system, and create free space in the import information queue file. When all log information has been imported, re-create the synchronous import group.
Import processing cannot be performed due to a shortage of resources in the target database or due to a timeout. Take one of the following actions:
  • Change the database settings, and then re-execute.
  • Disable the synchronous import group, restart the target system, and create free space in the import information queue file. When all log information has been imported, re-create the synchronous import group.
Synchronization cannot be achieved due to an import error on at least one of the data linkage identifiers (such as an SQL error). Take one of the following actions:
  • Eliminate the cause of the error, and then re-execute.
  • Skip the erroneous update information by using import suppression or the skip_sqlcode operand in the import environment definition.
A synchronous event or a sequence was lost. Disable the synchronous import group.
Note
If you use the error recovery facility in the source system, the import transaction synchronization facility cannot be used because the transaction branch information is not extracted. To recover an error, either delete the synchronous import group definition or start the system while the synchronous import group is disabled.