Page Comparison

[oracle@source ~]$ dbvrep
Initializing......done
Dbvisit Replicate version 2.6.00.3735
Copyright (C) Dbvisit Software Limited.  All rights reserved.
No DDC file loaded.
Run "setup wizard" to start the configuration wizard or try "help" to see all commands available.
dbvrep> 

dbvrep> setup wizard                                                                                                                                                      
This wizard configures Dbvisit Replicate.
The setup wizard creates configuration scripts, which need to be run after the wizard ends. No changes to the databases are made before that.
The progress is saved every time a list of databases, replications, etc. is shown. It will be re-read if wizard is restarted and the same DDC name and script path is
selected.

Before starting the actual configuration, some basic information is needed. The DDC name and script path determines where all files created by the wizard go (and where to reread them if wizard is rerun) and the license key determines which options are available for this configuration.
(DDC_NAME) - Please enter a name for this replication (suggestion: use the name of the source database): [] dbvrep_orcl 	

(LICENSE_KEY) - Please enter your license key: [(trial)]

Step 1 - Describe databases
========================================
The first step is to describe databases used in the replication. There are usually two of them (source and target).
Store SYSDBA and DBA passwords? Passwords only required during setup and initialization? (yes/no) [yes]                                                                   
Let's configure the database, describing it's type, connectivity, user names etc.
What type of database is this? (Oracle/MySQL/SQL Server/Oracle AWS RDS/CSV/Hadoop): [Oracle]                                                      

Please enter database TNS alias: [] ttorcl_src                                                                                                                            

Connecting to database ttorcl_src as SYSTEM to query list of tablespaces and to detect ASM (by looking whether any redo logs or archived logs are stored in ASM).
Enter the Dbvisit Replicate owner (this user will be created by this script): [dbvrep]                                                                                    

Enter the number of the database to modify it, or "add", or "done": [add]                                                                                                 

Connecting to database ttorcl_trg as SYSTEM to query list of tablespaces and to detect ASM (by looking whether any redo logs or archived logs are stored in ASM).
Enter the Dbvisit Replicate owner (this user will be created by this script): [dbvrep]                                         this script): [dbvrep]                                             

Following databases are now configured:
1: Oracle ttorcl_src, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:NO, TZ: +00:00
2: Oracle ttorcl_trg, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:NO, TZ: +00:00
Enter the number of the database to modify it, or "add", or "done": [done] 

Step 2 - Replication pairs
========================================
The second step is to set source and targets for each replication pair.
Let's configure the replication pair, selecting source and target.
Following databases are described:
1: ttorcl_src (Oracle)  
2: ttorcl_trg (Oracle)  
Select source database: [1]                                                                                                                                               

Will be DDL replication enabled? [yes]                                                                        

Lock and copy the data initially one-by-one or at a single SCN?
one-by-one : Lock tables one by one and capture SCN
single-scn : One SCN for all tables
ddl-only   : Only DDL script for target objects
resetlogs  : Use SCN from last resetlogs operation (standby activation, rman incomplete recovery)                                                                         
(one-by-one/single-scn/ddl-only/resetlogs) [single-scn]                                           

What data instantiation script to create?
dp_networklink : Data Pump with network link. No export datafile is created (APPLY.sh)
dp_exp         : Data Pump with export datafile. Creates an export datafile (APPLY.sh)
exp            : Pre-datapump exp/imp with export datafile (APPLY.sh)
ddl_file       : DDL file created (APPLY.sql)
ddl_run        : DDL is automatically executed on target
load           : All replicated data is created and loaded automatically 
none                                                                                                                                                                      
(dp_networklink/dp_exp/exp/ddl_file/ddl_run/load/none) [dp_networklink] 

Following replication pairs are now configured:
1: ttorcl_src (Oracle) ==> ttorcl_trg (Oracle), DDL: yes, fetcher: no, process suffix: (no suffix), compression: no, encryption: no, network timeout: 60, prepare type:
single-scn, data load: dp_networklink
Enter number of replication pair to modify it, or "add", or "done": [done] 

Step 3 - Replicated tables
========================================
The third step is to choose the schemas and tables to be replicated. If the databases are reachable, the tables are checked for existence, datatype support, etc.,
schemas are queried for tables. Note that all messages are merely hints/warnings and may be ignored if issues are rectified before the scripts are actually executed.
Following tables are defined for replication pairs:
1: ttorcl_src (Oracle) ==> ttorcl_trg (Oracle), DDL: yes, suffix: (no suffix), prepare: single-scn
  No tables defined.
Enter number of replication pair to modify it, or "done": [1]

Please enter list of all individual tables to be replicated. Enter schema name(s) only to replicate all tables in that schema. Use comma or space to delimit the entries.
Enter the tables and schemas: [] oe                                                                                                                                       
Selected schemas: OE

You can also specify some advanced options:
1. Rename schemas or tables.
2. Specify filtering conditions.
3. (Tables only) Configure Change Data Capture; this does not maintain a copy of the source table, but logs all operations as separate entries. This is useful for ETL or
as an audit trail. This usually requires adding of new columns (timestamps, old/new values etc.) to the target table.
Specify rename name or filter condition for any of the specified schemas (YES/NO): [no] 

Following tables are defined for replication pairs:
1: ttorcl_src (Oracle) ==> ttorcl_trg (Oracle), DDL: yes, suffix: (no suffix), prepare: single-scn
  OE(tables)
Enter number of replication pair to modify it, or "done": [done]                                                                                                          

Step 4 - Process configuration
========================================
The fourth step is to configure the replication processes for each replication.
Following processes are defined:
1: MINE on ttorcl_src
  Not configured.
2: APPLY on ttorcl_trg
  Not configured.
Enter number of process to modify it, or "done": [1]  

Enter number of process to modify it, or "done": [1]                                                                                                                      

Following processes are defined:
1: MINE on ttorcl_src
  Host: source, SMTP: no, SNMP: no
2: APPLY on ttorcl_trg
  Not configured.
Enter number of process to modify it, or "done": [2]                                                                                                                      

Run this script now? (yes/no) [NO]