The following Sybase Replication Agent features have unique behavior in the Replication Agent for UDB:
Creating a transaction log
Marking a table for replication
Support for rs_marker and rs_dump function calls
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. This user ID is stored in the Replication Agent pds_username configuration parameter.
If the user ID specified in the pds_username parameter
does not have either SYSADM or DBADM authority
in the primary database, the pdb_xlog create command
returns an error.
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 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.
The Replication Agent for UDB does not provide a stored procedure for the Replication Server rs_marker function call because the DB2 Universal Database server does not support procedures stored in the database. The Replication Agent for UDB provides shadow tables to support Replication Server rs_marker function calls.
The rs_marker function is used only if Replication Server is configured to perform automatic materialization.
To set up automatic materialization for the DB2 Universal Database server, you must create an rs_marker custom function string in Replication Server.
Before you create the rs_marker function string, you must use the Replication Agent pdb_xlog command to create the Replication Agent transaction log system tables in the primary database. You can then invoke the pdb_xlog command with no parameters to determine the actual name of the shadow table associated with rs_marker.
When you create the custom function string for rs_marker, you must use an insert statement that refers to the actual shadow table generated by the Replication Agent pdb_xlog command.
