oracle@dbvrlin301[/home/oracle/7.0/dbvisit/installer]: ./install-dbvisit

-------------------------------------------------------------------------------
 Welcome. Your Dbvisit product is going to be installed in a moment.
 It will be required by you to enter some configuration parameters
 during installation.
-------------------------------------------------------------------------------
 It is recommended to make a backup of our current Dbvisit software
 location for rollback purposes.
>>> INSTALLATION DIRECTORY
 Please specify the Dbvisit main installation directory.
 The default directory is "/usr/dbvisit".
 Note: the various Dbvisit products and components - such as Standby,
 Replicate, Dbvnet, and Dbvserver - will be installed in the appropriate
 subdirectories of this path.
 Enter a custom value or press ENTER to accept default [/usr/dbvisit]:
 > /usr/dbvisit

-------------------------------------------------------------------------------
 ABOUT TO CONFIGURE: DBVISIT STANDBY
-------------------------------------------------------------------------------
 Dbvisit Standby is Dbvisit's disaster recovery software for your
 Oracle database.
>>> ORACLE USER NAME
 Please specify the Oracle user name on this server.
 The default user name is "oracle".
 Note: you must be logged in as the Oracle user to run Dbvisit installer.
 Custom value or ENTER for default [oracle]:
 > oracle

-------------------------------------------------------------------------------
 ABOUT TO CONFIGURE: DBVISIT DBVNET
-------------------------------------------------------------------------------
 Dbvisit Dbvnet is Dbvisit's network transportation software which
 provides network connectivity for all Dbvisit products. Dbvnet is a
 persistent daemon software that must be running on both the primary
 and standby servers at all times.
>>> DBVNET PORT NUMBER
 Please specify the listening port number for Dbvnet on this server.
 The default port number used by Dbvnet is 7890. You may choose any
 value between 1024 and 65535.
 Note: if you can not access this port after the installation has
 finished, then please double-check your server's firewall settings
 to ensure the selected port is open.
 Custom value or ENTER for default [7890]:
 > 7890

>>> DBVNET PASSWORD
 Please specify a password to encrypt all network data transmissions
 between servers in your network on which Dbvisit software is running.
 The default password is "admin".
 Custom value or ENTER for default [admin]:
 > admin

>>> DBVNET START AFTER INSTALLATION
 Please specify whether or not Dbvnet should be started when the
 installer has finished.
 The default setting is "yes".
 Custom value or ENTER for default [yes]:
 > yes

-------------------------------------------------------------------------------
 ABOUT TO CONFIGURE: DBVISIT DBVSERVER
-------------------------------------------------------------------------------
 Dbvisit Dbvserver is Dbvisit's web server software that provides a web
 interface for all Dbvisit products. Dbverver is a also a daemon that
 must be running on both servers if you wish to use its built-in
 command scheduler or control Dbvisit software through your web
 browser.
>>> DBVSERVER WEB PROTOCOL
 Please specify the web protocol to be used by Dbvserver on this server.
 Dbvserver supports both the HTTP and HTTPS web protocols. HTTP sends
 plain text messages across the network and should therefore be used
 on local networks only.
 The default web protocol is "https".
 If unsure, select HTTPS which safely encrypts all network transmissions.
 Custom value or ENTER for default [https]:
 > https

>>> DBVSERVER PORT NUMBER
 Please specify the listening port number for Dbvserver on this server.
 The default port number used by Dbvserver is 8081 for HTTP and 8443
 for HTTPS. You may choose any value between 1024 and 65535.
 Note: if you can not access this port after the installation has
 finished, then please double-check your server's firewall settings
 to ensure the selected port is open.
 Custom value or ENTER for default [8443]:
 > 8443

>>> DBVSERVER USER
 Please specify a user name to be used to access Dbvserver through
 your web browser later on.
 Note: this is a virtual user name, i.e. there is no corresponding
 system user account required.
 The default user name is "admin".
 Custom value or ENTER for default [admin]:
 > admin

>>> DBVSERVER PASSWORD
 Please specify a login password for the user name you just entered.
 The default password is "admin".
 Custom value or ENTER for default [admin]:
 > admin

>>> DBVSERVER START AFTER INSTALLATION
 Please specify whether or not Dbvserver should be started when the
 installer has finished.
 The default setting is "yes".
 Custom value or ENTER for default [yes]:
 > yes

>>> AUTOMATIC ERROR NOTIFICATION
 In order to improve both the Dbvisit web interface and the network
 transport layer, an automatic email can be sent to Dbvisit support
 when a run-time issue is detected by Dbvserver or Dbvnet.
 Note: information pertaining to Dbvserver and Dbvnet is sent only,
 and the information is solely used to improve our software.
 The default setting is "yes".
 Custom value or ENTER for default [yes]:
 > yes

