...
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| SQL> select current_scn from v$database;
CURRENT_SCN
-----------
1007088
SQL> alter system switch logfile;
System altered. |
|
|
9. Backup archivelogs, so the theese backups can be are used to restore target database up to the SCN 1007088.
...
10. Copy these backupsets to the exact same location on target server.
...
12. Now, you can configure Dbvisit Replicate by running setup wizard normally on source server. Select 'resetlogs' as data instantiation method in step 2 of setup wizard.
| 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: reptest1 (Oracle)
2: reptest2 (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] resetlogs
What data copy script to create? (dp_networklink/dp_exp/exp/ddl_file/ddl_run/none) [none] Following replication pairs are now configured:
1: reptest1 (Oracle) ==> reptest2 (Oracle), DDL: yes, fetcher: no, process suffix: (no suffix), network: LAN, prepare type:
resetlogs, data load: none
Enter number of replication pair to modify it, or "add", or "done": [done] |
|
|
...