All keywords are case-insensitive.
...
FILTER
Set filtering rules for an already prepared table/schema. The usual way how to configure filtering is using Setup wizard (which in turn uses this very command).
...
| No Format |
|---|
|
dbvrep> QUIT
$> Â |
READ
Reads the designated filename like it would be entered at the command prompt. As with SQL*Plus, both "@file" and "@ file" work. See @.
...
| No Format |
|---|
|
dbvrep> REPREPARE TABLE SCOTT.DEPT3
Connecting to running mine [SCOTT.DEPT3]: [Table unprepared (1 internal records).]
Connecting to running apply:[Apply table removed (1 metadata record(s)). Apply table added (0 metadata record(s)).]
Table SCOTT.DEPT3 processed.
Connecting to running apply [SCOTT.DEPT3]: [Apply table removed (0 metadata record(s)). Apply table added (1 metadata record(s)).]
Connecting to running mine [SCOTT.DEPT3]: [Table prepared (1 internal records).]
Table SCOTT.DEPT3 instantiated at SCN 79653884
dbvrep>
dbvrep> REPREPARE AS OF 79653884 TABLE SCOTT.DEPT3
Connecting to running mine [SCOTT.DEPT3]: [Table unprepared (1 internal records).]
Connecting to running apply:[Apply table removed (1 metadata record(s)). Apply table added (0 metadata record(s)).]
Table SCOTT.DEPT3 processed.
Connecting to running apply [SCOTT.DEPT3]: [Apply table removed (0 metadata record(s)). Apply table added (1 metadata record(s)).]
Connecting to running mine [SCOTT.DEPT3]: [Table prepared (1 internal records).]
Table SCOTT.DEPT3 instantiated at SCN 79653884
dbvrep> Â |
READDDC
...
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> |
...
| No Format |
|---|
|
dbvrep> SHOW notify
*.NOTIFY_ALERT_EMAIL = OFF
*.NOTIFY_ALL_EMAIL = chris.lawless@dbvisit.com
*.NOTIFY_CONFLICT_CURRENT_PAUSE = YES
*.NOTIFY_CONFLICT_CURRENT_RETRY = 2
*.NOTIFY_CONFLICT_THRESHOLD = 100
*.NOTIFY_DAILY_LIST_PROGRESS_TIME24 = 0700
*.NOTIFY_EXCEEDED_CYCLE_NUM = 2
*.NOTIFY_INCIDENT_LIMIT = 10
*.NOTIFY_INTERVAL_BETWEEN_CHECK = 5m
*.NOTIFY_ON_DDL = YES
*.NOTIFY_PEER_DOWN = ALL
*.NOTIFY_PROGRESS_DIFFERENCE_PERC = 10
*.NOTIFY_SCN_DIFFERENCE = 1000
*.NOTIFY_SEND_HEARTBEAT_TIME24 = 0800:1300
*.NOTIFY_SEQUENCE_DIFFERENCE = 10
*.NOTIFY_SUCCESS_EMAIL = OFF
*.NOTIFY_TIME_DIFFERENCE = 300 dbvrep> |
| Anchor |
|---|
| SHOW_CONFLICT_HANDLERS |
|---|
| SHOW_CONFLICT_HANDLERS |
|---|
|
SHOW_CONFLICT_HANDLERS
...
| No Format |
|---|
|
dbvrep> shutdown all
Upon restart MINE will go back to redolog 4873 (thread 1), going back 1 log.
Upon restart APPLY will go back to plog 4873, going back 1 plog.
Are you sure you want to shutdown? (Yes/No) [No]
dbvrep> shutdown mine
Upon restart MINE will go back to redolog 4873 (thread 1), going back 1 log.
Are you sure you want to shutdown? (Yes/No) [No]
dbvrep> shutdown immediate all
Dbvisit Replicate MINE process shutting down.
Dbvisit Replicate APPLY process shutting down.
dbvrep> |
| Anchor |
|---|
| START_SERVICE process |
|---|
| START_SERVICE process |
|---|
|
START_SERVICE
...
| No Format |
|---|
|
dbvrep> start_service MINE
 |
| Anchor |
|---|
| SUPPORT PACKAGE |
|---|
| SUPPORT PACKAGE |
|---|
|
SUPPORT PACKAGE
...
| No Format |
|---|
|
dbvrep> SUPPORT PACKAGE MINE
Packaging into ZIP file: ./dbvisit_support_dbvrep_RQ1180_MINE.UHSX.zip for process MINE, addinfo []
Packaging data from database. If this fails, restart SUPPORT PACKAGE with NODB option.
Zip file created: ./dbvisit_support_dbvrep_RQ1180_MINE.UHSX.zip (status: 1) dbvrep> |
For APPLY, ensure the command console is run from the APPLY server so that the APPLY logs and PLOGs can be found. If you run the support package from the SOURCE server (where most people typically run dbvrep) it will NOT include the log file. Please get the log file as well from the target server. If you do not have the command console on the target run the following command from the TARGET server.
...
| No Format |
|---|
|
dbvrep> upgrade repository mine
OK-9255: [MINE] Requested version is same as the current one. No operation needed.
MINE: Upgrade skipped.
dbvrep>
 |
VERSION
...