Installation Prerequisites

Task

Comment

Completed?

Oracle software is installed on primary server or for each node in Oracle RAC

The location of the Oracle software is called the ORACLE_HOME. In Dbvisit Standby this variable is also called ORACLE_HOME.

Oracle software is installed on standby server.

The location of the Oracle software is called the ORACLE_HOME. In Dbvisit Standby this variable is called ORACLE_HOME_DR.

Oracle Production database is up and running.
For Oracle RAC, ensure instance is running.

Ensure database is in ARCHIVELOG mode. To determine if database is in archive log mode run SQL command:
SQL> archive log list
Example output:
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/oraarch/dbvisitp
Oldest online log sequence 3959
..

The same user that installed Oracle software should be used to install Dbvisit Standby.

This user must have permission to logon to the database as sysdba.
The user should be a member of the Oracle DBA group (usually dba or ora_dba).
Ensure that this user exists on the standby server as well.

Dbvisit Standby uses email for alerting. Dbvisit Standby comes with its own mail client. The smtp server needs to be specified so that Dbvisit Standby knows where to send the emails to.
Sendmail can also be used for email. In this case, the smtp server is not required.

smtp server is usually in the format:
mail.<your companyname>.com

Although not strictly necessary, ensure that ORACLE_BASE is known. Ensure that the admin directory of the database (usually under the ORACLE_BASE) is known.
Example of ORACLE_BASE would be:
c:\oracle\orabase
Example of admin directory for database dbvisitp would be:
c:\oracle\orabase\admin\dbvisitp

The ORACLE_BASE is only used by Dbvisit Standby during setup to determine the location of the admin directories of the database.
A new directory called dbvisit will be created under the admin directory of the database. This will be where the log file of Dbvisit Standby is kept.

Ensure that the standby server name is known on the primary server.
Ensure that the primary server name is known on the standby server.

Try pinging the standby server. The ping does not have to be successful, but the host name should be resolved to an IP address.
On the primary server:
ping standby_server
PING standby_server (60.234.66.131) 56(84) bytes of data
On the standby server:
ping primary_server
PING primary_server (60.235.66.131) 56(84) bytes of data

Ensure that the firewall port is opened between the primary and the standby servers.

Default port will be with port 22 for ssh.
The default port can be changed by setting SSH_PORT.

If Dbvserver is being used to provide the web based interface to Dbvisit, then the Dbvserver http port needs to be opened on the firewall

Default http port is 8081.

In case either primary or standby databases use ASM storage, the user that installed Dbvisit Standby should be able to connect to the ASM instance as sysdba

The user should either:
a) be a member of the Oracle DBA group (usually dba or ora_dba) in case operating system authentication is used to access the ASM instance
or
b) be able to access the ASM instance using credentials of a user with SYSDBA privilege set up in the dbvisit configuration file, in case password authentication is used to access the ASM instance
If Oracle Grid infractructure implemented when the Grid user is different from the Oracle database owner, the user that installed Dbvisit Standby should have execute permission on SQLPLUS under Grid Oracle Home. This can be achieved though group permissions on the SQLPLUS executable.