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 | ||
|---|---|---|
| ||
|
| width | 95 |
|---|
| bgColor | CCC |
|---|
Start > Dbvisit Replicate Command Consoledbvrep>
dbvrep> setup wizard
On Windows, the Dbvisit Replicate processes are by default installed as services and run as LOCAL SYSTEM.
| Note |
|---|
If multiple processes run in the same host (two APPLY(APPLY,APPLY1) or one MINE and one APPLY) . The host names become case sensitive in setup wizard so we have to retain the same case , if not we risk over writing the startup files created during the setup wizard . This behaviour is seen specifically in WINDOWS. |
On Linux/UNIX (tar file):
| Section |
|---|
| Column | ||
|---|---|---|
| ||
|
| width | 95 |
|---|
| bgColor | CCC |
|---|
cd /usr/dbvisit/replicate (this may be different)
./dbvrep
dbvrep>
dbvrep> setup wizard
On Linux (rpm file):
| Section |
|---|
| Column | ||
|---|---|---|
| ||
|
| width | 95 |
|---|
| bgColor | CCC |
|---|
cd /home/oracle/dbvrep (this maybe different)
dbvrep
dbvrep>
dbvrep dbvrep> setupwizard
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.
...