Page Comparison

Upgrading from version 5.3.x or 6.0.x to 7.0.x

Please note:

Upgrading from version 5.3.x or 6.0.x to 7.0.x

Please note:

1. Upgrading of Dbvisit Standby software needs to be done on both the primary server and standby servers.

...

The upgrade steps for Dbvisit Standby in a single or Oracle RAC configuration is the same.   Where different steps are required it will be highlighted.

The Dbvisit Standby version 7 installation use approximately 70MB of disk space, but as trace files and log files will be stored in this location, 200MB free space is the recommended minimum.  

In version 7 the default installation location is /usr/dbvisit.  We do recommend you use the default /usr/dbvisit or /usr/local/dbvisit.  This directory will be known as the Dbvisit Base directory from version 7.cluster (Oracle RAC) configuration are the same.   Where different steps are required this will be highlighted. 

When upgrading you will run the installation process exactly the exact same as how you would perform a new Installationinstallation, with the exception that you need to make sure you specify the location of the current Dbvisit Standby installation location.  Example during the installation, known as the Dbvisit Base directory.  For example, if you currently have Dbvisit Standby version 6 installed in /usr/local/dbvisit or /opt/dbvisit you will need to make sure that during the installation process that you specify this location as the your installation location.

On a high level the upgrade process can be seen as:

...

Step 1:  Stop your Dbvisit Standby schedules

All schedules should be disabled on all servers involved in the Dbvisit Standby configuration. 

• If you

...

• make use of the

...

• Unix CRON scheduler for Dbvisit, it is recommended to disable these schedules before performing the upgrade.

...

•  
• If you are using the Dbvisit Scheduler - available in the web based GUI, you will need to first login to the current GUI installation and disable all schedules on all primary and standby nodes.  The Scheduler menu can be found under the "Run" main menu option. 

Step 2:  Download Latest Software

...

...
...
>>> Installing Standby - the Dbvisit disaster recovery software...
    Installing product files...

    Updating and migrating existing DDC files in /usr/local/dbvisit...


    > Removing old DDC files with appended timestamps
    Updating and migrating existing DDC files in
    /usr/local/dbvisit/standby...


    > Migrating DDC file /usr/local/dbvisit/standby/dbv_testdb.env to
    /usr/local/dbvisit/standby/conf/dbv_testdb.env


    > Renaming old DDC file /usr/local/dbvisit/standby/dbv_testdb.env to
    /usr/local/dbvisit/standby/conf/dbv_testdb.env.v6


    > Removing old DDC files with appended timestamps
    Removing old product files...
 
..
..

Note regarding the upgrade of existing DDC files:

• As you can see from the above the installation process picked up that there are version 6 Dbvisit Configuration

...

• files (DDC) located in /usr/local/dbvisit/standby/dbv_testdb.env
• This file is then converted to a version 7 configuration (DDC) file and moved into the /usr/local/dbvisit/standby/conf/ directory.
• The original version 6 configuration file is renamed to dbv_testdb.env.v6 and moved also moved to the /usr/local/dbvisit/standby/conf directory.
• Once the installation and upgrade is complete you will end up with the following files in the /usr/local/dbvisit/standby/conf directory

...

• Note that any old backup DDC files with date timestamps as extensions (dbv_SID.dbv.yyyymmdd)  will be removed from the /usr/local/dbvisit/standby directory.

At this stage you should now have the Dbvisit Standby version 7 software installed and if you upgraded from version 5.0.x or 6.0.x your DDC files would have been upgraded as part of the installation process.  If you selected to auto start Dbvnet (Dbvisit Networking) and Dbvserver (GUI) you will have a number of Background processes running.  Below is example output listing these processes:

...

• To update the Dbvisit Database Configuration (DDC) file go to Home > Setup > Update Dbvisit > Update Configuration > select Database from drop-down menu and click Save Configuration.

 Using CLI to update DDC

...

• To update the Dbvisit Database Repository (DDR) file go to Home > Setup > Update Dbvisit > Manage Dbvisit Repository > select Database from drop-down menu and click Check Dbvisit Repository.

• If the DDR needs to be upgraded, select Upgrade Dbvisit Repository
• Repeat upgrade of DDC and DDR for all databases on this primary server.

...

oracle@dbvrlin301[/usr/dbvisit/standby]: ./dbvisit_setup

