These Replication Agent features have unique behavior in Replication Agent for UDB.
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 ra_admin init command returns an error. This user ID is stored in the Replication Agent pds_username configuration parameter.
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.
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.