>>> AUTOMATIC ERROR EMAIL ADDRESS
 What email address should be used to send automatic error notifications
 to? Usually, they are sent to a special Dbvisit error collection address.
 However, you may use your own support email address to receive error
 notifications first, and then forward them to Dbvisit support later in
 case there is a serious issue.
 Note: the Dbvisit notification address below can not be used for support
 enquiries. Manual email sent to this address will be ignored. Please open
 a support ticket on the support desk (http://www.dbvisit.com/servicedesk)
 if you are facing any difficulties.
 The default email address is "bugtrack700@dbvisit.com".
 Custom value or ENTER for default [bugtrack700@dbvisit.com]:
 >

-------------------------------------------------------------------------------
 Thank you. Configuration is complete. Installation will commence now.
-------------------------------------------------------------------------------
>>> Installing Standby - the Dbvisit disaster recovery software...
 Installing product files...

 Updating and migrating existing DDC files in /usr/dbvisit...
 > Removing old DDC files with appended timestamps
 Updating and migrating existing DDC files in /usr/dbvisit/standby...
 > Removing old DDC files with appended timestamps
 Removing old product files...
 Dbvisit Standby installation complete.

>>> Installing Dbvnet - the Dbvisit network layer...

>>> Adjusting init script templates for product dbvnet...
 Please find some init script templates in the following directory:
 /usr/dbvisit/dbvnet/conf/init.d
 These templates will allow your Systems Administrator to automatically
 start Dbvserver after a database server reboot.
 Templates are available for Sun Solaris, IBM AIX, and the Linux flavours
 OpenSuSE, RedHat/Centos/Fedora & Debian/Ubuntu.

>>> Starting Dbvnet daemon, please wait...
 Dbvnet is up and running on the following ip address and port:
 niop://172.16.1.111:7890

>>> Installing Dbvserver - the Dbvisit web interface...

>>> Adjusting init script templates for product dbvserver...
 Please find some init script templates in the following directory:
 /usr/dbvisit/dbvserver/conf/init.d
 These templates will allow your Systems Administrator to automatically
 start Dbvserver after a database server reboot.
 Templates are available for Sun Solaris, IBM AIX, and the Linux flavours
 OpenSuSE, RedHat/Centos/Fedora & Debian/Ubuntu.

>>> Starting Dbvserver daemon, please wait...
 Dbvserver is up and running. Please point your browser to the
 following URL to log in to the Dbvisit web interface:
 https://172.16.1.111:8443
 Login user name is 'admin' (password 'admin')

>>> Dbvisit product and component installation is now complete.

>>> NEXT STEPS: CONFIGURE DBVISIT STANDBY VIA COMMAND LINE INTERFACE (CLI):
 cd /usr/dbvisit/standby
 ./dbvisit_setup
 Note: Dbvisit can also be configured and run through a (GUI) web browser.
 Dbvserver (dbvserverd) must be installed and started for this.

>>> IMPORTANT - PLEASE NOTE THE FOLLOWING REQUIREMENTS BEFORE CONTINUING:
 > The Dbvisit Standby, Dbvnet, and Dbvserver software must be installed
 on both the primary and standby servers.
 > For network communication between the primary and standby server
 via Dbvnet port number 7890 must not be blocked by your firewalls.
 > Dbvnet must be up and running on both the primary and standby servers
 at all times.
 > If you wish to use Dbvserver, the Dbvisit web interface, then please
 ensure port 8443 is open on your servers' firewalls, as well.

>>> Thank you for using Dbvisit software!

Dbvisit Standby considerations with RAC

The Dbvisit Standby Database Configuration file (DDC) created during the setup on each node will have the name of the instance and not the name of the database (dbv_oracle_instance.env).
Dbvisit Standby needs to be scheduled separately on each primary node. It is recommended that Dbvisit Standby is scheduled at different times on each node. For example:

node1 – Schedule every hour at 00, 15, 30, 45
node2 – Schedule every hour at 02, 17, 32, 47

The archive destination location on the standby node must be accessible by all standby nodes in the RAC standby cluster.

Dbvisit Standby RAC Takeover

If a RAC node fails and is unavailable, then Dbvisit Standby on another RAC node can automatically take over the log shipment from the failed node. The Dbvisit Standby RAC Takeover is controlled by the following variables in the dbv{_}oracle_instance.env file:

RAC_TAKEOVER
RAC_TAKEOVER_SID
RAC_TAKEOVER_FORCE

RAC_TAKEOVER:

• Yes = Dbvisit Standby (on this instance) will take over from another instance when that instance is unavailable.
• No = Dbvisit Standby (on this instance) will NOT take over from another instance when that instance is unavailable. 

RAC_TAKEOVER_FORCE:

• Yes = Dbvisit Standby (on this instance) will take over from another instance regardless of whether that instance is available or not.
• No = Dbvisit Standby (on this instance) will NOT take over from another instance unless the instance is not available and RAC_TAKEOVER = Yes. 

RAC_TAKEOVER_SID

• Specify the instance name that Dbvisit Standby processing should take over if that instance is unavailable.
• The instance name must be different to the current instance name.

Example - 2 Node Primary RAC configuration

If the RAC setup contains 2 nodes (racnode1, racnode2) with instance names RACDB1 and RACDB2, then:
On racnode1 the dbv_RACDB1.env will contain:

RAC_TAKEOVER_SID=RACDB2
RAC_TAKEOVER=Y

On racnode2 the dbv_RACDB2.env will contain:

RAC_TAKEOVER_SID=RACDB1
RAC_TAKEOVER=Y

This ensures that if either node is unavailable, the other node will takeover log shipment to the standby database(s).

Example - 3 Node Primary RAC Configuration

The RAC_TAKEOVER_SID is not too different with a 3 node set up, as for a 2, and you just specify the next node in the sequence in a rolling/circular fashion. So, if the RAC setup contains 3 nodes (racnode1, racnode2, racnode3) with instance names RACDB1, RACDB2 and RACDB3 then:

On racnode1 the dbv_RACDB1.env will contain:

RAC_TAKEOVER_SID=RACDB2
RAC_TAKEOVER=Y

On racnode2 the dbv_RACDB2.env will contain:

RAC_TAKEOVER_SID=RACDB3
RAC_TAKEOVER=Y

On racnode3 the dbv_RACDB3.env will contain:

RAC_TAKEOVER_SID=RACDB1
RAC_TAKEOVER=Y

This ensures that if a particular node is unavailable, the 'next' node will takeover log shipment to the standby database(s). And if there are more than 3 nodes in the RAC configuration then you just follow this same approach and specify the 'next' node, in a rolling/circular fashion.