Marking and Unmarking Tables

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

To replicate transactions that affect the data in a table in the primary database, that table must be marked for replication, and replication must be enabled for the marked table.

Marking a table can be separate from enabling replication for that table. If the value of the pdb_dflt_object_repl parameter is true, replication is enabled automatically at the time a table is marked.

• Table Marking with Replication Agent for Oracle
  When a table is marked for replication with Replication Agent for Oracle, Replication Agent connects to the RASD and records the mark status for the table in the RASD article for that table.
• Table Marking and Unmarking with Replication Agent for Microsoft SQL Server
  When a table is marked for replication with Replication Agent for Microsoft SQL Server, Replication Agent logs in to the primary database and executes commands to turn on logging of changes in the Microsoft SQL Server transaction log.
• Table Marking with Replication Agent for UDB
  Replication Agent for UDB performs tasks at the primary database when a table is marked for replication.
• Table Unmarking with Replication Agent for UDB
  Replication Agent for UDB performs tasks at the primary database when a table is unmarked.
• Marking a Table in the Primary Database for Replication
  Mark tables for replication with any Replication Agent instance.
• Unmarking a Table in the Primary Database
  Unmark primary database tables.