...
- MINE - APPLY
- MINE1 - APPLY1
Configuring 2-way replication
2-way replication can be configured through the setup wizard. To configure 2-way replication, two replication pairs have to be setup. The default in the setup wizard is to configure only 1 pair.
Example configuring 2-way replication
In this example we have setup two databases: orcl and test11202.
At step 2 in the setup wizard, the replication pairs are configured.
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| 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 (Oracle)
2: test11202 (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]
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]
Lock and copy the data initially one-by-one or at a single SCN? (one-by-one/single-scn/ddl-only/resetlogs) [single-scn]
What data copy script to create? (dp_networklink/dp_exp/exp/ddl_file/ddl_run) [dp_networklink] Following replication pairs are now configured:
1: orcl (Oracle) ==> test11202 (Oracle), DDL: yes, fetcher: no, process suffix: (no suffix), network: LAN, prepare type: single-scn, data load:
dp_networklink Enter number of replication pair to modify it, or "add", or "done": [done] |
|
|
Add another replication pair, by typing "add" instead of "done". Choose the reverse source and target database:
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| Enter number of replication pair to modify it, or "add", or "done": [done] add
Let's configure the replication pair, selecting source and target.
Following databases are described:
1: orcl (Oracle)
2: test11202 (Oracle)
Select source database: [1] 2
Select target database: [2] 1
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]
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]
Lock and copy the data initially one-by-one or at a single SCN? (one-by-one/single-scn/ddl-only/resetlogs) [single-scn]
What data copy script to create? (dp_networklink/dp_exp/exp/ddl_file/ddl_run) [dp_networklink] Following replication pairs are now configured:
1: orcl (Oracle) ==> test11202 (Oracle), DDL: yes, fetcher: no, process suffix: (no suffix), network: LAN, prepare type: single-scn, data load:
dp_networklink
2: test11202 (Oracle) ==> orcl (Oracle), DDL: yes, fetcher: no, process suffix: 1, network: LAN, prepare type: single-scn, data load: dp_networklink
Enter number of replication pair to modify it, or "add", or "done": [done] |
|
|
Two replication pairs are now configured.