Prepare command - Adding new tables
...
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. This is also called data instantiation. To ensure there is no gap between loading the historical data and starting the replication, we recommend the following steps:
- Pause the apply APPLY process (PAUSE APPLY)
- PREPARE the new table. Dbvisit Replicate will give the SCN of where the table will be replicated from.
- Use the SCN from step 2 to load the historical data (Example use datapump with flashback_scn=xxx)
- Resume the replication (RESUME APPLY)
...
| Info |
|---|
The PREPARE commands add supplemental logging to the table if it was not there yet. This can sometimes result in the ORA-01466 error while performing step 3. If this happens, we recommend using the internal commands to prepare a new table. In following example, scott.emp table is prepared. It first adds the supplemental logging, then waits for the SCN to advance then it does the actual PREPARE: dbvrep>ENGINE SUPPLEMENTAL LOGGING TABLE SCOTT.EMP ENABLE PRIMARY KEY |
...
| Note |
|---|
...
The table needs to exist on the target side before the |
...
APPLY process can be resumed. Using datapump in step 3 is a good choice, since the import creates the table automatically if it does not exist. |
| Note |
|---|
impdp does not actually compare the SCNs, but timestamp converted using dbms_flashback to SCN and the last_ddl time in dba_objects. |
Example:
http://support.dbvisit.com/entries/24422248-Synching-up-one-table-when-it-gets-out-of-sync
...