The complete installation and configuration should take less than 30 minutes. This page provides a quick overview of the installation and configuration process. For a more detailed installation process that lists all the steps involved and describes each step please see the Dbvisit Installation and Users Guide (4.0).

Ensure all prerequisites are met before continuing with installation. It is recommended that Dbvisit is installed and run as the Oracle software user.

RAC environment

In an Oracle RAC environment, Dbvisit must be installed as below on each primary node in the RAC cluster. However when running dbvisit_setup:

1. On the first node a new installation must be done. Choose option 1 in the main dbvisit_setup menu.
2. On the second and subsequent nodes only the Dbvisit database environment file needs to be created. The Dbvisit database environment file will have the name of the instance. Choose option 2 in the main dbvisit_setup menu.
3. If the Dbvisit Archive Log Module is to be installed on the second and subsequent nodes, then option 3 needs to be run in the dbvisit_setup menu.

On the primary server only (or primary RAC node)

1. Copy the installation file dbvisit40.tar to the install (/usr/local/dbvisit) directory.
2. Change directory to the installation directory (/usr/local/dbvisit).
3. Untar the file:

/usr/local/dbvisit/> tar xvf dbvisit40.tar

      Where /usr/local/dbvisit/ >   is the prompt of the OS showing the current directory.

4. Ensure the files are executable:

/usr/local/dbvisit/> chmod 750 *

5. Edit the configuration file. This only requires changing if the default variables are not acceptable :

/usr/local/dbvisit/> vi dbv.env

6. Run the Dbvisit setup utility on the primary server and follow the instructions on the screen.

/usr/local/dbvisit/> dbvisit_setup

7. Once the setup is completed, Run Dbvisit on the primary server (this will automatically install Dbvisit on the standby server):

/usr/local/dbvisit/> dbvisit dbvisitp ====================================================== Dbvisit Standby Database technology dbvisit started on dbvisit11: 05:19:04 PM 07/31/2006 ======================================================   Log file(s) for dbvisitp will be transferred from dbvisit11 to dbvisit12... 200607281719 - 1 Log transfer(s) for dbvisitp completed.                Last sequence was 157.   ====================================================== dbvisit ended on dbvisit11: 05:19:13 PM 07/31/2006 ======================================================

Where dbvisitp is the name of the database.

8. Run Dbvisit on the standby server:

/usr/local/dbvisit/> dbvisit dbvisitp ====================================================== Dbvisit Standby Database technology dbvisit started on dbvisit12: 12:27:20 PM 07/31/2006 ======================================================   Log file(s) for dbvisitp from dbvisit11 will be applied to dbvisit12... 200607311227 - Log seq 154 applied to standby        database dbvisitp. 200607311227 - Log seq 155 applied to standby        database dbvisitp. 200607311227 - Log seq 156 applied to standby        database dbvisitp. 200607311227 - Log seq 157 applied to standby        database dbvisitp.   ====================================================== dbvisit ended on dbvisit12: 12:27:34 PM 07/31/2006 ======================================================

Where dbvisitp is the name of the database.

9. Schedule Dbvisit on the primary (schedule separate on each RAC node) and standby server with cron (or other scheduling software):

# Dbvisit - Standby Database Technology 00,10,20,30,40,50 * * * * /usr/local/dbvisit/dbvisit dbvisitp >/tmp/dbvisit.dbvisitp 2>&1

Where dbvsitp  is the name of the Database and Dbvisit is installed in the /usr/local/dbvisit directory

            Dbvisit installation completed.