Primary Database Object Marking

Individual tables to be replicated must be marked. Tables can be marked explicitly with the pdb_setreptable command or automatically during ra_admin init processing when the pdb_automark_tables configuration parameter is set to true.

Note: The pdb_automark_tables parameter is not available for Replication Agent for UDB.

Tables, stored procedures, and sequences (Oracle only) must be marked for replication and have replication enabled for the object (table, stored procedure, or sequence). LOB columns must have replication enabled, and the table that contains the LOB column must be marked for replication and have replication enabled for that table.

There are four types of objects that can be marked for replication in a primary database:

If you drop a table in the primary database that is marked for replication and run pdb_setreptable, the command returns an incorrect mark status indicating that the table as marked. The pdb_setreptable owner.tablename command returns a correct error message indicating that the table does not exist in the primary database. If you create the same table again and run pdb_setreptable, the command still returns an incorrect mark status. The pdb_setreptable owner.tablename command returns a correct status indicating that the table is unmarked. These inconsistencies can also occur when you drop a stored procedure in the primary database and run the pdb_setrepproc command or drop a sequence in the primary database and run the pdb_setrepseq command. To avoid these inconsistencies, run the ra_truncatearticles command after you drop any table, stored procedure, or sequence in the primary database.