When the Adabas commands are replicated, non-zero Adabas response codes can occur on the target database. Some of them can be handled by the replication database itself and do not need any intervention, whereas others will require the intervention of the DBA.
In order to avoid a timeout in the target database it is useful to define large timeout values in the target database. The replicator database provides such an OP command for the target database. It is also important that the WORK for the target database is large enough so that no WORK overflow is caused by the replication.
Initially,the replication nucleus tries to repeat the transaction.
If the response code 9 still occurs, the replication nucleus writes an appropriate message to its nucleus log and sets the replication exit status to recording. Then the DBA can act on the basis of what caused the error, for example, he can increase the WORK size of the target database and then reset the status to active using the Replication Administration tool.
Response code 148 (Adabas nucleus not active) indicates that the target database is not available. An appropriate error message is printed in the replicator nucleus log, and the target database is polled with OP commands by the replicator until it is available again. Then the current transaction is restarted.
Response code 149 indicates a communication error.
Response code 224 indicates a command timeout by Net-Work.
An appropriate error message is printed in the replicator nucleus log, and an OP command is issued for the target database. Then the current transaction is restarted. If the error occurs again, the status of the replication is set to recording.
There are several response codes that can occur when the target database is available, but it does not make sense to continue the replication because interaction by the DBA is required. For these response codes, a BT and CL command are issued by the replication database and the status is changed to recording. The response codes concerned are listed below:
47 - Maximum for NISNHQ parameter exceeded
48 - Requested database operation not allowed
49 - Compressed record too long for DATA container
72 - User queue overflow
77 - No space available in database container
79 - Hyperexit not available
114 - File refresh via E1 failed
162 - Buffer pool overflow
245 - Pending utility entries in UCB
255 - Client-server communication error
After the problems have been resolved, the DBA should reset the status to active again.
Other Adabas response codes will result in setting the replication status to error (together with an appropriate error message in the nucleus log). For the target database the replicator issues a BT and a CL command.
It is the responsibility of the DBA to solve the problem and then execute another “initial state processing”.
