Versions Compared

Version Old Version 9 New Version Current
Changes made by

Chris Lawless (Deactivated)

Jakub Sejba

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

All keywords are case-insensitive.

...

Execute command in a new shell. See also EXEC.

...

Image Removed

Reads the designated filename like it would be entered at the command prompt. As with SQL*Plus, both "@file" and "@ file" work.. See also READ.

...

Image Removed

APPLY COMMIT TRANSACTION. Force commit of the specified transaction on APPLY. 

Example:

No Format
bgColorCCC
dbvrep> APPLY COMMIT TRANSACTION 0002.01a.00010cec!pwd
/home/oracle/demo                                                                                                                                         Commit added to applier and applier ran.

Anchor
@
@
READ

Image Added

Reads the designated filename like it would be entered at the command prompt. As with SQL*Plus, both "@file" and "@ file" work.. See also READ.

No Format
bgColorCCC
dbvrep> @/home/oracle/my_file_name.txt                                                                                                                                dbvrep>

Anchor
APPLY
APPLY
APPLY

Image Added

APPLY ROLLBACK COMMIT TRANSACTION. Force rollback commit of the specified transaction on APPLY.
Use List transactions first to see what transactions are currently pending on APPLY. Ensure you fully understand the implication before running these commands. 

Example:

No Format
bgColorCCC
dbvrep> APPLY ROLLBACKCOMMIT TRANSACTION 0002.01a.00010cec                                                                                                                                      
RollbackCommit added to applier and applier ran.                                                                                                                                              dbvrep>                          dbvrep>

APPLY ROLLBACK TRANSACTION. Force rollback of the specified transaction on APPLY.
Use List transactions first to see what transactions are currently pending on APPLY. Ensure you fully understand the implication before running these commands. 

Example:

No Format
bgColorCCC
dbvrep> APPLY ROLLBACK TRANSACTION 0002.01a.00010cec

APPLY FLUSH FILES. When the output is into files (CSV/Hadoop), force flush of committed data in memory to disk, even if the files would be below configured size thresholds.

Example:

No Format
bgColorCCC
dbvrep> apply flush files      
Rollback added to applier and applier ran.                                                                                                                                           1 file flushed. dbvrep>


APPLY FLUSH FILES. When the output is into files (CSV/Hadoop), force flush of committed data in memory to disk, even if the files would be below configured size thresholds.

Example:

No Format
bgColorCCC
dbvrep> apply               flush files

APPLY REGISTER PLOG. In certain circumstances you may copy plogs manually to the target server.  Use this command to tell apply about these new files.  Make sure that the files do exist on the target.  This command must be run the target server.  This may mean that you must run the dbvrep console from the target server.

Example:

No Format
bgColorCCC
dbvrep> apply register plog 2865                                     
1 file flushed.
dbvrep>                                                                                                                Manually registering plogs 2865 to 2865: OK: Plog information updated (seq 2865). dbvrep>        dbvrep> apply register plog 2864 to 2865                                                                                                                                                 Manually registering plogs 2864 to 2865:
OK: Plog information updated (seq 2864).
OK: Plog information updated (seq 2865).   
dbvrep>

APPLY REGISTER PLOG. In certain circumstances you may copy plogs manually to the target server.  Use this command to tell apply about these new files.  Make sure that the files do exist on the target.  This command must be run the target server.  This may mean that you must run the dbvrep console from the target server.

Example:

No Format
bgColorCCC
dbvrep> apply register plog 2865                                                                                                                                                        
Manually registering plogs 2865 to 2865:
OK: Plog information

...

Image Removed
Configure CDC/Audit for an already prepared table/schema. The usual way how to configure this is using Setup wizard (which in turn uses this very command). 

...

updated (seq 2865).
dbvrep>       
dbvrep> apply register plog 2864 to 2865                                                                                                                                                
Manually registering plogs 2864 to 2865:
OK: Plog information updated (seq 2864).
OK: Plog information updated (seq 2865).   
dbvrep>

Anchor
CDCAUDIT
CDCAUDIT
CDCAUDIT

Image Added
Configure CDC/Audit for an already prepared table/schema. The usual way how to configure this is using Setup wizard (which in turn uses this very command). 
This command sets this feature for insert/update/delete operations, sets the prefix for new/old value columns and configures additional added columns (operation type, transaction, session audit information, etc).

...

No Format
bgColorCCC
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
DELETE SERVICE process
DELETE SERVICE process
DELETE SERVICE

Example:

Delete Windows service for given process. (Windows only)

No Format
bgColorCCC
dbvrep> DELETE SERVICE MINE     
Service DbvisitReplicateorcldb_MINE deleted.                                                                                                                                                       dbvrep>

 


