Using the exceptions log

You can use the exceptions log to troubleshoot a problem with replication. For example, when a transaction is not processed because of a SQL error, you can follow this procedure:

  1. Right-click the connection and select Resume. Issue the resume command with a skip transaction clause to the queue.

  2. Right-click the connection and select View Exceptions. The View Exceptions dialog box displays the exceptions log in the Exceptions Log table

  3. View the skipped transaction and the erroneous SQL in the exceptions log.

  4. Filter the display of the exceptions log by selecting the columns in the table: Origin Data Server, Origin Database, and Previous Hours.

  5. To see the command language associated with a transaction, select it from the Exceptions Log table. The Command Editor text box displays the SQL commands in the transaction.

  6. Edit the transaction in the text box.

  7. To resubmit the transaction to the replicate data server, select Resubmit.




Copyright © 2010. Sybase Inc. All rights reserved. Accessing queue data