All keywords are case-insensitive.
...
Shows Dbvisit Replicate version. Can be also invoked by --V switch.
PREPARE
| Align |
|---|
Used for adding tables or schemas to the replication. Prepares a schema/table for replication and declares that their content is in sync as of now. If a schema is prepared and DDL replication is enabled, new tables created in this schema in future will be also prepared and replicated. By default, this command connects to running apply and mine and instructs them to replicate the schema/table. If OFFLINE is used, apply/mine will pick the new tables on the next start. Use OFFLINE if the apply and mine are not running, as some network configurations may cause long timeouts while PREPARE tries to connect to the apply/mine. By default, DDL replication is enabled. Use NODDL to disable it (mandatory for non-Oracle databases). RENAME clause makes the replication to apply the changes to the given schema/table at apply. Note that the RENAME TO clause requires the NODDL option. PREPARE will lock the table to ensure no inflight transactions are missed. During initial setup in the *.dbvrep script, the PREPARE command is often preceded with the ENGINE LOCK TABLES, or ENGINE LOCK SCHEMAS command (followed by the RELEASE LOCK). Prepare recognizes that the ENGINE LOCK command has run and use the SCN from the lock. So when multiple tables are prepared, only a single SCN is used for all tables. When an ENGINE LOCK command has been issued in the same session, then the PREPARE command will no longer lock the tables. To clear the session, restart the console. |
UNPREPARE
Used for removing tables or schemas from the replication.
Unprepares a schema/table for replication and declares that this object should no longer be replicated.
If OFFLINE is used, apply/mine will pick the change on the next start. Use OFFLINE if the apply and mine are not running, as some network configurations may cause long timeouts while PREPARE tries to connect to the apply/mine.
REPREPARE
Repreare
Used for adding tables or schemas to the replication.
Reprepare does UNPREPARE and PREPARE in a single step to save typing. It also understands that there is no need to drop supplemental logging in the unprepare phase as prepare would create it again.
...
The DEFAULT conflict handler will not be applied to existing prepared (replicated) tables. The DEFAULT conflict handler will only be applied to tables that are prepared after the DEFAULT conflict handler is set. To change the conflict handler for existing prepared tables, each table has to be individually set using FOR TABLE conflict handler.
SHOW_CONFLICT_HANDLERS
Shows current setting of conflict handlers for given table (schema.name refers to table at mine).
...