Upgrading from version 5.2.x, 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.
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.
5. Existing 5.0.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.
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
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.
When upgrading you will run the installation process the exact same as how you would perform a new Installation, with the exception that you need to make sure you specify the current Dbvisit Standby installation location. 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 installation location.
On a high level the upgrade process can be seen as a 5 step process:
- 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 (making sure you select the previous versions, installation directory during installation)
- Update the Dbvisit Standby Repository
- Update the Dbvisit Standby Configuration files (Only required if already on Version 7 and updating to a later version - 7.0.x)
- Start Dbvserver and Dbvnet if you did not select the auto start during the installation of the new software
- Start your Dbvisit Standby schedules
The next section will provide a more detail overview of the upgrade steps.
Step 1: Stop your Dbvisit Standby schedules
If you are making use of the UNIX cron schedule it is recommended to disable these schedules before performing the upgrade. All schedules should be disable on all servers envolved in the Dbvisit Standby configruation.
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
The next step is to download the latest available version if you have not already from the Dbvisit web site http://www.dbvisit.com
If you are upgrading from version 5.0.x or 6.0.x to version 7 you will need to obtain a new license key from Dbvisit Sales team.
The upgrade free at no additional charge for support paying customers.
Once the software is downloaded, you can copy it to a temporary location on your server.
In this example, we create a temporary directory called 7.0 in /home/oracle and copy the software download into this directory.
We now have the following structure:
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.
First use "unzip" to uncompress the downloaded software package, followed by using the "tar -xf" command to extract the archive. The steps are shown below:
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
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.
In this directory you will find an "installer" directory which contains the installation script to be executed. Before executing this script you need to make it "executable". This can be done as follow:
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 oracle@dbvlin101[/home/oracle/7.0]: cd dbvisit oracle@dbvlin101[/home/oracle/7.0/dbvisit]: ls dbvnet dbvserver installer standby oracle@dbvlin101[/home/oracle/7.0/dbvisit]: cd installer oracle@dbvlin101[/home/oracle/7.0/dbvisit/installer]: ls -l total 2648 -rw-r--r-- 1 oracle oinstall 2707057 Aug 19 18:10 install-dbvisit oracle@dbvlin101[/home/oracle/7.0/dbvisit/installer]: chmod u+x install-dbvisit oracle@dbvlin101[/home/oracle/7.0/dbvisit/installer]: ls -l total 2648 -rwxr--r-- 1 oracle oinstall 2707057 Aug 19 18:10 install-dbvisit
Now that the install-dbvisit script has the correct permissions, you may execute this script to start the installer.
Below is the detail output of the installation process. In summary the following are performed
In most cases just accepting the default values are recommended:
- Start the installer using - ./install-dbvisit command
- Provide the DBVISIT_BASE directory - /usr/dbvisit (default)
- Confirm the Oracle Database software owner name - oracle (default)
- Specify the dbvnet port number - 7890 (default)
- Specify the dbvnet password used for secure communication between nodes - admin (default)
- Confirm if you want to auto start dbvnet after installation - yes (default)
- Specify the Dbvserver (GUI) protocol (http or https) - https (default)
- Confirm the default port number for Dbvserver (GUI) - 8443 (default for https)
- Specify the Dbvserver administrator user name - admin (default)
- Specify the Dbvserver administrator user password - admin (default)
- Confirm if you want to auto start Dbvserver after installation - yes (default)
- Do you want to allow error notification (bug tracking Dbvserver) - yes (default)
- Confirm bug tracking email address (bug tracking Dbvserver) - bugtrack700@dbvisit.com (default)
Below is an example installation process. At the end of this process the Dbvnet and Dbvserver background processes will be started automatically.
oracle@dbvlin101[/home/oracle/7.0/dbvisit/installer]: ./install-dbvisit
-------------------------------------------------------------------------------
Welcome. Your Dbvisit product is going to be installed in a moment.
It will be required by you to enter some configuration parameters
during installation.
-------------------------------------------------------------------------------
It is recommended to make a backup of our current Dbvisit software
location for rollback purposes.
>>> INSTALLATION DIRECTORY
Please specify the Dbvisit main installation directory.
The default directory is "/usr/dbvisit".
Note: the various Dbvisit products and components - such as Standby,
Replicate, Dbvnet, and Dbvserver - will be installed in the appropriate
subdirectories of this path.
Enter a custom value or press ENTER to accept default [/usr/dbvisit]:
> /usr/dbvisit
-------------------------------------------------------------------------------
ABOUT TO CONFIGURE: DBVISIT STANDBY
-------------------------------------------------------------------------------
Dbvisit Standby is Dbvisit's disaster recovery software for your
Oracle database.
>>> ORACLE USER NAME
Please specify the Oracle user name on this server.
The default user name is "oracle".
Note: you must be logged in as the Oracle user to run Dbvisit installer.
Custom value or ENTER for default [oracle]:
> oracle
-------------------------------------------------------------------------------
ABOUT TO CONFIGURE: DBVISIT DBVNET
-------------------------------------------------------------------------------
Dbvisit Dbvnet is Dbvisit's network transportation software which
provides network connectivity for all Dbvisit products. Dbvnet is a
persistent daemon software that must be running on both the primary
and standby servers at all times.
>>> DBVNET PORT NUMBER
Please specify the listening port number for Dbvnet on this server.
The default port number used by Dbvnet is 7890. You may choose any
value between 1024 and 65535.
Note: if you can not access this port after the installation has
finished, then please double-check your server's firewall settings
to ensure the selected port is open.
Custom value or ENTER for default [7890]:
> 7890
>>> DBVNET PASSWORD
Please specify a password to encrypt all network data transmissions
between servers in your network on which Dbvisit software is running.
The default password is "admin".
Custom value or ENTER for default [admin]:
> admin
>>> DBVNET START AFTER INSTALLATION
Please specify whether or not Dbvnet should be started when the
installer has finished.
The default setting is "yes".
Custom value or ENTER for default [yes]:
> yes
-------------------------------------------------------------------------------
ABOUT TO CONFIGURE: DBVISIT DBVSERVER
-------------------------------------------------------------------------------
Dbvisit Dbvserver is Dbvisit's web server software that provides a web
interface for all Dbvisit products. Dbverver is a also a daemon that
must be running on both servers if you wish to use its built-in
command scheduler or control Dbvisit software through your web
browser.
>>> DBVSERVER WEB PROTOCOL
Please specify the web protocol to be used by Dbvserver on this server.
Dbvserver supports both the HTTP and HTTPS web protocols. HTTP sends
plain text messages across the network and should therefore be used
on local networks only.
The default web protocol is "https".
If unsure, select HTTPS which safely encrypts all network transmissions.
Custom value or ENTER for default [https]:
> https
>>> DBVSERVER PORT NUMBER
Please specify the listening port number for Dbvserver on this server.
The default port number used by Dbvserver is 8081 for HTTP and 8443
for HTTPS. You may choose any value between 1024 and 65535.
Note: if you can not access this port after the installation has
finished, then please double-check your server's firewall settings
to ensure the selected port is open.
Custom value or ENTER for default [8443]:
> 8443
>>> DBVSERVER USER
Please specify a user name to be used to access Dbvserver through
your web browser later on.
Note: this is a virtual user name, i.e. there is no corresponding
system user account required.
The default user name is "admin".
Custom value or ENTER for default [admin]:
> admin
>>> DBVSERVER PASSWORD
Please specify a login password for the user name you just entered.
The default password is "admin".
Custom value or ENTER for default [admin]:
> admin
>>> DBVSERVER START AFTER INSTALLATION
Please specify whether or not Dbvserver should be started when the
installer has finished.
The default setting is "yes".
Custom value or ENTER for default [yes]:
> yes
>>> AUTOMATIC ERROR NOTIFICATION
In order to improve both the Dbvisit web interface and the network
transport layer, an automatic email can be sent to Dbvisit support
when a run-time issue is detected by Dbvserver or Dbvnet.
Note: information pertaining to Dbvserver and Dbvnet is sent only,
and the information is solely used to improve our software.
The default setting is "yes".
Custom value or ENTER for default [yes]:
> yes
>>> AUTOMATIC ERROR EMAIL ADDRESS
What email address should be used to send automatic error notifications
to? Usually, they are sent to a special Dbvisit error collection address.
However, you may use your own support email address to receive error
notifications first, and then forward them to Dbvisit support later in
case there is a serious issue.
Note: the Dbvisit notification address below can not be used for support
enquiries. Manual email sent to this address will be ignored. Please open
a support ticket on the support desk (http://www.dbvisit.com/servicedesk)
if you are facing any difficulties.
The default email address is "bugtrack700@dbvisit.com".
Custom value or ENTER for default [bugtrack700@dbvisit.com]:
>
-------------------------------------------------------------------------------
Thank you. Configuration is complete. Installation will commence now.
-------------------------------------------------------------------------------
>>> Installing Standby - the Dbvisit disaster recovery software...
Installing product files...
Updating and migrating existing DDC files in /usr/dbvisit...
> Removing old DDC files with appended timestamps
Updating and migrating existing DDC files in /usr/dbvisit/standby...
> Removing old DDC files with appended timestamps
Removing old product files...
Dbvisit Standby installation complete.
>>> Installing Dbvnet - the Dbvisit network layer...
>>> Adjusting init script templates for product dbvnet...
Please find some init script templates in the following directory:
/usr/dbvisit/dbvnet/conf/init.d
These templates will allow your Systems Administrator to automatically
start Dbvserver after a database server reboot.
Templates are available for Sun Solaris, IBM AIX, and the Linux flavours
OpenSuSE, RedHat/Centos/Fedora & Debian/Ubuntu.
>>> Starting Dbvnet daemon, please wait...
Dbvnet is up and running on the following ip address and port:
niop://172.16.1.111:7890
>>> Installing Dbvserver - the Dbvisit web interface...
>>> Adjusting init script templates for product dbvserver...
Please find some init script templates in the following directory:
/usr/dbvisit/dbvserver/conf/init.d
These templates will allow your Systems Administrator to automatically
start Dbvserver after a database server reboot.
Templates are available for Sun Solaris, IBM AIX, and the Linux flavours
OpenSuSE, RedHat/Centos/Fedora & Debian/Ubuntu.
>>> Starting Dbvserver daemon, please wait...
Dbvserver is up and running. Please point your browser to the
following URL to log in to the Dbvisit web interface:
https://172.16.1.111:8443
Login user name is 'admin' (password 'admin')
>>> Dbvisit product and component installation is now complete.
>>> NEXT STEPS: CONFIGURE DBVISIT STANDBY VIA COMMAND LINE INTERFACE (CLI):
cd /usr/dbvisit/standby
./dbvisit_setup
Note: Dbvisit can also be configured and run through a (GUI) web browser.
Dbvserver (dbvserverd) must be installed and started for this.
>>> IMPORTANT - PLEASE NOTE THE FOLLOWING REQUIREMENTS BEFORE CONTINUING:
> The Dbvisit Standby, Dbvnet, and Dbvserver software must be installed
on both the primary and standby servers.
> For network communication between the primary and standby server
via Dbvnet port number 7890 must not be blocked by your firewalls.
> Dbvnet must be up and running on both the primary and standby servers
at all times.
> If you wish to use Dbvserver, the Dbvisit web interface, then please
ensure port 8443 is open on your servers' firewalls, as well.
>>> Thank you for using Dbvisit software!
One key area to review are these lines indicating an upgrade from version 6 to version 7.
As you can see from the above the installation process picked up there are version 6 Dbvisit Configuration file (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 software installed and 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:
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 5 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 test communication between the primary and standby servers you can run the following recommended test commands:
- To perform a basic status check which confirms that the primary and standby server can communicate using Dbvnet:
- dbvnet-test [-s|--status] SERVER[:PORT]
- To perform a more detail check, testing network connectivity, you can run the following:
- dbvnet-test [-f|--fulltest] SERVER:PORT
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:
Test 1: Basic Status Check
oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnet-test -s dbvlin102:7890
>>> Determining Dbvnet status on server dbvlin102:7890...
Dbvnet on server dbvlin102:7890 is running.
Test 2: Full Test - 10MB file is copied (and verified) between primary and standby
oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnet-test -f 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% [2609 KB/s] - done.
> Retrieving file "dbvnet-test.tmp" from server dbvlin102:7890
Progress: 0%...20%...40%...60%...80%...100% [4599 KB/s] - done.
Comparing checksums: all three checksums (local/remote/local) are identical. File
transfer round trip finished successfully.
Stop and Start Dbvnet
Dbvnet can be stopped and started using the dbvnetd executable located in the dbvnet sub directory (example - /usr/dbvisit/dbvnet). Below is an example of stopping and starting the Dbvnet background processes:
oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnetd stop oracle@dbvlin101[/usr/dbvisit/dbvnet]: ps -ef|grep dbvnet oracle 12641 12446 0 09:20 pts/1 00:00:00 grep dbvnet oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnetd start oracle@dbvlin101[/usr/dbvisit/dbvnet]: ps -ef|grep dbvnet oracle 12643 1 0 09:20 pts/1 00:00:00 ./dbvnetd start oracle 12644 12643 0 09:20 pts/1 00:00:00 ./dbvnetd start oracle 12645 12643 0 09:20 pts/1 00:00:00 ./dbvnetd start oracle 12646 12643 0 09:20 pts/1 00:00:00 ./dbvnetd start oracle 12647 12643 0 09:20 pts/1 00:00:00 ./dbvnetd start oracle 12649 12446 0 09:20 pts/1 00:00:00 grep dbvnet
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.
To access this interface you can use http or https and the specified port you specified during installation. The default is https with port 8443 and you should be able to connect to the web based frontend using the following url: https://yourservername:8443
Example below is connecting to the GUI on dbvlin101 (172.16.1.111) using https and port 8443.
When asked for a username and password you need to provide the username and password specified during installation.
Summary
If you followed the above steps you should now have Dbvisit Standby installed on both your primary and standby servers.
You are now ready to move on to the next step which is to configure Dbvisit Standby.
11. The Dbvisit Standby configuration is next to be upgraded. Both the Dbvisit Database Configuration (DDC) file and Dbvisit Database Repository (DDR) needs to be upgraded. This can be done through the command line interface (CLI) indicated by 
or web based interface (GUI) indicated by 
12. Start browser and specify the URL given. Note the port number.
13. The Dbvisit Standby login screen will be displayed. The default username/password is admin/admin.
14. 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.
15. 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.
16. If the DDR needs to be upgraded, select Upgrade Dbvisit Repository
17. Repeat upgrade of DDC and DDR for all databases on this primary server.
18. Installation and upgrade complete. Please continue to Completing the upgrade below.
Alternative - command line interface (CLI) 
If it is not possible to access Dbvisit Standby through a browser, the command line interface (CLI) can also be used to upgrade the Dbvisit configurations.
19. 
To update the DDC and DDR through the command line interface, run dbvisit_setup.
/usr/dbvisit/standby/> dbvisit_setup
20. 
Choose options 6 to ensure all the latest parameters (or variables) are available in the Dbvisit Standby Database Configuration (DDC) file.
=========================================================
Dbvisit Standby Database Technology
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
9) Uninstall Dbvisit Database repository (DDR)
E) Exit
=========================================================
Please enter choice : 6
21. 
Choose for which database the updated applies.
=>Updating Dbvisit Database configuration (DDC) file.
For which database do you want to update the Dbvisit Database configuration
(DDC) file?
The following Oracle database(s) have a Dbvisit Database configuration (DDC)
file on this server:
SID
===
1) dbvisitp
2) Return to menu
Please enter choice : 1
Where dbvisitp is the database to be upgraded.
22. 
Dbvisit Standby will give the option to review all the variables. Choose No.
------------------------------------------------------------------------------
Would you like to review all the variables? <Yes/No> [Yes]: No
23. 
The new DDC file will now be created. The old DDC file will be renamed.
------------------------------------------------------------------------------
=>Writing Dbvisit Database configuration (DDC) file.
Dbvisit Database configuration (DDC) file
/usr/local/dbvisit/standby/dbv_dbvisitp.env already exists. Are you sure you want to
override? (a backup copy will be make) <Yes/No> [Yes]:
=>Dbvisit Database configuration (DDC) file
/usr/local/dbvisit/standby/dbv_dbvisitp.env renamed up to:
/usr/local/dbvisit/standby/dbv_dbvisitp.env.200901230925.
=>Dbvisit Database configuration (DDC) file
/usr/local/dbvisit/standby/dbv_dbvisitp.env updated.
Please press <Enter> to continue...
24. 
The main menu will be displayed again.
25. 
Choose option 5) Manage Dbvisit Standby Database repository (DDR).
26. 
Choose option 3) Check version of Dbvisit Standby Database repository (DDR).
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
27. 
Choose for which database the check applies.
------------------------------------------------------------------------------
=>Checking Dbvisit Database repository (DDR) version.
For which database do you want to check the Dbvisit Database repository (DDR)
version?
The following Oracle database(s) have a Dbvisit Database configuration (DDC) file
on this server:
SID
===
1) dbvisitp
2) dbvlx102
3) Return to menu
Please enter choice : 1
Is this correct? <Yes/No> [Yes]: Yes
Where dbvisitp is the database to be upgraded.
28. 
Dbvisit Standby will now indicate if the DDR is up to date.
Database dbvisitp is up.
Dbvisit Database repository (DDR) version: 5.3
Dbvisit software version: 5.3
Dbvisit Database repository (DDR) up to date. No need to upgrade.
Please press <Enter> to continue...
29. 
If Dbvisit Standby indicates that the DDR should be upgraded, then choose option 1 to upgrade.
30. Return to the main menu.
31. Repeat upgrade of DDC and DDR for all databases on this primary server.
32. Once the main menu is displayed again, choose e to exit out of main menu.
Completing the upgrade
33. Repeat above steps on all:
i. primary servers (including RAC nodes)
ii. standby (or secondary servers). However the DDC and DDR does not need to be upgraded on the standby servers.
34. Run Dbvisit Standby manually on the primary and standby server with the command to ensure correct functionality:
Through the command line interface (CLI) :
dbvisit <DDC>
Through the web based graphical user interface (GUI) 
:
Home > Run > Run Interactive > Primary Server tab > select Database from drop-down menu > select Default from Run Action drop-down menu > Run
Home > Run > Run Interactive > Standby Server tab > select Database from drop-down menu > select Default from Run Action drop-down menu > Run
35. Restart the Dbvisit Standby schedule (if using Dbvserver and this has been started, then the schedule will be automatically started).
Upgrade completed.
Upgrading from version 4.0 to 6.0
1. You may want to create a backup of the Dbvisit install directory for rollback purposes.
2. The Dbvisit 4.0 software needs to be removed including the DDC file.
3. Dbvisit Standby 6.0 can be installed as a new installation by following the steps in Dbvisit Standby installation (step 2) - Linux/Unix
4. A new DDC file will have to be created.
5. 
The existing DDR can be upgraded through the web based interface using Home > Setup > Update Dbvisit > Manage Repository and select Upgrade Dbvisit Repository.
6. 
The existing DDR can be upgraded through the command line interface, run dbvisit_setupand choose option 5).
/usr/local/dbvisit/standby/> dbvisit_setup
7. Existing 4.0 license keys are NOT valid for 6.0. Contact Dbvisit Sales to obtain 6.0 license keys if you have current Dbvisit support.