The following Replication Agent features have unique behavior in the Replication Agent for UDB:
Initializing Replication Agent
Marking a table for replication
The Replication Agent for UDB provides the same features for initiliazing Replication Agent and creating its objects in the primary database as other implementations of the Replication Agent. Replication Agent for UDB creates only a few 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 UDB 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 init command returns an error. This user ID is stored in the Replication Agent pds_username configuration parameter.
See “Replication Agent objects in the UDB primary database”.
The Replication Agent for UDB provides the same features for marking and unmarking tables for replication as other implementations of the 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 manually change the DATA CAPTURE attribute
of a table that has been marked for replication by Replication Agent
for UDB. Doing so may adversely effect replication results.
Marking or unmarking all tables at once in the primary database using pdb_setreptable all, mark or pdb_setreptable all, unmark is not supported in Replication Agent for UDB. You must mark or unmark each table individually.
The following Replication Agent features are not available with Replication Agent for UDB:
Stored procedure replication–The replication of stored procedures is not available with the Replication Agent for UDB. Therefore, the pdb_setrepproc command is not supported.
DDL replication–The replication of data definition language (DDL) commands and system procedures executed in the primary database is not supported.
Altering replication definitions from the primary data server–This involves stored procedure replication, which is not supported.
Automatically creating replication definitions–This requires use of the Replication Agent rs_create_repdef command, which is not available for Replication Agent for UDB.
When you invoke Replication Agent commands related to
these features, you receive an error.
