During this step the source and target databases are set for each replication pair. More information about step-2 is available here
| No Format | ||
|---|---|---|
| ||
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_dbvisit210 (Oracle) 2: orcl_dbvisit230 (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] Following replication pairs are now configured: 1: orcl_dbvisit210 (Oracle) ==> orcl_dbvisit230 (Oracle), DDL: yes, fetcher: no, process suffix: (no suffix), network: LAN Enter "1" to modify or "done": [done] |