...

Upgrading from version 5.3.x or 6.0.x or 7.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.

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 When upgrading, you will install Dbvisit Standby version 7 into the exact same location as what the current (older) version was installed. Example if you have version 6 installed in /usr/local/dbvisit you will need to make sure you select this same path when asked by the installer what the location (destination) is of the installation. The upgrade process is an in-place upgrade. Do not install Dbvisit Standby version 7 into a separate location, unless you plan to recreate the DDC files from scratch.

4. 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).

45. Existing 7.0 license keys are automatically applied to the new software.

56. 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.

67. 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

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)

The upgrade process is an "in-place" upgrade, meaning you install the version 7 software into the exact same location as your previous version.

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 .

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 your installation location. When Dbvisit Standby version 7 is installed, the installer will upgrade the required files in this location.

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

Stop your Dbvisit Standby schedules on all systems
Stop Dbvserver (GUI) if you are using it
Stop Dbvnet (Dbvisit Networking)
Download and Install the new Dbvisit Standby version 7 software which will be in a zip archive.
Extract the downloaded software into a temporary directory, example /home/oracle/7.0/ (this is just temporary, once the installation is complete, you can remove this directory)
Start the installer from the extracted download (making sure you select the previous versions, installation directory during installation)
Note that during the installation process if you are upgrading a previous installation, you must select the previous installation base directory for the DBVISIT_BASE.
Example, if you have Dbvisit Standby version 6 installed in /usr/local/dbvisit then you have to install version 7 in the same location.
During the installation, the version 6 DDC files located in DBVISIT_BASE/standby directory (example /usr/local/dbvisit/standby/dbv_PROD.env) will be upgraded to version 7 DDC files and will be copied to the new conf directory under the standby sub directory (example /usr/local/dbvisit/standby/conf/dbv_PROD.env)
Update the Dbvisit Standby Repository
Update the Dbvisit Standby Configuration files (Optional if you want to edit parameters as part of the upgrade)
Remove any old temporary files (*.dbv) that might be located in the DBVISIT_BASE/standby/tmp directory (example /usr/dbvisit/standby/tmp/)
Start Dbvserver and Dbvnet if you did not select the auto start during the installation of the new software
Start your Dbvisit Standby schedulesDbvisit Standby schedules
Once the installation is complete, you can remove the install files, example if you extracted the installer into /home/oracle/7.0/ you can remove this temporary directory.

The next section will provide a more detail overview of the upgrade steps to follow:

...

Note

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

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

Note
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 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 Dbvserver

To stop Dbvserver (the web based front-end), run the command "./dbvserverd stop" from the DBVISIT_BASE/dbvserver directory:

No Format
cd /usr/dbvisit/dbvserver ./dbvserverd stop

Stop Dbvnet

To stop Dbvnet (Dbvisit Network), run the command "./dbvnetd stop" from the DBVISIT_BASE/dbvnet directory:

No Format
cd /usr/dbvisit/dbvnet ./dbvnetd stop

Step 2: Download Latest Software

The next step is to download the latest available version if you have not already from the Dbvisit web site http://www.dbvisit.com

...

Code Block

language	text
align	left

oracle@dbvlin101[/home/oracle/7.0]: ls -l
total 44084
-rw-r--r-- 1 oracle oinstall 45089534 Aug 21 10:40 dbvisit-standby7.0.01_linux.zip

Step 3: Extract Software

The next step is to extract the software downloaded in the previous step as well as updating the install-dbvisit file permission to allow the execution option.

...

Code Block

language	text
align	left

oracle@dbvlin101[/home/oracle/7.0]: unzip dbvisit-standby7.0.01_linux.zip
Archive:  dbvisit-standby7.0.01_linux.zip
  inflating: dbvisit-standby7.0.01.tar
  inflating: README.txt
  inflating: online_user_guide_reference.txt
