If the Replication Server outbound queue is being updated but transaction data is not being applied at the replicate database, use the following procedure to determine the reason.
To determine why replicate transactions are not
applied at the replicate database
Determine if the subscription contains a where clause.
Verify that the transaction data expected will pass any where clause in the subscription definition. Use the rs_helpsub stored procedure to list the text of the subscription.
Verify HDS installation.
If you are using Replication Server HDS to support replication to or from a non-Sybase data server, verify that the HDS scripts have been properly applied.
See “Expected datatype translations do not occur” for more information.
Verify that the rs_lastcommit table is set up correctly.
If you are using Replication Server HDS to support replication to or from a non-Sybase data server, verify that the HDS scripts have been properly applied.
Refer to “Updates to rs_lastcommit fail” for more detail.
Review the replicate Replication Server log for errors.
Review the replicate database log for errors.
Verify manual access to replicate objects.
Log in to the replicate database (or DirectConnect gateway) using the Replication Server connection Maintenance User ID, and verify that you have update authority to the replicate table or procedure.
Validate commands sent to the replicate database:
Turn on the DSI_BUF_DUMP trace in the replicate Replication Server and record to the Replication Server log the commands being sent to the replicate database.
Verify that these commands, when manually applied, produce the expected results.
The DSI_BUF_DUMP trace
flag can be used with any Replication Server. (By contrast, the
similar DSI_CMD_DUMP trace
flag is available only with the diagnostic version of Replication
Server.) Refer to the Replication Server Troubleshooting
Guide for more information about the Replication Server
traces.
Turn on tracing at the DirectConnect gateway to see what commands are being received.
For example, these parameters in a DirectConnect for Oracle configuration file cause DirectConnect to write additional information to the DCO.log file:
network_tracing = 1
traces = 1,2,3,4,5,6,10
Refer to the appropriate DirectConnect documentation for specific trace availability and syntax.
