This section describes administration and maintenance procedures for the following Replication Agent variants:
Replication Agent for Microsoft SQL Server
Replication Agent for IBM DB2 Universal Database (UDB)
Replication Agent for Oracle
The Replication Agent for Microsoft SQL Server uses the native Microsoft SQL Server log to capture replicated transactions. The objects it creates in the primary database facilitate replication. These database objects require no routine maintenance.
See the Replication Agent Primary Database Guide for information about how to automatically truncate the primary database transaction log.
The Replication Agent for UDB uses the native DB2 log to capture replicated transactions. The Replication Agent for UDB creates objects in the primary database to store its system data, but those database objects require no routine maintenance.
Depending on the configuration, Replication Agent may process only online transaction logs (default) or may also access archived transactions logs. For information about online transaction log files, archive transaction log files, and log truncation, see the Replication Agent Primary Database Guide.
The Replication Agent for Oracle uses the native Oracle log to capture replicated transactions. The objects it creates in the primary database facilitate stored procedure replication. These database objects require no routine maintenance.
Depending on the configuration, Replication Agent may also access archived transactions logs (default) or may process only online transaction logs. For information about redo log and archive log files, see the Replication Agent Primary Database Guide.
The following sections describe each Replication Agent administration and maintenance task in detail:
