Log-based Replication Agents (for DB2 Universal Database) and trigger-based Replication Agents (for Informix, Microsoft SQL Server, and Oracle) have different transaction log maintenance requirements.
A log-based Replication Agent uses the native transaction log maintained by the primary database to capture transactions for replication. Log-based Replication Agents also create some transaction log objects in the primary database to maintain system data for the Replication Agent, but these database objects require no routine maintenance.
Routine transaction log maintenance requirements are no different for a primary database when a log-based Replication Agent is used.
A trigger-based Replication Agent uses its own proprietary transaction log to capture transactions in the primary database for replication. The Replication Agent transaction log consists of tables, stored procedures, and triggers that the Replication Agent creates in the primary database.
The only routine maintenance required for the trigger-based Replication Agent transaction log is truncation. If not periodically truncated, the transaction log can grow large enough to consume all the available resources allocated to the primary database.
See Chapter 4, “Sybase Replication Agent Command Reference,” for more information on using the pdb_truncate_xlog command to truncate the Replication Agent transaction log.
