...
- Describing the individual databases that are taking part in the replication.
- Setting up the replication pairs to determine which are the source and target databases.
- Choosing what to replicate, this can be tables and schemas.
- Process configuration which includes hostnames, port numbers and notification settings.
Starting the wizard
Login as the user that is going to run Dbvisit Replicate On Windows, the Dbvisit Replicate processes are by default installed as services and run as LOCAL SYSTEM. and start the Dbvisit Replicate Command Console and start the setup wizard:
On Windows:
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| Start > Dbvisit Replicate Command Console
dbvrep> setup wizard |
On Windows, the Dbvisit Replicate processes are by default installed as services and run as LOCAL SYSTEM. |
|
On Linux/UNIX (tar file):
(do not run as root)
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| cd /usr/dbvisit/replicate (this may be different)
./dbvrep
dbvrep> setup wizard |
|
|
On Linux (rpm file):
(do not run as root)
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| cd /home/oracle/dbvrep (this maybe different)
dbvrep
dbvrep> setup wizard |
|
|
The setup wizard is usually run on the source server, although this is not strictly necessary. However, it makes the built-in checking of directories and auto-detection of tnsnames.ora more useful. The setup scripts are created in user home directory (My Documents) – a subdirectory DDC_NAME is created. In this directory, sub-directories mine, mine_stage, apply, log and ddc_backup are created. These are used as defaults for various variable settings in DDC file and can be changed if needed.