Versions Compared

Key

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

...

No Format
bgColorCCC
Step 2 - Replication pairs
========================================
The second step is to set source and targets for each replication pair.
This is usually just choosing the first database as source and the second one as target,
but many more configurations are possible.
Let's configure the replication pair, selecting source and target.
Following databases are described:
1: orcl_dbvisit210SDB11 (Oracle)  
2: orcl_dbvisit230TDB11 (Oracle)  
Select source database: [1]                                                                                                                                                   
Select target database: [2]                                                                                                                                                   
Will be DDL replication enabled? (If YES, the script will grant more privileges to
the Dbvisit Replicate users and enable database-wide supplemental logging): [yes] [yes]                                                                                                                                        
Use fetcher to offload the mining to a different server? (yes/no) [no]           (NETWORK_QUALITY) - Please specify your network type (LAN or WAN).
Autoconfigures timeouts, use of compression etc. [LAN]
                                                                                             
Would you like to encrypt the data across the network (yes or no) [no]                                                                                                        
Would you like to compress the data across the network (yes or no) [no]                                                                                                       
How long do you want to set the network timeouts. Recommended range between 60-300 seconds [60]                                                                               
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: orcl_dbvisit210 (Oracle) ==> orcl_dbvisit230 (Oracle), DDL: yes, fetcher: no, process suffix: (no suffix), compression: no, encryption: no, network: LAN
Enter "1" timeout: 60, prepare type: single-scn, data load: dp_networklink
Enter number of replication pair to modify it, or "add", or "done": [done]