Task

Comment

Completed?

1.    

Oracle software is installed on primary server.

The location of the Oracle software is called the ORACLE_HOME

2.    

Oracle Production Database is up and running.

Ensure Database is in ARCHIVELOG mode. 

3.    

Oracle Standby Database has been created and is up and running.

To create a standby Database, please see Appendix A

4.    

Either rsh or ssh is installed and configured.

Please make sure you can connect between the primary and standby server without a password or passphrase.

To configure ssh or rsh, please see Appendix B and C in the Dbvisit User Manual

5.    

Decide which Unix or Linux user will install and run Dbvisit. It is recommended that this user is the same as the Oracle software owner.

This user must have permission to logon to the database as sysdba.

Ensure that this user exists on the standby server as well.

6.    

Decide where to install Dbvisit. Recommended location is /usr/local/dbvisit. Create this directory on the primary server and set the correct ownership.

To setup the correct ownership use the following command:

chown oracle:dba /usr/local/dbvisit

This assumes oracle is the Oracle software owner and dba is the Oracle software owner group.

7.    

Create the Dbvisit install directory (see above) on the standby server and set the correct ownership.

This directory has to be the same as on the primary server.

To setup the correct ownership use the following command:

chown oracle:dba /usr/local/dbvisit

This assumes oracle is the Oracle software owner and dba is the Oracle software owner group.

8.    

External compression software is installed on both the primary and the standby server.

This can be compress, or gzip, or any other compression software. Both servers must have the same compression method installed.

9.    

Sendmail is configured to send external emails on both the primary and standby server for notifications.

10. 

There is an entry for the database (or instance) in the oratab file.

The oratab file is located as /etc/oratab or /var/opt/oracle/oratab, other locations are also possible.

The oratab file is used by the Oracle supplied oraenv script to set the correct environment for the database. Dbvisit uses oraenv to set the environment.

11. 

Add Dbvisit installation directory to the PATH variable on both primary and standby database.

Edit the .profile or .bash_profile and add:

PATH=$PATH:/usr/local/dbvisit

export PATH

Note: this is not absolutely necessary, but avoids having to specify the directory when running Dbvisit interactively.

12. 

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:

/oracle/orabase

Example of admin directory for database dbvisitp would be:

/oracle/orabase/admin/dbvisitp

The ORACLE_BASE is only used by Dbvisit during installation 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 will be kept.

13. 

Ensure KornShell is available (only on Solaris)

This is done by checking if file /bin/ksh exists:

ls -al /bin/ksh

Only necessary on Solaris.