Page Comparison

...

dbvrep> PREPARE TABLE schema.table_name

Ensure that the appropriate privileges are given to the Dbvisit Replicate owner on both the source and target. The privileges are:

SQL> grant select, update, insert, delete to dbvrep;

If a DDL replication was enabled during the Setup Wizard (Step 2 - Replication pairs), the Dbvisit Replicate owner on the target database already has SELECT/INSERT/UPDATE/DELETE ANY privileges. No other grants should be necessary.

Loading data before table is added to replication

When a new table is added to the replication, it is usually necessary to ensure that the historical data is in the target table before the replication starts. To ensure there is no gap between loading the historical data and starting the replication, we recommend the following steps:

1. Pause the apply process (PAUSE APPLY)
2. PREPARE the new table. Dbvisit Replicate will give the SCN of where the table will be replicated from.
3. Use the SCN from step 2 to load the historical data (Example use datapump with flashback_scn=xxx)
4. Resume the replication (RESUME APPLY)

Note that the table needs to exist on the target side before the apply process can be resumed. Using a datapump in step 3 is a good choice, since the import creates table automatically if it does not exist.

...

To add a new schema to the replication run the following command.

dbvrep> PREPARE SCHEMA schema

All the tables within the schema must be initialized in the same way as described above for the single table preparation. Follow those steps to ensure there is no data missing on the target side.

...

dbvrep> UNPREPARE TABLE schema.table_name

UNPREPARE will only take affect after a restart of the mine process.

Use UNPREPARE SCHEMA command to manually remove the whole schema.