Anchor
DOWNGRADE REPOSITORY
DOWNGRADE REPOSITORY
DOWNGRADE REPOSITORY

...

No Format
bgColorCCC
dbvrep> DUMP MINE ALL                                                                                                                                           
Dump complete.                                                                                                                                                  dbvrep> dbvrep>
dbvrep> DUMP MINE MESSAGES
Trace messages dump complete.                                                                                                                                   dbvrep>    
dbvrep> DUMP MINE MEMORY_ACCOUNTING                                                                                                                             
Memory accounting dump complete. 
dbvrep> dbvrep> 

Anchor
ENCRYPT password
ENCRYPT password
ENCRYPT

...

No Format
bgColorCCC
dbvrep>EXCLUDE COLUMN SCOTT.DEPT.LOC                                                                                                                                           
Connecting to running mine [SCOTT.DEPT.LOC] 2: [Column excluded (1 internal records).]
Exclude Column [SCOTT.DEPT.LOC] set. 
dbvrep>

Anchor
EXCLUDE CREATE TABLE
EXCLUDE CREATE TABLE
EXCLUDE CREATE TABLE

...

The commands add a new rule; if an existing rule of opposite meaning already exists, it is deleted instead. The matching starts with the oldest one and goes on till the newest rule added; if a reordering is needed, clear the list and start again. The SHOW option lists the existing rules using the very same syntax, so the list can be easily edited and then executed to APPLY the changes.

Additional example found @ https://support.dbvisit.com/hc/en-us/articles/115000220613-Exclude-CREATE-TABLE-for-a-specific-schema

This command requires a restart of the MINE process.

...

No Format
bgColorCCC
dbvrep> EXCLUDE CREATE TABLE scott2%.%                                                                                                                          
Exclude rule created.
dbvrep>
dbvrep> EXCLUDE CREATE TABLE SHOW                                                                                                                              
List of excluded (included) tables:
EXCLUDE CREATE TABLE CLEAR
EXCLUDE CREATE TABLE scott2%.%
1 rule(s) listed.
dbvrep>  
dbvrep> EXCLUDE CREATE TABLE CLEAR                                                                                                                              
1 rule(s) deleted.
dbvrep>

...

Execute command in a new shell. See also EXCLAMATION MARK. 


Example:

No Format
bgColorCCC
dbvrep> EXEC pwd                                                                                                                                                
/home/oracle/v2714_4933
dbvrep>

...

No Format
bgColorCCC
dbvrep> EXIT
$>

Anchor
FILTER
FILTER
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). this very command). 

NOTE ** DO NOT put a semicolon after the command in the console or upon restart of APPLY process it will not start & create support package.

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.

...

No Format
bgColorCCC
dbvrep> FILTER TABLE SCOTT.DEPT ON INSERT SET TO deptno > 50                                                                                                   
Connecting to running apply: [Apply table removed (1 metadata record(s)). Apply table added (1 metadata record(s)).]
Filter condition on table SCOTT.DEPT set.
dbvrep> 
dbvrep> FILTER SCHEMA SCOTT ON INSERT SET TO where id >20                                                                                  
Connecting to running apply: [Apply table removed (0 metadata record(s)). Apply table added (0 metadata record(s)).]
Filter condition on table SCOTT.BONUS set.
Connecting to running apply: [Apply table removed (0 metadata record(s)). Apply table added (0 metadata record(s)).]
Filter condition on table SCOTT.DEPT 
Connecting to running apply: [Apply table removed (0 metadata record(s)). Apply table added (0 metadata record(s)).]
Filter condition on table SCOTT.EMP set.
Connecting to running apply: [Apply table removed (0 metadata record(s)). Apply table added (0 metadata record(s)).]
Filter condition on table SCOTT.SALES set.
Connecting to running apply: [Apply table removed (0 metadata record(s)). Apply table added (0 metadata record(s)).]
Filter condition on table SCOTT.SALGRADE set.
Connecting to running apply: [Apply table removed (0 metadata record(s)). Apply table added (0 metadata record(s)).]
dbvrep> 






dbvrep> filter show table scott.sales                                                                                                      
Filter conditions on table SCOTT.SALES are set as follows:
insert     : deptno>50
pre-update : (no filter)
post-update: (no filter)
delete     : (no filter)
dbvrep>    
dbvrep> filter show schema scott                                                                                                           
Filter conditions on schema SCOTT are set as follows:
insert     : (no filter)
pre-update : (no filter)
post-update: (no filter)
delete     : (no filter)
dbvrep>

Anchor
HEALTHCHECK
HEALTHCHECK
HEALTHCHECK