=========================================================

Dbvisit Standby Database Technology (7.0.01.11204)
 http://www.dbvisit.com

=========================================================

=>dbvisit_setup only needs to be run on the primary server.

  Is this the primary server? <Yes/No> [Yes]:
=========================================================
 Dbvisit Standby Database Technology (7.0.01.11204)
 http://www.dbvisit.com

 Dbvisit Database setup
 Default values will be shown in []

Options:
 1) New Dbvisit Database setup (combines options 2,3,4)
 1a) New Dbvisit RAC Instance setup (combines options 2,3,4)

 2) New Dbvisit Database configuration (DDC) file setup
 3) New Dbvisit Archive Management Module (AMM) setup
 4) New Dbvisit Database repository (DDR) setup

 5) Manage Dbvisit Database repository (DDR)
 6) Update Dbvisit Database configuration (DDC) file

 7) Create Standby Database (and template)
 8) Synchronize Standby Database

 9) Uninstall Dbvisit Database repository (DDR)
 E) Exit

=========================================================
Please enter choice : 5
=========================================================

Maintain Dbvisit Database repository (DDR)
 Default values will be shown in []

Options:
 1) Upgrade Dbvisit Database repository (DDR)
 2) Downgrade Dbvisit Database repository (DDR)
 3) Check version of Dbvisit Database repository (DDR)

 r) Return to main menu

=========================================================
Please enter choice : 3

------------------------------------------------------------------------------
=>Checking Dbvisit Database repository (DDR) version.

Choose database:

The following Oracle database(s) have a Dbvisit Database configuration (DDC)
file on this server:

DDC
 ===
1) TSTRAC1
2) Return to menu

Please enter choice : 1

Is this correct? <Yes/No> [Yes]: Yes
Database TSTRAC1 is up.

Dbvisit Database repository (DDR) version: 7.0
Dbvisit software version: 7.0

Dbvisit Database repository (DDR) up to date. No need to upgrade.

Please press <Enter> to continue...

=========================================================

Maintain Dbvisit Database repository (DDR)
 Default values will be shown in []

Options:
 1) Upgrade Dbvisit Database repository (DDR)
 2) Downgrade Dbvisit Database repository (DDR)
 3) Check version of Dbvisit Database repository (DDR)

 r) Return to main menu

=========================================================
Please enter choice :

Step 9:  Completing the upgrade

The last step in the upgrade process is to run Dbvisit Standby manually on the primary - if using Oracle RAC you should run Dbvisit Standby on ALL the primary nodes; once Dbvisit Standby was run on the primary server, run it on the standby server.  This step can be performed from either the command line or the GUI. 

Image Removed Through the command line interface (CLI) :  ./dbvisit <DDC>

...

 Select Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Default from Run Action drop-down menu > Run
Image Removed
 

...

 enter choice :

Step 9:  Completing the upgrade

The last step in the upgrade process is to run Dbvisit Standby manually on the primary. If using Oracle RAC you should run Dbvisit Standby on ALL the primary nodes; once Dbvisit Standby has been run on the primary server, run it on the standby server.  This step can be performed from either the command line or the GUI. 

Through the command line interface (CLI):

To run Dbvisit Standby from the command line, execute the following command first on the primary node followed by the running it on the standby server:   ./dbvisit <DDC>

Through the web based graphical user interface (GUI):

To execute Dbvisit (run it) from the GUI on the primary server, login as the admin user (default) and navigate to the “Run Interactive” screen:

• Select Home -> Run -> Run Interactive 
• Ensure you are on the primary tab, if not select it
• From the top drop down option, select the database 
• Select “Default (transfer archive log) option as your “Run Action”
• Click on Run
   

To execute Dbvisit (run it) from the GUI on the standby server, login as the admin user (default) and navigate to the “Run Interactive” screen:

• Select Home -> Run -> Run Interactive 
• Ensure you are on the standby tab, if not select it
• From the top drop down option, select the database 
• Select “Default (apply archive log) option as your “Run Action”

Once you have completed a successful run from both the primary and standby side, you can now move on to the final step, which is to re-enable your schedules.

Step 10:   Restarting your Schedules

Once you have completed the upgrade and you can run Dbvisit Standby successfully manually, you can re-enable your Dbvisit Standby schedules disabled in Step 1.