Adding new tables
...
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.
| Note |
|---|
If a table is added to the replication that already has historic data, then this data needs to be added to the target table. Please see "Loading the data before table is added to replication" below. |
One-to-Many Replication
In one-to-many replication, you have to choose which replication process you want the new table to belong to before preparing the table for replication.
...
| 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 that 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
Adding new schemas
To add a new schema to the replication run the following command.:
| Panel | ||
|---|---|---|
| ||
dbvrep> PREPARE SCHEMA schema |
...