...

No Format
bgColorCCC
dbvrep> HEALTHCHECK                                                                                                                                             
Connectivity test for APPLY: OK
Connectivity test for MINE: OK
2 processes checked.
dbvrep>

Anchor
HELP
HELP
HELP

...


Shows general help, help for specific command or help for a variable.

...

No Format
bgColorCCC
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
INCLUDE COLUMN
INCLUDE COLUMN
INCLUDE COLUMN

...

No Format
bgColorCCC
dbvrep> INCLUDE CREATE TABLE SCOTT2.%                                                                                                                           
Include rule created.
dbvrep>   
dbvrep> INCLUDE CREATE TABLE SHOW                                                                                                                               
List of excluded (included) tables:
EXCLUDE CREATE TABLE CLEAR
EXCLUDE CREATE TABLE scott2%.%
INCLUDE CREATE TABLE SCOTT2.%
2 rule(s) listed.

dbvrep>   dbvrep> INCLUDE CREATE TABLE CLEAR2 rule(s) deleted.
dbvrep>

Anchor
LICENSE
LICENSE
LICENSE

...

No Format
bgColorCCC
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
LIST
LIST
LIST

Displays the current status of MINE, APPLY and FETCHER processes. 

...

No Format
bgColorCCC
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.

...

No Format
bgColorCCC
dbvrep> LIST MINE REDOLOGS                                                                                                                                      

O Seq#   FirstSCN    NextSCN    ReadCount  StartDate              EndDate              FileName
-----------------------------------------------------------------------------------------------
N 3267   79626512   79634437            1   30.03.2015 03:23:40   30.03.2015 03:23:53 
/u01/app/oracle/fast_recovery_area/SDB11/archivelog/2015_03_30/o1_mf_1_3267_bkkyb3jm_.arc
N 3268   79634437   79635588            1   30.03.2015 03:23:54   30.03.2015 03:24:06 
/u01/app/oracle/fast_recovery_area/SDB11/archivelog/2015_03_30/o1_mf_1_3268_bkkyb7gq_.arc
N 3269   79635588   79635595            1   30.03.2015 03:24:06   30.03.2015 03:24:06 
/u01/app/oracle/fast_recovery_area/SDB11/archivelog/2015_03_30/o1_mf_1_3269_bkkybcsz_.arc
N 3270   79635595   79635664            1   30.03.2015 03:24:06   30.03.2015 03:24:06 
/u01/app/oracle/fast_recovery_area/SDB11/archivelog/2015_03_30/o1_mf_1_3270_bkkybkz1_.arc
N 3271   79635664   79635727            1   30.03.2015 03:24:06   30.03.2015 03:25:57  
 
dbvrep> 
dbvrep> LIST APPLY PLOGS                                                                                                                                        
O Seq#   FirstSCN    NextSCN    LastSCN ProcessDate         FileName
--------------------------------------------------------------------
N 3267   79626512   79634434   79632380 30.03.2015 03:24:03 /home/oracle/review/apply/3267.plog
N 3268   79634437   79635583   79635587 30.03.2015 03:24:19 /home/oracle/review/apply/3268.plog
N 3269   79635588   79635589   79635594 30.03.2015 03:24:49 /home/oracle/review/apply/3269.plog
N 3270   79635595   79635659   79635663 30.03.2015 03:24:50 /home/oracle/review/apply/3270.plog

...

No Format
bgColorCCC
dbvrep> LIST PROGRESS SCOTT
 Progress of replication review: total/this execution
    --------------------------------------------------------------------------------------------------------------------------------------------

    SCOTT.T2:                     100%  Mine:23/23           Unrecov:0/0         Applied:23/23       Conflicts:0/0       Last:30/03/2015 03:27:19/OK

    SCOTT.DEPT:                   100%  Mine:27/27           Unrecov:0/0         Applied:27/27       Conflicts:0/0       Last:30/03/2015 03:26:16/OK

    SCOTT.EMP:                    100%  Mine:14/14           Unrecov:0/0         Applied:14/14       Conflicts:0/0       Last:30/03/2015 03:26:16/OK
--------------------------------------------------------------------------------------------------------------------------------------------

    3 tables listed. 


LIST PREPARE. Shows list of prepared tables. You can optionally specify a schema to filter the results to a particular database schema (this is source schema if renaming is used). Use ALL to see everything including internal tables.

...

No Format
bgColorCCC
dbvrep> MEMORY_SET mine.mailcfg_from = info@example.com                                                                                                         
Variable MAILCFG_FROM set to info@example.com for process mine.
dbvrep>

Anchor
NOTIFY
NOTIFY
NOTIFY

