Versions Compared

Key

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

Dbvisit Replicate supports One-to-many replication and this can be specified during the setup wizard.
During Step 1 of the setup wizard, more databases can be added. In the following example, there are 3 databases added:

Section
Column
width5%

 

Column
width95
panel No Format
bgColorCCC
Step 1 - Describe databases


========================================


The first step is to describe databases used in the replication. There are 
usually 
usually 
two of them (source and target); however, there can be just one (when


source and target is the same) or more than two (one-to-many or other 
complex 
complex 
configurations.)
 
 
Following databases are now configured:


1: Oracle orcl, SYS/**, SYSTEM/*, dbvrep/**, USERS/TEMP, dbvrep/, ASM:YES


2: Oracle test11202, SYS/**, SYSTEM/*, dbvrep/**, USERS/TEMP, dbvrep/, ASM:NO


3: Oracle dbvisit210_d112f, SYS/**, SYSTEM/*, dbvrep/**, USERS/TEMP, dbvrep/,
 
 
ASM:NO


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

 

During Step 2 of the setup wizard the configuration pairs can be specified. In this example, orcl is the source database and test11202 and dbvisit210_d112f are the target databases.

Section
Column
width5%

 

Column
width95
Panel No Format
bgColorCCC
Step 2 - Replication pairs


========================================


The second step is to set source and targets for each replication pair. This 
is 
is 
usually just choosing the first database as source and the second one as


target, but many more configurations are possible.
 
 
Following replication pairs are now configured:


1: orcl (Oracle) ==> test11202 (Oracle), DDL: yes, fetcher: no, process suffix: (
no 
no 
suffix), network: LAN


2: orcl (Oracle) ==> dbvisit210_d112f (Oracle), DDL: yes, fetcher: no, 
process 
process 
suffix: 1, network: LAN


Enter number of replication pair to modify it, or "add", or "done": [done]

 

During Step 4 of the setup wizard the processes configuration of each server has to be specified:

Section
Column
width5%

 

Column
width95
Panel No Format
bgColorCCC
Step 4 - Process configuration


===Following processes are defined:


1: MINE on orcl


Host: rac11202node1, SMTP: YES, SNMP: NO


2: APPLY on test11202


Host: dbvisit400, SMTP: YES, SNMP: NO


3: MINE1 on orcl


Not used, work done by MINE.


4: APPLY1 on dbvisit210_d112f


Host: dbvisit210, SMTP: YES, SNMP: NO


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

 

Note that the mine process MINE is shared for both the apply processes APPLY and APPLY1. The process MINE1 is not used because it is more efficient to only use 1 mine process (MINE) for all the target databases.
The Next steps (Nextsteps.txt) displayed when the setup wizard has completed will show the actions to be taken for each server and will include the steps that need to run for all target databases.