oracle@dbvlin101[/home/oracle/7.0]: ls -l
total 109844
-rw-r--r-- 1 oracle oinstall 45089534 Aug 21 10:40 dbvisit-standby7.0.01_linux.zip
-rw-rw-rw- 1 oracle oinstall 67165696 Aug 19 18:10 dbvisit-standby7.0.01.tar
-rw-rw-rw- 1 oracle oinstall      393 Jul 10 23:21 online_user_guide_reference.txt
-rw-rw-rw- 1 oracle oinstall    87875 Aug 19 14:17 README.txt
oracle@dbvlin101[/home/oracle/7.0]: tar -xf dbvisit-standby7.0.01.tar
oracle@dbvlin101[/home/oracle/7.0]: ls -l
total 109848
drwxr-xr-x 6 oracle oinstall     4096 Aug 21 10:50 dbvisit
-rw-r--r-- 1 oracle oinstall 45089534 Aug 21 10:40 dbvisit-standby7.0.01_linux.zip
-rw-rw-rw- 1 oracle oinstall 67165696 Aug 19 18:10 dbvisit-standby7.0.01.tar
-rw-rw-rw- 1 oracle oinstall      393 Jul 10 23:21 online_user_guide_reference.txt
-rw-rw-rw- 1 oracle oinstall    87875 Aug 19 14:17 README.txt

Note that once the installation is finished you can remove this temporary directory.

Step 4: Running the Dbvisit Installer

The next step in the process is to start the Dbvisit Standby installer. Once you have extracted the tar archive, you will notice a new "dbvisit" directory.

...

Code Block

language	text

oracle@dbvlin101[/home/oracle]: ps -ef|grep dbvisit |grep -v grep
oracle    6410     1  0 Aug21 ?        00:00:01 /usr/dbvisit/dbvnet/dbvnetd
oracle    6411  6410  0 Aug21 ?        00:00:00 /usr/dbvisit/dbvnet/dbvnetd
oracle    6414  6410  0 Aug21 ?        00:00:00 /usr/dbvisit/dbvnet/dbvnetd
oracle    6415  6410  0 Aug21 ?        00:00:00 /usr/dbvisit/dbvnet/dbvnetd
oracle    6416  6410  0 Aug21 ?        00:00:00 /usr/dbvisit/dbvnet/dbvnetd
oracle    6431     1  0 Aug21 ?        00:00:01 /usr/dbvisit/dbvserver/dbvserverd
oracle    6432  6431  0 Aug21 ?        00:00:00 /usr/dbvisit/dbvserver/dbvserverd
oracle    6434  6431  0 Aug21 ?        00:00:01 /usr/dbvisit/dbvserver/dbvserverd
oracle    6436  6431  0 Aug21 ?        00:00:00 /usr/dbvisit/dbvserver/dbvserverd

Step 5: Repeat Installation on Standby Server

Dbvisit Standby needs to be installed on the Primary server as well as on the Standby server.

Before you continue with the next step you need to make sure you follow Step 1 to 4 above on all the servers in the standby configuration. When doing this, it is important to make sure the Dbvnet password provided during installation is the same on all the servers where you are installing Dbvnet. This password is used for secure communication and if different passwords are used between the primary and standby servers, you will not be able to establish a connection between these servers using Dbvnet.

Step 6: Testing Dbvnet Communication

Once you have Dbvisit Standby installed on all the servers, it is important to make sure that the communication between the Primary and Standby servers are working. This can be done by making use of the Dbvnet Test utility provided with the Dbvisit Standby installation - dbvnet-test, which is located under the dbvnet sub directory. When using the default path this utility will be in /usr/dbvisit/dbvnet/dbvnet-test

...

To perform a basic status check which confirms that the primary and standby server can communicate using Dbvnet:
- dbvnet-test [-s|--status] SERVER SERVER[:PORT]
To perform a more detail check, testing network connectivity, you can run the following:
- dbvnet-test [-f|--fulltest] SERVER TMPDIR SERVER:PORT

For more detail on Dbvnet and troubleshooting please see - Dbvisit Standby Networking (Dbvnet and SSH)

In the example below, dbvlin101 is the primary server and dbvlin102 is the standby server. Dbvisit Standby was installed using default values and no additional configuration has been performed at this stage. Dbvnet and Dbvserver is running on both nodes, but only Dbvnet is required and used for these tests:

...

Code Block

language	text

oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnet-test -f /tmp dbvlin102:7890
 