Image RemovedImage Added

Sends sample email/SNMP trap – use to test your SMTP/SNMP configuration.

...

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:

 


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.
No Format
bgColorCCC
Note

Please read the following page before using AS OF <scn> clause: Adding new object from a given SCN

Anchor
PREPARE_AND_LOAD
PREPARE_AND_LOAD
PREPARE_AND_LOAD

Image AddedImage Added

Prepares the new table to be added into the replication stream.  Also LOADs the table at the same time.  With this one command the table is prepared for all future changes and then loads the target table with all of the historical rows in the source table.  The target table will have to be created before running this command.  The dbvrep user on the SOURCE database will need to have SELECT and FLASHBACK privileges on the table that is being prepared and loaded.

Note

Please read the following page before using AS OF <scn> clause: Adding new object from a given SCN

Example:

No Format
bgColorCCC
dbvrep> PREPARE_AND_LOAD TABLE SCOTT.REPTEST4  
Connecting to running apply [SCOTT.TEST1REPTEST4]: [Apply table removed (0 metadata record(s)). Apply table added (1 metadata record(s)).]
Connecting to running mine [SCOTT.TEST1REPTEST4]: [Table prepared (1 internal records).]
Table SCOTTOLLIE.TEST1REPTEST4 instantiated at SCN 79728416
dbvrep>

...

Image RemovedImage Removed

DESCRIPTION

Example:

No Format
bgColorCCC
dbvrep> MAKE example 31096663
Table OLLIE.REPTEST4 will be loaded using SCN 31096663.
Connecting to running mine [SCOTT.REPTEST4]: [1 records processed.]
dbvrep>

Anchor
PROCESS LOAD_REQUEST
PROCESS LOAD_REQUEST
PROCESS LOAD_REQUEST

...

Calls upon the MINE process to use the LOAD feature to populate the given table at the given SCN.

 


Example:

No Format
bgColorCCC
dbvrep>PROCESS LOAD_REQUEST TABLE SCOTT.sample_table AT INSTANTIATE SCN

...


 Anchor
QUIT
QUIT
QUIT
Exits dbvrep. See also EXIT.
...
 No Format
bgColorCCC
dbvrep> QUIT
$>  
 Anchor
READ
READ
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
bgColorCCC
dbvrep> READ filename.txt
dbvrep>
 

 Anchor
REPREPARE
REPREPARE
REPREPARE
...
Reprepare runs the UNPREPARE and PREPARE commands 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.
 Note
Please read the following page before using AS OF <scn> clause: Adding new object from a given SCN
Example:
 No Format
bgColorCCC
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>   
 Anchor
READDDC
READDDC
READDDC
...
 Anchor
SET_CONFLICT_HANDLERS
SET_CONFLICT_HANDLERS
SET_CONFLICT_HANDLERS
Image Added
Image Added
Image RemovedImage Added
Image RemovedImage Added
Image RemovedImage Added
Image RemovedImage Added

Gets object id as of current MINE progress and sets conflict handlers for this table (schema.name refers to current table name at MINE).
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
bgColorCCC
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
bgColorCCC
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
SHOW_CONFLICT_HANDERSHANDLERS. Shows current setting of conflict handlers for given table (schema.name refers to table at MINE).
...
 No Format
bgColorCCC
dbvrep> show_conflict_handlers for table scott.dept                                                                                                                                     
The table called SCOTT.DEPT on source is handled on apply (APPLY) as follows:
UPDATE (error): handler: RETRY logging: LOG
UPDATE (no_data): handler: RETRY 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>  
dbvrep> show_conflict_handlers for default                                                                                                                                              
The default handling on APPLY is set as follows:
No handler of type UPDATE (error) defined.
No handler of type UPDATE (no_data) defined.
No handler of type UPDATE (too_many) defined.
No handler of type DELETE (error) defined.
No handler of type DELETE (no_data) defined.
No handler of type DELETE (too_many) defined.
No handler of type INSERT (error) defined.
No handler of type TRANSACTION (error) defined.
 
 Anchor
SHUTDOWN process
SHUTDOWN process
SHUTDOWN 
...
 No Format
bgColorCCC
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
bgColorCCC
dbvrep> start_service MINE
 
 Anchor
SUPPORT PACKAGE
SUPPORT PACKAGE
SUPPORT PACKAGE
...
 No Format
bgColorCCC
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
bgColorCCC
dbvrep> upgrade repository mine                                                                                                                                                         
OK-9255: [MINE] Requested version is same as the current one. No operation needed.
MINE: Upgrade skipped.
dbvrep>    
 Anchor
VERSION
VERSION
VERSION
...