If your connection terminates and tries to connect repeatedly, the cause may be a log record that cannot replicate. Such a record causes Replication Agent to terminate, reconnect, and go to the queue ID specified by Replication Server that precedes the log record it cannot replicate. Replication Agent terminates the connection and begins again.
To correct this problem, find the name of the table encountering the error by examining the Replication Server or Replication Agent error log. Then, choose one of the following courses of action, depending on the circumstances of the failure.
Message LEX0025 is normal upon starting Replication Agent.
If message LEX 0025 displays on the console repeatedly
Shut down Replication Agent.
Determine whether open transactions still exist in the stable queue by issuing the admin who, sqt command.
If open transactions exist in the stable queue, contact your Replication Server Administrator for advice, and use either sysadmin purge_all_open or sysadmin purge_first_open.
Use the Replication Server documentation to solve stable
queue problems. This does not imply that this is the only circumstance
under which open transactions can exist in the stable queue.
If open transactions do not exist in the stable queue, prevent replication on the table in error.
For the column in the LTMOBJECTS system table representing the table containing the error, insert a value of 20 in the ERROR_CODE column.
You can edit and run the sample SQL in the SETREPERR member of the hlq.DOCS data set to make this change in your LTMOBJECTS system table. (See “Understanding and using the LTMOBJECTS table” for details.)
Rematerialize the table that contained the error.
Restart replication on the table that contained the error by resetting the ERROR_CODE column value to 0 (zero).
Start Replication Agent.
Replication Server Commands Reference for information about Replication Server commands
If message LEX 0025 does not display on the console
repeatedly
Stop replication on the primary DB2 table encountering the error by inserting a value of 20 in the ERROR_CODE column for that table in LTMOBJECTS.
Start Replication Agent and let it read past the log record that it cannot replicate.
Resynchronize the primary and replicate tables either by issuing individual updates, inserts, or deletes or by rematerializing the affected table.
Start replication on the primary DB2 table by selecting option 1 from the Activate and Deactivate Replication panel.
