The following Sybase Replication Agent features have unique behavior in the Replication Agent for UDB:
Creating a transaction log
Marking a table for replication
The Replication Agent for UDB provides the same features for creating and removing the “transaction log” as other implementations of the Sybase Replication Agent. However, since the actual transaction log used by Replication Agent for UDB is the native transaction log of the DB2 Universal Database server, Replication Agent for UDB creates fewer tables in the primary database to store its system information. The Replication Agent for UDB does not create any stored procedures or triggers in the primary database.
Because the Replication Agent for UDB requires access to the DB2 Universal Database transaction log, the user ID that the Replication Agent uses to access the primary database must have either SYSADM or DBADM authority in the database; otherwise, the pdb_xlog create command returns an error. This user ID is stored in the Replication Agent pds_username configuration parameter.
For more information about the Replication Agent for UDB transaction log, see “Replication Agent for UDB transaction log”.
The Replication Agent for UDB provides the same features for marking and unmarking tables for replication as other implementations of the Sybase Replication Agent. However, the Replication Agent for UDB does not create any stored procedures or triggers in the primary database.
When marking a table for replication, Replication Agent for UDB alters the table to set the UDB DATA CAPTURE attribute to DATA CAPTURE CHANGES. When the table is unmarked, the table is altered to return to its original DATA CAPTURE attribute.
Do not change the DATA CAPTURE attribute
of a table marked for replication with the Replication Agent for UDB.
