All keywords are case-insensitive.
...
| Anchor | ||||
|---|---|---|---|---|
|
CHOOSE REPLICATION process will allow you to choose which processes will be specified when issuing commands or displaying settings. This can be done by specifying the process name or by means of source and target databases.
...
| No Format | ||
|---|---|---|
| ||
dbvrep> DDL CREATE PRINT scott.dept CREATE TABLE "SCOTT"."DEPT" ( "DEPTNO" NUMBER(2), "DNAME" VARCHAR2(14), "LOC" VARCHAR2(13)); dbvrep> dbvrep> DDL DROP PRINT scott.dept DROP TABLE "SCOTT"."DEPT" cascade constraints; dbvrep> dbvrep> DDL CREATE SPOOL SCOTT.dept to test.txt File test.txt has been written successfully. |
| Anchor | ||||
|---|---|---|---|---|
|
Example:
Delete Windows service for given process. (Windows only)
| No Format | ||
|---|---|---|
| ||
dbvrep> DELETE SERVICE MINE Service DbvisitReplicateorcldb_MINE deleted. dbvrep> |
| Anchor | ||||
|---|---|---|---|---|
|
...
Execute command in a new shell. See also EXCLAMATION MARK.
Example:
| No Format | ||
|---|---|---|
| ||
dbvrep> EXEC pwd /home/oracle/v2714_4933 dbvrep> |
...
| No Format | ||
|---|---|---|
| ||
dbvrep> HEALTHCHECK Connectivity test for APPLY: OK Connectivity test for MINE: OK 2 processes checked. dbvrep> |
| Anchor | ||||
|---|---|---|---|---|
|
...
Shows general help, help for specific command or help for a variable.
...
| No Format | ||
|---|---|---|
| ||
dbvrep> HELP FILTER Command FILTER: Set filtering condition -- Command syntax -- FILTER [OFFLINE] (TABLE schema.table | SCHEMA schema) ON (INSERT|PRE-UPDATE|POST-UPDATE|DELETE) SET TO sql condition: Set filtering condition for specified table/schema for specified operation. dbvrep> dbvrep> HELP SET MAILCFG_SMTP_SERVER MAILCFG_SMTP_SERVER - Sets SMTP mail server to be used for sending emails. dbvrep> |
...
| Anchor | ||||
|---|---|---|---|---|
|
...
| No Format | ||
|---|---|---|
| ||
dbvrep> license show
Licensed for , 30-day license (trial license). dbvrep> *license show full
Product: Dbvisit Replicate
Allowed versions:1.0-2.63
Key-version: 1
License type: RS1S
Customer id: 1.0 (trial license)
Production: yes
License-type: server
Name: *
Expiry: 30 days
CPU count mine: 0
CPU count apply: 0
Row-count limit: unlimited
Enabled options: rac, fetcher, partitions, onetomany, cascade, 2way, ddl, asm, mysql, mssql, oracle, snmp, mail_notify
Licensed for *, 30-day license (trial license).
Additionally to set the license key use the following command in the console:
dbvrep> set license_key XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX-XXXXX |
| Anchor | ||||
|---|---|---|---|---|
|
Displays the current status of MINE, APPLY and FETCHER processes.
...
| No Format | ||
|---|---|---|
| ||
dbvrep> LIST STATUS MINE IS running. Currently at plog 3274 and SCN 79668707 (03/30/2015 05:09:34). APPLY IS running. Currently at plog 3274 and SCN 79668685 (03/30/2015 05:09:29). dbvrep> |
...
Connects to database and lists registered REDOLOGS / PLOGS.
...
| 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. When using 'prepare as of SCN ' command to include tables in the on-going replication from pre-specified SCN, make sure that the current SCN of replication ( where MINE and APPLY is right now) is not greater than the SCN in "prepare as of SCN" command. |
Example:
| No Format | ||
|---|---|---|
| ||
dbvrep> PREPARE as of 79728416 TABLE scott.test1 noddl Prepare enabled supplemental logging, waiting for SCN advance enough to prevent ORA-01466 during consistent export....Waited 1 seconds until scn_to_timestamp changed. Connecting to running apply [SCOTT.TEST1]: [Apply table removed (0 metadata record(s)). Apply table added (1 metadata record(s)).] Connecting to running mine [SCOTT.TEST1]: [Table prepared (1 internal records).] Table SCOTT.TEST1 instantiated at SCN 79728416 dbvrep> |
...
Calls upon the MINE process to use the LOAD feature to populate the given table at the given SCN.
Example:
| No Format | ||
|---|---|---|
| ||
dbvrep>PROCESS LOAD_REQUEST TABLE SCOTT.sample_table AT INSTANTIATE SCN |
| Anchor | ||||
|---|---|---|---|---|
|
Exits dbvrep. See also EXIT.
...
| No Format | ||
|---|---|---|
| ||
dbvrep> READ filename.txt dbvrep> |
...
| Anchor | ||||
|---|---|---|---|---|
|
...
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.
Example:
| No Format | ||
|---|---|---|
| ||
dbvrep> SET_CONFLICT_HANDLERS FOR TABLE SCOTT.DEPT FOR UPDATE on NO_DATA TO OVERWRITE Connecting to running apply: [The table called SCOTT.DEPT on source is handled on apply (APPLY) as follows: UPDATE (error): handler: RETRY logging: LOG UPDATE (no_data): handler: OVERWRITE logging: LOG UPDATE (too_many): handler: RETRY logging: LOG DELETE (error): handler: RETRY logging: LOG DELETE (no_data): handler: RETRY logging: LOG DELETE (too_many): handler: RETRY logging: LOG INSERT (error): handler: RETRY logging: LOG TRANSACTION (error): handler: RETRY logging: LOG] dbvrep> |
...