Handling replicated tables during a schema-level restore of column-organized tables

During a schema-level restore of column-organized tables with row modification tracking, tables in the schema are dropped and recreated. You must take different steps depending on your settings for replicating DDL operations.

About this task

The actions that you take to ensure your replicated tables are the same on both the source and target depend on whether you choose to replicate CREATE TABLE and DROP TABLE operations when you create your replication set.
  • If you specified Replicate create and drop tables when you created the replication set, all of the tables in the schema are recreated at the target so that they are identical to the source.
  • If you did not specify Replicate create and drop tables, you need to remove the restored tables from the replication set and then add them back, with the initial load option. Because there is no replication of the CREATE TABLE and DROP TABLE operations, replication does not automatically ensure that the target table is refreshed to match the source table.

Procedure

Complete the schema-level restore, based on whether you chose to replicate CREATE TABLE and DROP TABLE operations.
When replicating CREATE TABLE and DROP TABLE operations:
  1. Stop the replication set that contains the schema that you are about to restore.
    Important: Do not stop individual tables, only the entire replication set. Stopping the set only suspends replication so that you can resume it later without the need for a load phase. Stopping individual tables forces a reload, during which the tables are inaccessible.
  2. Perform the restore operation.
  3. Start the replication set.
When not replicating CREATE TABLE and DROP TABLE operations:
  1. Edit the replication set to remove any tables that are part of the schema backup and restore.
    Important: You do not need to stop the replication set in this scenario.
  2. Perform the restore operation.
  3. If any DDL changes were made to source tables in the schema since the last backup, drop the corresponding target tables.
  4. Edit the replication set to add the affected tables. Ensure that you choose to load all tables in the replication set when the set is started.
  5. Do either of the following:
    • Start any tables that were added back individually on the replication set details pages.
    • Stop and then start the replication set.