Sybase Replication Agent uses a trigger-based log solution for Informix and Microsoft SQL Server databases. Use the following procedure to isolate the problem if an object marked for replication fails to update the log.
Replication Agents for DB2 Universal Database and Oracle
(on either OS/390 platforms, or UNIX, Windows NT, or Windows
2000 platforms) are not trigger-based.
To find the problem when a trigger-based log fails
to update
Verify that no exceptions have been logged.
The Replication Agent can log exceptions to an exception table (the default name is ra_exception) in the primary database.
Select the contents of the exception table. The table should be empty or contain a single empty entry. If the table is not empty, use the information in the exception to determine the problem.
Check the primary database log for error messages.
Verify that error messages are returned to the client application.
It may be that an error message is being generated, but the client application is suppressing it.
Attempt the command as a different user.
If logging occurs using a different user ID, the problem may be related to database permissions.
Check any related primary database system tables used to record error information.
For example, in Oracle, the all_errors system table can contain information about triggers and procedures that have been invalidated.
Check the database error tables for entries with object names that start with the same prefix as Replication Agent transaction log objects, that is, the value of the pdb_xlog_prefix configuration parameter.
Verify that triggers or procedures are enabled.
Some primary databases allow triggers or procedures to be enabled or disabled at the system level.