>>> Determining Dbvnet status on server dbvlin102:7890...
    Dbvnet on server dbvlin102:7890 is running.
 
>>> Running file transfer round trip on server dbvlin102:7890...
    Creating file '/tmp/dbvnet-test.tmp' containing 10 MB of data... - done.
 
  > Transferring 'dbvnet-test.tmp' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [260911046 KB/s] - done.
 
  > Retrieving file "dbvnet-test.tmp" from server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [459911209 KB/s] - done.

    Comparing checksums: all three checksums (local/remote/local) are
identical. File   identical. File transfer round trip finished successfully.

...

You should run the above tests from both the primary and standby servers to ensure communication between primary and standby servers can be established. Once this is done you can continue to the next step which is the creation of a Dbvisit Standby Database Configuration (DDC) file.

Step 7: Accessing the GUI (Dbvserver)

If you selected to install the Dbvserver (GUI) and allowed the auto start option during the installation process you should now be able to connect to the web based GUI interface.

...

If you followed the above steps you should now have Dbvisit Standby installed on both your primary and standby servers.

Step 8: Updating the Dbvisit Standby Repository and Dbvisit Configuration files

When upgrading the Dbvisit Standby version from 5.3.x or 6.0.x to version 7 you will only need to update the Dbvisit Standby Repository, but not the Dbvisit Database Configuration (DDC) files, as they would have been upgrade as part of the software installation (upgrade) process.

If you are upgrading an existing version 7.0.x installation, you only need to update the Dbvisit Standby Repository. The DDC file would have been already converted to a version 7 DDC file and no steps will be required - unless explicitly mentioned in the update release notes.

Step 8.1 - Updating the Dbvisit Database Configuration (DDC) file - (Optional)

This step is optional if you want to edit parameters as part of the upgrade - otherwise this step, if already on a version 7.0.x release is not needed

...

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

...

Following the above steps the current DDC file will be upgraded.

Step 8.2 - Updating the Dbvisit Standby Repository

Note

Oracle RAC Configurations - You only need to perform this step on one of the primary nodes.

Single Instance Configuration - This step is only performed on the primary server

...

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.

...

Panel

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 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.

...

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.

Step 11: Clean up the temporary files (the downloaded install files)

If you extracted the installer into a temporary location, example /home/oracle/7.0, you can now remove this as it is no longer required.

Versions Compared

Old Version 18

New Version Current

Key

Table of Contents

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

Upgrade Steps

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

Stopping the Schedules

Stop Dbvserver

Stop Dbvnet

Step 2: Download Latest Software

Step 3: Extract Software

Step 4: Running the Dbvisit Installer

Step 5: Repeat Installation on Standby Server

Step 6: Testing Dbvnet Communication

Step 7: Accessing the GUI (Dbvserver)

Step 8: Updating the Dbvisit Standby Repository and Dbvisit Configuration files

Step 8.1 - Updating the Dbvisit Database Configuration (DDC) file - (Optional)

Step 8.2 - Updating the Dbvisit Standby Repository

Step 9: Completing the upgrade

Step 10: Restarting your Schedules

Step 11: Clean up the temporary files (the downloaded install files)

Page Comparison

Versions Compared

Old Version 18

New Version Current

Key

<span class="diff-html-changed" data-a11y-before="Start of changed content" data-a11y-after="End of changed content" id="changed-diff-0">[data-colorid=</span>

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

Upgrade Steps

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

Stopping the Schedules

Stop Dbvserver

Stop Dbvnet

Step 2: Download Latest Software

Step 3: Extract Software

Step 4: Running the Dbvisit Installer

Step 5: Repeat Installation on Standby Server

Step 6: Testing Dbvnet Communication

Step 7: Accessing the GUI (Dbvserver)

Step 8: Updating the Dbvisit Standby Repository and Dbvisit Configuration files

Step 8.1 - Updating the Dbvisit Database Configuration (DDC) file - (Optional)

Step 8.2 - Updating the Dbvisit Standby Repository

Step 9: Completing the upgrade

Step 10: Restarting your Schedules

Step 11: Clean up the temporary files (the downloaded install files)