/
Upgrading Dbvisit Standby - Windows

Upgrading Dbvisit Standby - Windows

May 10, 2016

If upgrading from version 5.3.x or 6.0.x to 7.0.x

Please note the following if upgrading from earlier versions to version 7:

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

2. For Oracle RAC, the upgrade needs to be done for each node.

3. You may want to create a backup of the Dbvisit Standby install directory for rollback purposes. (all Dbvisit software is contained within the main directory).

4. Existing 7.0 license keys are automatically applied to the new software (this is if you are upgrading from a current version 7 update to a later update, example 7.0.10 to 7.0.50)

5. Existing 5.3.x and 6.0.x license keys are NOT valid for 7.0. Contact Dbvisit Sales to obtain 7.0 license keys if you have current Dbvisit support.  A support contract is required to obtain license keys for later versions of Dbvisit Standby.

6. Your current Dbvisit Database Configuration (DDC) configurations will be upgraded and a new configuration (DDC) file will be created.  A backup of the original DDC file will be created.

Upgrade Steps

Note that the following steps apply if you are upgrading from version 5.3.x or 6.0.x or 7.0.x to the latest version 7 update.  Example you would follow these upgrade steps if you are updating from 7.0.10 to 7.0.50.

The upgrade steps for Dbvisit Standby in a single or cluster (Oracle RAC) configuration are the same.   Where different steps are required this will be highlighted. 

Recommended:   Before starting the upgrade, it is recommended that the standby database is up to date with the primary database (this is not required, but recommended - all archive logs in the Dbvisit Standby ARCHDEST on the standby server should have been applied to the standby)

When upgrading you will run the installation process exactly the same as you would perform a new installation, with the exception that you need to make sure you specify the location of the current Dbvisit Standby installation during the installation, known as the Dbvisit Base directory.  For example, if you currently have Dbvisit Standby already installed in "C:\Program Files (x86)\dbvisit"  you will need to make sure that during the installation process that you specify this location as your installation location.  

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

  1. Stop your Dbvisit Standby schedules on all systems

  2. Stop Dbvserver (GUI) if you are using it

  3. Stop Dbvnet (Dbvisit Networking)

  4. Download and Install the new Dbvisit Standby version 7 (making sure you select the previous versions, installation directory during installation)

  5. Update the Dbvisit Standby Repository

  6. Update the Dbvisit Standby Configuration files (Only required if already on Version 7 and updating to a later version - 7.0.x)

  7. Recommended: remove any temp (*.dbv) files in the DBVISIT_BASE/standby/tmp directory

  8. Start Dbvserver and Dbvnet if you did not select the auto start during the installation of the new software

  9. Start your Dbvisit Standby schedules

The next section will provide a more detail overview of the upgrade steps.

In Dbvisit Standby version 7 the Archive logs are renamed when they are copied to the standby server (in the Dbvisit ARCHDEST location).

Before upgrading, make sure the standby have already applied all the archive logs that was available in the Dbvisit standby ARCHDEST.

New archive logs in this location will have the new naming convention:

 

<thread>_<sequence>_<resetlogs_id><STANDBY_ARCHIVELOG_NAME_EXTENSION>

 

Where STANDBY_ARCHIVELOG_NAME_EXTENSION defaults to .arc

Example: 1_45628_ 812975118.arc

 

Upgrading the Primary Server

This steps should be performed on all the primary servers if Oracle RAC is used

 

 

Step 1:  Stop your Dbvisit Standby schedules, Dbvserver (GUI) and Dbvnet

 

It is recommended that before you start the upgrade that the standby database are up to date with the primary database - meaning all archive logs in the Dbvisit Standby ARCHDEST on the standby server should be applied to the standby.

This is not a strict requirement, but recommended.

 

Stopping the Schedules

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

  • If you make use of the Windows scheduler for Dbvisit, it is recommended to disable/stop 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. 

 

If you are already making use of Dbvisit Standby version 7 and upgrading to a new update of version 7, please make sure you stop both Dbvserver (GUI) and Dbvnet (Networking) before you start the upgrade process.  

If you are upgrading from a version prior to version 7, example version 6.0.54 then you only need to stop Dbvserver (GUI) as Dbvnet was not part of previous releases.

Stop the Dbvisit Standby schedule(s) (If using the Dbvserver schedule, these will be automatically stopped).

It is recommended to stop the Dbvserver and Dbvnet (if previously installed) Windows Services prior to starting the upgrade process

 

Step 2: Start the Installer

Double click on the Dbvisit Standby installation executable. Click on Next when the Welcome screen is presented:

Step 3: Review and Accept the license terms.

Step 4: Review Installation Owner

Please ensure that the account that is used to install Dbvisit Standby is the same account that installed the Oracle software.

For Windows 2008 and higher it is recommended that the User Account Control (UAC) be turned off.  

 

Step 5: Choose Components to Install

For new Installations and Upgrades it is recommended to select all components in the list (Dbvnet, Dbvserver and Standby)

 

Step 6:  Installation Location

You will be prompted for the installation location for all components, known as the DBVISIT_BASE location in version 7.