The Dbvisit Standby upgrade process in Version 9 will be similar to the process in earlier versions. There are a number of pre-requisites before upgrading:
Prior to performing any upgrades, it is recommended to make sure you have sufficient backups. This is good practice for any software upgrade.
This can easily be done by just backing up the DBVISIT_BASE folder prior to installing the new version.
Before starting the upgrade process, please make sure all Dbvisit Standby schedules are stopped. |
Central Console (dbvserver) must be the same version as all the other components. We can not run dbvserver on a lower or higher version than dbvnet, dbvagent, and core. |
When upgrading from 9.0.08 to 9.0.10 we've made some changes to how Dbvisit Software obtains certificates. These parameters are removed from the conf files - dbvnet, dbvagent & dbvserver cert=conf/cert.pem prikey=conf/prikey.pem ca=conf/ca.pem The software now looks for certificates in the default conf locations. If, however, a client wants to use their own certificates (different names & locations), they can still manually add these setting lines to the conf files. Existing customers with custom values in those lines should NOT have them cleared on upgrade. |
The rest of this section will take you through the upgrade process from Dbvisit Standby version 8.0.x to 9.0.x
On this page: |
Important Notes:
For creating a new Oracle RAC DDC files see the examples here
If you are using Dbvisit Standby 7.0.x you must first upgrade to Dbvisit Standby version 8 before you can upgrade to version 9.0.x. You can directly move to Version 9.0 by doing a fresh install and creating a fresh DDC file. Remember you don't have to re-create your standby database for moving Version 7.0.x to Version 9.0 if your standby already exists and is in sync.
For more details on upgrading from version 7.0.x to version 8.0.x please see the Dbvisit Standby version 8 documentation.
It is recommended to be on the latest update of Dbvisit Standby version 8 prior to upgrading to version 9.
The upgrade process consists of two key steps:
When upgrading from version 8.0.x, the process is easy and should only take a few minutes.
The high level recommended steps are:
The section below will show you a detailed example of the upgrade process.
The first example shows the upgrade process for the Dbvisit Standby version 8 core components which include - Dbvnet, Dbvagent and the Standby Core CLI.
The steps followed below are:
Stop the Dbvisit components. Check the processes running and by running ps -ef |grep dbv which would list out processes that are running and you can stop them. Below is the example for stopping the Dbvisit components from both primary and standby. We have our dbvserver installed in the standby server in this example.
Primary: dbvel71 Standby: dbvel72 Stopping the components in Primary: [oracle@dbvel71 standby]$ ps -ef |grep dbv oracle 4620 1 0 18:33 ? 00:00:00 ./dbvnet -d start oracle 4629 1 0 18:33 ? 00:00:00 ./dbvagent -d start oracle 6374 1 0 18:46 ? 00:00:00 ./dbvctl -d ORCLCDB -D start oracle 6681 3951 0 18:51 pts/0 00:00:00 grep --color=auto dbv [oracle@dbvel71 standby]$ pwd /usr/dbvisit/standby [oracle@dbvel71 standby]$ ./dbvctl -d ORCLCDB -D stop Stopping Dbvisit Daemon... Successfully stopped. [oracle@dbvel71 standby]$ cd ../dbvnet/ [oracle@dbvel71 dbvnet]$ ./dbvnet -d stop Stop signal has been sent to pid: 4620 [oracle@dbvel71 dbvnet]$ cd ../dbvagent/ [oracle@dbvel71 dbvagent]$ ./dbvagent -d stop Stop signal has been sent to pid: 4629 [oracle@dbvel71 dbvagent]$ cd ../standby/ [oracle@dbvel71 standby]$ ps -ef |grep dbv oracle 6760 3951 0 18:52 pts/0 00:00:00 grep --color=auto dbv [oracle@dbvel71 standby]$ Stopping the components in the Standby: [oracle@dbvel72 standby]$ ps -ef |grep dbv oracle 4899 1 0 18:34 ? 00:00:00 ./dbvnet -d start oracle 4907 1 0 18:34 ? 00:00:00 ./dbvagent -d start oracle 4982 1 0 18:35 ? 00:00:02 ./dbvserver -d start oracle 7878 1 0 18:46 ? 00:00:00 ./dbvctl -d ORCLCDB -D start oracle 8510 3902 0 18:53 pts/0 00:00:00 grep --color=auto dbv [oracle@dbvel72 standby]$ ./dbvctl -d ORCLCDB -D stop Stopping Dbvisit Daemon... Successfully stopped. [oracle@dbvel72 standby]$ cd ../dbvnet/ [oracle@dbvel72 dbvnet]$ ./dbvnet -d stop Stop signal has been sent to pid: 4899 [oracle@dbvel72 dbvnet]$ cd ../dbvagent/ [oracle@dbvel72 dbvagent]$ ./dbvagent -d stop Stop signal has been sent to pid: 4907 [oracle@dbvel72 dbvagent]$ cd ../dbvserver/ [oracle@dbvel72 dbvserver]$ ./dbvserver -d stop Stop signal has been sent to pid: 4982 [oracle@dbvel72 dbvserver]$ ps -ef |grep dbv oracle 8550 3902 0 18:54 pts/0 00:00:00 grep --color=auto dbv [oracle@dbvel72 dbvserver]$ |
Backup the Dbvisit Standby installation directory (optional - but recommended)
In this example, we will backup the /usr/dbvisit directory using the "tar" command to create a backup in a backup folder called /home/oracle/backup. You can use the "du -sh" command to confirm the /usr/dbvisit directory size prior to backup. The "tar" command used in this case will use the -z option to enable compression.
[oracle@dbvel71 dbvisit]$ pwd /usr/dbvisit [oracle@dbvel71 dbvisit]$ du -sh . 232M . [oracle@dbvel71 dbvisit]$ tar czf /home/oracle/backup/dbvisit_backup_29May2019.tar.gz . [oracle@dbvel71 dbvisit]$ ls -lrt /home/oracle/backup/dbvisit_backup_29May2019.tar.gz -rw-r--r--. 1 oracle oinstall 68702946 May 28 18:57 /home/oracle/backup/dbvisit_backup_29May2019.tar.gz [oracle@dbvel71 dbvisit]$ |
If you have a regular backup schedule the above backup process might not be required. Backing up the full directory is not strictly required, the most important files are located in /usr/dbvist/standby/conf/ which is the DDC files and their respective repositories. It is recommended to have at minimum at least a backup of this folder. |
Now that the required process is stopped and a backup is created, you can continue with the upgrade process.
The example below shows you the steps as discussed above:
[oracle@dbvel71 9.0]$ pwd /home/oracle/9.0 [oracle@dbvel71 9.0]$ ls dbvisit-standby9.0.0_1399_gf162ef6c-el6.zip [oracle@dbvel71 9.0]$ unzip dbvisit-standby9.0.0_1399_gf162ef6c-el6.zip Archive: dbvisit-standby9.0.0_1399_gf162ef6c-el6.zip inflating: dbvisit-standby9.0.0_1399_gf162ef6c-el6.tar [oracle@dbvel71 9.0]$ tar xf dbvisit-standby9.0.0_1399_gf162ef6c-el6.tar [oracle@dbvel71 9.0]$ ls dbvisit dbvisit-standby9.0.0_1399_gf162ef6c-el6.tar dbvisit-standby9.0.0_1399_gf162ef6c-el6.zip INSTALL.txt README.txt [oracle@dbvel71 9.0]$ cd dbvisit [oracle@dbvel71 dbvisit]$ cd installer/ [oracle@dbvel71 installer]$ ls install-dbvisit [oracle@dbvel71 installer]$ ./install-dbvisit ----------------------------------------------------------- Welcome to the Dbvisit software installer. ----------------------------------------------------------- It is recommended to make a backup of our current Dbvisit software location (Dbvisit Base location) for rollback purposes. Installer Directory /home/oracle/9.0/dbvisit >>> Please specify the Dbvisit installation directory (Dbvisit Base). The various Dbvisit products and components - such as Dbvisit Standby, Dbvisit Dbvnet will be installed in the appropriate subdirectories of this path. Enter a custom value or press ENTER to accept default [/usr/dbvisit]: > /usr/dbvisit DBVISIT_BASE = /usr/dbvisit ----------------------------------------------------------- Component Installer Version Installed Version ----------------------------------------------------------- standby 9.0.0_1399_gf162ef6c 8.0.26_0_g3fdeaadd dbvnet 9.0.0_1399_gf162ef6c 8.0.26_0_g3fdeaadd dbvagent 9.0.0_1399_gf162ef6c 8.0.26_0_g3fdeaadd dbvserver 9.0.0_1399_gf162ef6c not installed ----------------------------------------------------------- What action would you like to perform? 1 - Install component(s) 2 - Uninstall component(s) 3 - Exit Your choice: 1 Choose component(s): 1 - Core Components (Dbvisit Standby Cli, Dbvnet, Dbvagent) 2 - Dbvisit Standby Core (Command Line Interface) 3 - Dbvnet (Dbvisit Network Communication) 4 - Dbvagent (Dbvisit Agent) 5 - Dbvserver (Dbvisit Central Console) - Not available on Solaris/AIX 6 - Exit Installer Your choice: 1 ----------------------------------------------------------- Summary of the Dbvisit STANDBY configuration ----------------------------------------------------------- DBVISIT_BASE /usr/dbvisit Press ENTER to continue ----------------------------------------------------------- About to install Dbvisit STANDBY ----------------------------------------------------------- NTF repo installed. Component standby installed. ----------------------------------------------------------- About to install Dbvisit DBVNET ----------------------------------------------------------- Copied file /home/oracle/9.0/dbvisit/dbvnet/dbvnet to /usr/dbvisit/dbvnet/dbvnet Copied file /usr/dbvisit/dbvnet/conf/dbvnetd.conf to /usr/dbvisit/dbvnet/conf/dbvnetd.conf.201905281908 DBVNET config file updated ----------------------------------------------------------- About to install Dbvisit DBVAGENT ----------------------------------------------------------- Copied file /home/oracle/9.0/dbvisit/dbvagent/dbvagent to /usr/dbvisit/dbvagent/dbvagent Copied file /usr/dbvisit/dbvagent/conf/dbvagent.conf to /usr/dbvisit/dbvagent/conf/dbvagent.conf.201905281908 DBVAGENT config file updated ----------------------------------------------------------- Component Installer Version Installed Version ----------------------------------------------------------- standby 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvnet 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvagent 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvserver 9.0.0_1399_gf162ef6c not installed ----------------------------------------------------------- What action would you like to perform? 1 - Install component(s) 2 - Uninstall component(s) 3 - Exit Your choice: 3 >>> Installation completed Install log /tmp/dbvisit_install.log.201905281900. [oracle@dbvel71 installer]$ |
Before you upgrade any DDC files - please make sure that you have upgraded both the Primary and Standby Dbvisit Standby software and that if you are using Dbvnet and the Dbvagent components that you start them prior to performing the upgrade. To test the status of network connectivity please see this section Dbvisit Standby Networking - Dbvnet#Dbvnet-5.TestingDbvnetCommunication |
The next step is to update the Dbvisit Standby Configuration (DDC) files which are located in DBVISIT_BASE/standby/conf directory. Before doing the below step please start all components from both primary and standby.
From Primary: [oracle@dbvel71 installer]$ cd /usr/dbvisit/ [oracle@dbvel71 dbvisit]$ cd dbvnet/ [oracle@dbvel71 dbvnet]$ ./dbvnet -d start Dbvnet daemon started. [oracle@dbvel71 dbvnet]$ cd ../dbvagent/ [oracle@dbvel71 dbvagent]$ ./dbvagent -d start Dbvagent daemon started. From Standby: [oracle@dbvel72 installer]$ cd /usr/dbvisit/ [oracle@dbvel72 dbvisit]$ cd dbvnet/ [oracle@dbvel72 dbvnet]$ ./dbvnet -d start Dbvnet daemon started. [oracle@dbvel72 dbvnet]$ cd ../dbvagent/ [oracle@dbvel72 dbvagent]$ ./dbvagent -d start Dbvagent daemon started. [oracle@dbvel72 dbvagent]$ cd ../dbvserver/ [oracle@dbvel72 dbvserver]$ ./dbvserver -d start Dbvserver daemon started. [oracle@dbvel72 dbvserver]$ |
During this upgrade process, the original DDC file will automatically be backed up with a date-timestamp suffix.
The command to upgrade the DDC files is: ./dbvctl -d <DDC> -o upgrade
The Below command must be run from the Primary Database Server |
[oracle@dbvel71 standby]$ ./dbvctl -d ORCLCDB -o upgrade ============================================================= Dbvisit Standby Database Technology (9.0.0_1399_gf162ef6c) (pid 8729) dbvctl started on dbvel71: Tue May 28 19:22:37 2019 ============================================================= >>> DDC file ORCLCDB version: 8.0.26 >>> DDC file ORCLCDB upgraded to version 9.0.0. >>> Dbvisit Database repository (DDR) ORCLCDB upgraded. ============================================================= dbvctl ended on dbvel71: Tue May 28 19:22:37 2019 ============================================================= [oracle@dbvel71 standby]$ ls -lrt conf/ total 144 -rw-r--r--. 1 oracle oinstall 23130 May 28 19:18 dbv_ORCLCDB.env.201905281922 -rw-r--r--. 1 oracle oinstall 8876 May 28 19:20 dbv_message.html -rw-r--r--. 1 oracle oinstall 8872 May 28 19:20 dbv_error.html -rw-r--r--. 1 oracle oinstall 28672 May 28 19:20 dbv_notify.db -rw-r--r--. 1 oracle oinstall 24709 May 28 19:22 dbv_ORCLCDB.env -rw-r--r--. 1 oracle oinstall 37888 May 28 19:22 orclcdb.db [oracle@dbvel71 standby]$ |
After the upgrade is completed you have to apply the version 9.0 license from the Primary before we can start sending and applying logs.
[oracle@dbvel71 standby]$ ./dbvctl -d ORCLCDB -l 4jo70-qwp4l-7gplh-g1cld-0ozd6-0tacd-k5q01 ============================================================= Dbvisit Standby Database Technology (9.0.0_1399_gf162ef6c) (pid 8907) dbvctl started on dbvel71: Tue May 28 19:25:25 2019 ============================================================= =>Update with license key: 4jo70-qwp4l-7gplh-g1cld-0ozd6-0tacd-k5q01? <Yes/No> [Yes]: yes >>> Dbvisit Standby License License Key : 4jo70-qwp4l-7gplh-g1cld-0ozd6-0tacd-k5q01 customer_number : 0 dbname : expiry_date : 2019-06-12 os : sequence : 1 software_features : 00000000 status : VALID updated : YES version : 9 ============================================================= dbvctl ended on dbvel71: Tue May 28 19:25:28 2019 ============================================================= [oracle@dbvel71 standby]$ |
This section will show you the upgrade process for the Dbvisit Standby version 9 Central Console (Dbvserver).
The process is similar to the upgrading of the core components, but in this case, the Dbvserver component will be selected for installation (upgrade).
Prior to upgrading the Dbvserver component, it is required to first stop Dbvserver if it is already running followed by a backup of the installation destination (Dbvisit Base).
The steps are similar to what we have used earlier for Dbvnet and Dbvagent, the steps for Dbvserver is shown below:
Stop Dbvserver:
First, we confirm if the process is running, if it is we stop it using the "./dbvserver -d stop", followed by confirming no dbvserver processes are running.
[oracle@dbv103 dbvisit]$ pwd /usr/dbvisit [oracle@dbv103 dbvisit]$ ps -ef|grep dbvserver|grep -v grep oracle 26664 0 0 22:25 ? 00:00:00 ./dbvserver -d start [oracle@dbv103 dbvisit]$ [oracle@dbv103 dbvisit]$ cd dbvserver [oracle@dbv103 dbvserver]$ ./dbvserver -d stop dbvserver attempt to stop pid: 26664 [oracle@dbv103 dbvserver]$ [oracle@dbv103 dbvserver]$ ps -ef|grep dbvserver|grep -v grep [oracle@dbv103 dbvserver]$ |
Backup the Dbvisit Standby installation directory (optional - but recommended)
In this example, we will backup the /usr/dbvisit directory using the "tar" command to create a backup in a backup folder called /backup. You can use the "du -sh" command to confirm the /usr/dbvisit directory size prior to backup. The "tar" command used in this case will use the -z option to enable compression.
[oracle@dbv103 dbvisit]$ pwd /usr/dbvisit [oracle@dbv103 dbvisit]$ tar czf /backups/usr_dbvisit.tar.gz . [oracle@dbv103 dbvisit]$ ls -al /backups/usr_dbvisit* -rw-r--r-- 1 oracle oinstall 3755257 Sep 5 22:27 /backups/usr_dbvisit.tar.gz [oracle@dbv103 dbvisit]$ |
We are now ready to perform the upgrade of the Central Console (Dbvserver).
Below are the example steps followed to upgrade the Dbvserver component:
[oracle@dbvel72 installer]$ ./install-dbvisit ----------------------------------------------------------- Welcome to the Dbvisit software installer. ----------------------------------------------------------- It is recommended to make a backup of our current Dbvisit software location (Dbvisit Base location) for rollback purposes. Installer Directory /home/oracle/9.0/dbvisit >>> Please specify the Dbvisit installation directory (Dbvisit Base). The various Dbvisit products and components - such as Dbvisit Standby, Dbvisit Dbvnet will be installed in the appropriate subdirectories of this path. Enter a custom value or press ENTER to accept default [/usr/dbvisit]: > DBVISIT_BASE = /usr/dbvisit ----------------------------------------------------------- Component Installer Version Installed Version ----------------------------------------------------------- standby 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvnet 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvagent 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvserver 9.0.0_1399_gf162ef6c 8.0.26_0_g3fdeaadd ----------------------------------------------------------- What action would you like to perform? 1 - Install component(s) 2 - Uninstall component(s) 3 - Exit Your choice: 5 ----------------------------------------------------------- Component Installer Version Installed Version ----------------------------------------------------------- standby 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvnet 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvagent 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvserver 9.0.0_1399_gf162ef6c 8.0.26_0_g3fdeaadd ----------------------------------------------------------- What action would you like to perform? 1 - Install component(s) 2 - Uninstall component(s) 3 - Exit Your choice: 1 Choose component(s): 1 - Core Components (Dbvisit Standby Cli, Dbvnet, Dbvagent) 2 - Dbvisit Standby Core (Command Line Interface) 3 - Dbvnet (Dbvisit Network Communication) 4 - Dbvagent (Dbvisit Agent) 5 - Dbvserver (Dbvisit Central Console) - Not available on Solaris/AIX 6 - Exit Installer Your choice: 5 ----------------------------------------------------------- About to install Dbvisit DBVSERVER ----------------------------------------------------------- Copied file /home/oracle/9.0/dbvisit/dbvserver/dbvserver to /usr/dbvisit/dbvserver/dbvserver Copied file /usr/dbvisit/dbvserver/conf/dbvserver.conf to /usr/dbvisit/dbvserver/conf/dbvserver.conf.201905281921 DBVSERVER config file updated ----------------------------------------------------------- Component Installer Version Installed Version ----------------------------------------------------------- standby 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvnet 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvagent 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c dbvserver 9.0.0_1399_gf162ef6c 9.0.0_1399_gf162ef6c ----------------------------------------------------------- What action would you like to perform? 1 - Install component(s) 2 - Uninstall component(s) 3 - Exit Your choice: 3 >>> Installation completed Install log /tmp/dbvisit_install.log.201905281921. |
Important: Prior to installing Dbvisit Standby version 9 on Windows, please make sure you have performed the pre-requisite steps prior to starting the installer - Installing Dbvisit Standby#2.5.WindowsEnvironmentPre-requisites
In this section, we will review the process to upgrade an existing Dbvisit Standby version 8 installation to the latest version 9. It is recommended that before you perform the upgrade process that you have the Dbvisit Standby version 8 already at the latest version 8 update.
When upgrading a Windows-based installation, there are only a few key steps to follow. In summary, the installer will ask for the Dbvisit Base location to install the Dbvisit Software. If you already have an installation, please make sure you select the existing installation folder as the destination. The installer will detect that a version is already installed and will perform the upgrade - replacing the version 8 executable files with the new version 9.
The first step to stop any schedules if you have any configured.
The example below shows the disabling of a Windows scheduled task. Select the task, right click and select disable.
If you are using Daemon service, Please stop the daemon process in both Primary and Standby
Below screenshot will provide the status of the daemon service.
4. Start the Installer by running (double click) the dbvisit-standby9.0.0-win64.exe file
The installer will start shortly. By default the installer will have the Dbvagent, Dbvnet and Standby CLI selected. Note that the Dbvserver (Central Console) is not selected. This is intentional as it is recommended to have the Dbvserver component installed on its own system. However, if required you can install the central console as part of the installation, but be advised that this is not recommended(We need to select it for this example as we have installed the dbvserver in standby). If the primary or standby system running the Central Console is down due to a disaster, you will not be able to access the Dbvisit Standby version 9 GUI. The installation process is similar to the Dbvisit Version 8.0.x installation process. The Dbvnet, Dbvagent and the Dbvserver configurations are updated and the services are started.
5. Once the above step is completed. Run the upgrade command from the Primary dbvctl.exe -d <DDC> -o upgrade . This has to be done before starting the daemon process in both primary and standby.
6. Apply the version 9 license key before starting the daemon service from Primary.
7. Now run the Archivelog send/apply manually and then start the daemon process for the automatic process to take over.
The steps performed are common for both Linux and Windows, After the CLI upgrade the GUI repository needs to updated with the latest DDC information.
1. Open the browser and type in the console address to view the version 9.0 GUI interface and to check the DDC file go to Manage Configurations page.
2. The DDC should still show the old version and allow you to click on the status to upgrade to the Version 9.0 release.
3. After the above step, you should see the current version of Dbvisit Standby and also the status showing a tick mark.
4. Post upgrade the Database Actions screen with Time Gap displayed between Primary and Standby (This will be displayed only after the first send and apply of archivelogs).
IMPORTANT: Please make sure that you have upgraded both primary and standby Dbvisit Standby software prior to upgrading the DDC files. This includes making sure Dbvnet is running on both systems.
For more detail on network communication please see - Dbvisit Standby Networking - Dbvnet#Dbvnet-5.TestingDbvnetCommunication
In Windows, you may have to delete the old daemon service, install it and start it, please see Dbvisit Standby Scheduling
https://dbvisit.com/blog/upgrade-dbvisit-standby-v8-v9-linux
https://dbvisit.com/blog/upgrade-dbvisit-standby-v8-v9-windows