Versions Compared

Old Version 2

changes.mady.by.user Anton Els

Saved on

compared with

New Version Current

changes.mady.by.user Anton Els

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

3. If any of the other standby database settings are different, these must be edited as well. The variables that can be changed are:

No Format
ORACLE_SID_DEST*

...

 
ORACLE_BASE_DR

...


LOGDIR_DR

...


ARCHDEST

...


MAX_TIMES_TRIED

...


LEAVE_COMPRESS_DEST

...


ADD_DATAFILE

 

    For a multiple standby database on the same node the ORACLE_SID_DEST must be different unique

...

6. On each standby server, Dbvisit Standby needs to be scheduled. Note that the correct DDC file needs to be specified.

Note
titleWindows Only

The Dbvisit Standby software and SSH software must be installed on the second standby server. Dbvisit Standby for Windows includes the Bitvise SSH environment with public and private keys. In order to configure this successfully for all standby servers please follow the following steps.

  • Install Dbvisit Standby on the second standby server.
  • Unselect the "System Readiness Check" from the installer.
  • Copy all the keys from the ssh2 directory on primary server to the same location on second standby server. This overwrites all the ssh2 keys from second standby with the keys from the primary server.
  • Start the Dbvisit Standby console on the second standby server. Type in the command:
    dbv_functions -Y standby setupssh
  • This loads the second standby server with the new ssh keys. All servers now have the same ssh keys, so that they can make contact with each other.
    • The ssh setup can be tested by running the following command on both the primary and the second standby server: dbv_functions -a system_readiness

    All servers that will be used (Primary server and all the standby servers).

    The Dbvnet Password must be the same on all nodes

    Creating multiple standby databases

    ...