If you need to temporarily stop replication for a marked table (for example, when maintenance operations are performed in the primary database), you can disable replication for a marked table without affecting replication for other tables in the primary database. Then, when you are ready to resume replication from that table, you can enable replication for that table without affecting other tables in the database.
To replicate transactions that affect the data in a table, that table must be marked for replication, and replication must be enabled for the marked table. For more information, see “Marking and unmarking tables”.
Replication Agents for Microsoft SQL Server and UDB have a marked objects table which contains an entry for each marked table in the primary database. Each marked table row contains a flag indicating whether replication is enabled or disabled for the marked table. Replication Agent for Oracle has articles in the RASD. An article is an object that has a one-to-one relationship to the tables and has a marked indicator.
Replication Agent has articles in the RASD. An article is an object that has a one-to-one relationship to the tables and has a marked indicator.
When replication is disabled for a marked object, the marking infrastructure remains in place, but no transactions for that object are sent to Replication Server.
For Replication Agents for Microsoft SQL Server or DB2
UDB, if you need to change the schema of a marked table in the primary
database, you must first unmark the table to remove the transaction
log objects that Replication Agent creates for the primary table.
This is not required for Replication Agent for Oracle since DDL commands are captured in the Oracle database and the RASD will be updated automatically.
See “Marking and unmarking tables” for more information.
