Updates to rs_lastcommit fail

When replicating into a non-Sybase replicate database, the replicate Replication Server updates the rs_lastcommit table as soon as the connection is resumed. If the replicate Replication Server error log displays a syntax error while updating the rs_lastcommit table, the following procedure may help identify the problem.

StepsTo troubleshoot rs_lastcommit update failure

  1. Verify that the table exists in the replicate database and that the schema matches the script in the hds_xxx_setup_for_replicate.sql file.

    NoteFor a non-Sybase database, you should create the rs_lastcommit table by executing the hds_xxx_setup_for_replicate.sql script supplied with Replication Server.

  2. Verify access authority.

    Log in to the replicate database using the Replication Server Maintenance User ID and password specified in the create connection command for that database connection.

    Verify that this user ID can update the rs_lastcommit table. You should be able to insert and delete a dummy entry without error.

  3. Trace the actual command.

    Turn on tracing in the replicate Replication Server (DSI_BUF_DUMP trace) or in the DirectConnect gateway and resume the Replication Server connection.

    Identify the failing statement and correct as necessary.