If replication stops on a table incorrectly, make sure that you do not drop and re-create the table while Replication Agent is running. Replication Extract uses the OBID of the table when it scans the log for items to replicate. This OBID can change when a table is dropped and re-created, and replication ceases.
To avoid dropping and re-creating tables during
replication
Allow Replication Agent to complete processing log records for the table containing the replication error.
Stop Replication Agent before dropping and re-creating primary tables.
To correct errors caused by dropping and re-creating
tables
Use either of the following procedures:
Stop and restart Replication Agent.
Use the Replication Agent interface panels to delete the table name from LTMOBJECTS; then replace the table name.
Either of these procedures cause Replication Extract to associate the new OBID with the table to replicate.
WARNING! Missed transactions can occur during the time the OBID is not recognized, so you may need to rematerialize the table.
