Upgrade from Version 9 or 10
This page will guide you through the process of upgrading Dbvisit Standby to version 12 from older versions 9 or 10.
- 1 1. Prerequisites
- 2 2. Linux Upgrade
- 2.1 2.1 Prepare installer files for upgrade
- 2.2 2.2 Stop dbvisit components and backup existing DBVISIT_BASE directory
- 2.3 2.3 Run version 12 dbvagentmanager installer to upgrade dbvisit on all primary and standby servers
- 2.4 2.4 Run version 12 dbvcontrol installer on dbvserver host
- 2.5 2.5 Importing v9 or v10 DDC file into dbvcontrol dashboard
- 3 3. Windows Upgrade
- 3.1 3.1 Stop dbvisit components and backup existing DBVISIT_BASE directory
- 3.2 3.2 Run version 12 dbvagentmanager installer to upgrade dbvisit on all primary and standby servers
- 3.3 3.3 Run version 12 dbvcontrol installer on dbvserver host
- 3.4 3.4 Importing v9 or v10 DDC file into dbvcontrol dashboard
- 3.5 3.5 Post Steps
- 4 4. Rollback Upgrade
1. Prerequisites
Before upgrading to version 12 you need to make sure that:
Version 12 uses completely different concept than version 9 or 10, ensure that you’re familiar with the differences:
you have valid version 12 Dbvisit StandbyMP key
The existing version 9 or 10 key will become invalid after upgrade and you must apply version 12 key in order for synchronization to continue after upgrade.
your standby database should be in sync with primary. In the dashboard you should see that your standby database is lagging only few minutes behind. For example this is how log gap report should look like in v10:
version 9 would look similar.
If your standby database is out of sync or has any other issues, we recommend to perform fresh v12 installation instead of upgrade and setup standby database from the scratch.
you have downloaded version 12 installer files to all servers where you want to upgrade Dbvisit. The latest available version can be downloaded from the Dbvisit web site https://www.dbvisit.com. Create temporary directory on the server to which you download the version 12 installer files
Determine existing DBVISIT_BASE and user running dbvisit components. On Linux you can do this by checking existing dbvagent, dbvnet and dbvserver process:
$ ps -ef | grep dbv oracle 1716772 1 0 17:37 ? 00:00:00 /usr/dbvisit/dbvnet/dbvnet -d start oracle 1716802 1 0 17:37 ? 00:00:00 /usr/dbvisit/dbvagent/dbvagent -d start oracle 1716831 1 0 17:37 ? 00:00:02 /usr/dbvisit/dbvserver/dbvserver -d startIn this example the DBVISIT_BASE is “/usr/dbvisit” and user is “oracle”.
On Windows, right click on dbvnet, dbvagent or dbvserver service (any of those will do) and choose properties. Refer to “Path to executable”:
In this example the DBVISIT_BASE is C:\Program Files\Dbvisit. On the “Log On” tab view and remember the user which runs the service:
In this example oracle user.
Dbvisit version 12 uses different ports than version 9 or 10. You need to make sure that your firewall rules are adjusted properly before the upgrade:
Default Ports | Dbvisit Standby Version 9.0.x and 10.x | Dbvisit StandbyMP |
|---|---|---|
7890 | Dbvnet | Dbvisit StandbyMP version 12 File transfer port |
7891 | Dbvagent | Not used in Dbvisit StandbyMP version 12 |
4433 | Dbvserver | Control center |
10853 | Observer | Not used in Dbvisit StandbyMP version 12 |
5533 | Not used in earlier versions | Dbvisit StandbyMP version 12 agentmanager port |
From the above table, you can see that ports 7891 and 10853 is no longer used and the new port used for agent manager is 5533.
If your current configuration is using an alternative copy and remote shell methods like SCP and SSH instead of Dbvnet then you need to switch back to Dbvnet before upgrading. Dbvisit Standby MP does not support these methods anymore. Before starting the upgrade process set the following in your DDC file:
RSH= <leave blank> CP= <leave blank> NETPORT=7890 NETPORT_DR=7890Delete old snapshots: If the current v9 or v10 configuration utilize the Snapshot functionality, you need to delete all Test/Dev snapshots and also Reportiing replica snapshots and configuration. For all the Snapshot Groups use the trash bin button to stop the snapshot generation and to delete all snapshots within the given Snapshot group. Optionally, you can delete the snapshot groups themselves. All of them will need to be created manually again after the upgrade is finished:
It is recommended to be on the latest update of Dbvisit Standby version 9 or 10 prior to upgrading to Dbvisit StandbyMP version 12.
2. Linux Upgrade
The upgrade consists of four main steps:
A. stop & backup existing version 9 and 10 components
B. run v12 installer and select existing Dbvisit Base for installation
C. startup v12
D. Import version 9 or 10 configuration and update licence key.
You must perform all upgrade steps below as user who run dbvisit components (typically oracle). You will need to upgrade dbvisit on all servers to complete the upgrade.
2.1 Prepare installer files for upgrade
Go to the temporary directory to which you downloaded the version 12 installer files. Make sure the ownership of the file is set to the same user who owns Dbvisit Base and extract the file:
chown oracle:oinstall standby-v12.1.0.tar.gz
tar -xzf standby-v12.1.0.tar.gzVerify you can now see two installer files:
-rwxr-xr-x. 1 oracle oinstall 197778472 Mar 27 23:03 install-agent-v12.1.0
-rwxr-xr-x. 1 oracle oinstall 66786142 Mar 27 23:01 install-control-v12.1.02.2 Stop dbvisit components and backup existing DBVISIT_BASE directory
Stop all Dbvisit components running on the server. There are three possible components: dbvnet, dbvagent and dbvserver. Dbvnet and dbvagent will be present on all database servers (primary and standby). Dbvserver will be present only on one database server or on separate host. To stop each component, run following commands:
/usr/dbvisit/dbvnet/dbvnet -d stop
/usr/dbvisit/dbvagent/dbvagent -d stop
/usr/dbvisit/dbvserver/dbvserver -d stopWe recommend to stop all dbvisit components on other servers which will be part of the upgrade at this point as well.
Cleanup existing directories in DBVISIT_BASE: standby/trace, standby/tmp, standby/gs. You can remove all files in those directories, as they are temporary only.
Backup existing DBVISIT_BASE directory, for example:
sudo su - oracle
mkdir /home/oracle/backup
cd /usr/dbvisit
cp -avr * /home/oracle/backupmake sure to create the backup, you will need to refer to it during upgrade
2.3 Run version 12 dbvagentmanager installer to upgrade dbvisit on all primary and standby servers
Perform this step on all primary and standby servers. This will install dbvagentmanager component only. Dbvagentmanager replaces dbvnet, dbvagent and standby core.
Run the version 12 installer from the temporary directory:
$ ./install-agent-v12.1.0You will need to respond to following prompts during installation:
Prompt | Example Value | Comment |
|---|---|---|
Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement? | Yes | Installation will proceed only with response “Yes” |
Which directory should the software be installed into? | /usr/dbvisit | Dbvisit Base directory you have identified during Prerequisites step |
Upgrade Dbvisit Standby from: 10.2.2_0_g06bd363f to v12.1.0? (Y/n) | Yes | Answer yes to perform upgrade on existing v9 or v10 dbvnet, dbvagent and standby core. Your current Dbvisit version will be displayed. |
Agent File Transfer Port: (7890) |
| Refer to backup dbvnet configuration file, in this example: /home/oracle/backup/dbvnet/conf/dbvnetd.confenter the same value as in line “listener_port” |
Fully Qualified Domain Name for this host: [? for help] (czlin0231) | czlin0231 | You need to enter hostname exactly as specified in DDC file. In this example: cat /home/oracle/backup/standby/conf/dbv_SLASH.env | grep "^SOURCE ="
cat /home/oracle/backup/standby/conf/dbv_SLASH.env | grep "^DESTINATION ="On primary server enter SOURCE value, on standby server enter DESTINATION value (case and domain sensitive). Note that your DDC file name will be different. The format is: dbv_<db_name>.env |
Fully Qualified Domain Name for the Control Center: | czlin0232 | Here you need to enter hostname of your dbvserver server. If dbvserver was running on standby server, enter the standby server hostname as specified in DDC file: cat /home/oracle/backup/standby/conf/dbv_SLASH.env | grep "^DESTINATION =" |
Agent Communications Port:(5533) | 5533 | This port is new in version 12, use with default vaule unless you specifically need to use different port. |
Passphrase: | Admin123 | passphrase used for encrypting communication between dbvagentmanagers and dbvcontrol. Must match on all hosts. There is no complexity requirement and there’s no dependency on version 9 or 10, you can choose any string. |
Example complete output of standby server upgrade (dbvserver was configured on standby server):
Directly after the installation of dbvagentmanager is finished, you have the option to create dbvagentmanager systemctl service by copying and running the last lines in the installer output:
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service install --user oracle
sudo /usr/dbvisit/standbymp/bin/dbvagentmanager service startThese commands need to be run with sudo or as root.
Creating systemctl service for dbvagentmanager will ensure dbvagentmanager will automatically startup after server reboot.
2.4 Run version 12 dbvcontrol installer on dbvserver host
Perform this step only on host where dbvserver was installed (typically standby host or in some cases different host from primary and standby). Dbvcontrol replaces dbvserver component.
Run the version 12 installer from the temporary directory:
$ ./install-control-v12.1.0You will need to respond to following prompts during installation:
Prompt | Example Value | Comment |
|---|---|---|
Please carefully read the end-user license agreement at https://dbvisit.com/eula. Do you agree to the terms of this agreement? | Yes | Installation will proceed only with response “Yes” |
Which directory should the software be installed into? | /usr/dbvisit | Dbvisit Base directory you have identified during Prerequisites step |
Upgrade Dbvisit Standby Web Server from: 10.2.2_0_g06bd363f to v12.1.0? Yes | Yes | Answer yes to perform upgrade on v9 or v10 dbvserver. Your current Dbvisit version will be displayed. |
Control Center Web Server Port: (4433) |
| Refer to backup dbvcontrol configuration file, in this example: /home/oracle/backup/dbvserver/conf/dbvserver.confenter the same value as in line “listener_port” |
Agent Communications Port: (5533) |
| This port is new in version 12, use with default vaule unless you specifically need to use different port. |
Passphrase: | Admin123 | passphrase used for encrypting communication between dbvagentmanagers and dbvcontrol. Must match on all hosts. There is no complexity requirement and there’s no dependency on version 9 or 10, you can choose any string. |
Example complete output of dbvserver host upgrade:
Directly after the installation of dbvcontrol is finished, you have the option to create dbvcontrol systemctl service by copying and running the last lines in the installer output:
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service install --user oracle
sudo /usr/dbvisit/standbymp/bin/dbvcontrol service startThese commands need to be run with sudo or as root.
Creating systemctl service for dbvcontrol will ensure dbvcontrol will automatically startup after server reboot.
Once dbvcontrol is installed and started, you can verify accessibility by going to following URL:
https://<control center hostname>:4433default username and password is: admin/admin
2.5 Importing v9 or v10 DDC file into dbvcontrol dashboard
Before starting this procedure, ensure that the DDC file (dbv_<DDC>.env) was copied by the automated upgrade process into standbymp/oracle/conf. If not, contact Dbvisit Support for further steps
After logging in to dbvcontrol, choose New Configuration (1) and Start with Oracle (2):
Make sure to select primary server:
Old version DDC file was automatically prepared for import, choose Import Configuration (1):
After the import the licence will be invalid:
You will need to enter & update licence key to version 12 as per: https://dbvisit.atlassian.net/wiki/spaces/DSMPV12/pages/4511793191 .
We recommend to test sending & applying one archivelog and checking Automated standby update: https://dbvisit.atlassian.net/wiki/spaces/DSMPV12/pages/4447600649
The time gap will be corrected after 1st successful archivelog apply.
This is the final step of the upgrade process on Linux. Let the synchronization run for few days and if there are no issues, delete the backup you created previously.
3. Windows Upgrade
As with Linux, the upgrade consists of four main steps:
A. stop & backup existing version 9 and 10 components
B. run v12 installer and select existing Dbvisit Base for installation
C. startup v12
D. Import version 9 or 10 configuration and update licence key.
You will need to upgrade dbvisit on all servers to complete the upgrade.
3.1 Stop dbvisit components and backup existing DBVISIT_BASE directory
Stop all dbvisit components using Windows services.msc:
note the user which is used to run the service. You will need to use this user and its password during upgrade. In this example “oracle”
Dbvserver will be present only on one database server (typically standby) or on separate host.
dbvctl-* service is synchronization daemon, you need to stop it as well. In case the dbvctl-* service is not displayed, make sure that you disable any windows scheduler jobs used for database synchronization as described here: https://dbvisit.atlassian.net/wiki/spaces/DS10QSG/pages/2415200756/Dbvisit+Standby+Scheduling#DbvisitStandbyScheduling-3.2.Disablingaschedule
We recommend to stop all dbvisit components on other servers which will be part of the upgrade at this point as well.
Cleanup existing directories in DBVISIT_BASE: standby\trace, standby\tmp, standbymp\gs. You can remove all files in those directories, as they are temporary only.
Afterwards backup existing DBVISIT_BASE (by default C:\Program Files\Dbvisit) directory by copy+paste into backup directory of your choice.
3.2 Run version 12 dbvagentmanager installer to upgrade dbvisit on all primary and standby servers
Perform this step on all primary and standby servers. This will install dbvagentmanager component only. Dbvagentmanager replaces dbvnet, dbvagent and standby core.
Run the version 12 agent installer from the temporary directory:
Click Next in the very first step:
You must accept EULA (1) in order for upgrade to proceed (2):
On the next screen, you should see Upgrade button (1) and the v10 or v9 release which was detected on the server:
You will need to fill in details on following screen:
Number | Description | Explanation |
|---|---|---|
1 | Fully qualified name for this host | To get the correct value, you will need to refer to your v10 or v9 DDC file which is found in the backup directory you created before upgrade: Dbvisit\standby\conf\dbv_<DDC>.envopen the file and on primary server enter SOURCE value, on standby server enter DESTINATION value (case and domain sensitive): Note that your DDC file name will be different than in the example. The format is: dbv_<db_name>.env |
2 | Fully qualified name for the Control Center Host | Enter hostname of the server where your dbvserver component is installed |
3 | Dbvagentmanager Service User Details | Fill in domain, username and password of user which runs the dbvnet, dbvagentmanager and dbvctl* service on the host.
|
click on next (4) to continue. Afterwards confirm that the server name is correct (1):
Enter and confirm passphrase used for encrypting communication between dbvagentmanagers and dbvcontrol. Must match on all hosts. There is no complexity requirement and there’s no dependency on version 9 or 10, you can choose any string (1), click on next (2):
Confirm installation folder location (1):
Finally, click on Install (1) to start upgrade:
Once upgrade finishes, close the installer (1):
Re-check the services.msc that dbvagent and dbvnet services were removed and dbvagentmanager service is running:
Do not delete the dbvctl* service at this point, leave it in stopped state
3.3 Run version 12 dbvcontrol installer on dbvserver host
Perform this step only on host where dbvserver was installed (typically standby host or in some cases different host from primary and standby). Dbvcontrol replaces dbvserver component.
Run the version 12 installer from the temporary directory:
On the frist screen click on Next:
You must accept EULA (1) in order for installation to proceed (2):
On the next screen, you should see and click on the Upgrade button (1):
Dbvcontrol doesn’t require as many details as dbvagentmanager. You can change the webserver port (1) if you have used custom webserver port for your dbvserver. You can double check in the backup folder file Dbvisit\Dbvserver\conf\dbvserver.conf parameter listener_port to verify the port.
Once you confirm the port, click Next (2). Afterwards, enter and confirm passphrase used for encrypting communication between dbvagentmanagers and dbvcontrol. Must match on all hosts. There is no complexity requirement and there’s no dependency on version 9 or 10, you can choose any string (1), click on next (2):
Change installation directory for dbvcontrol if needed or go with default. Once ready click on Next (1):
If you’re upgrading to dbvcontrol on server where you already upgraded dbvagentmanager, choose the same directory as you did for dbvagentmanager.
Start the upgrade by clicking on Install (1):
Once upgrade finishes, close the installer:
Re-check the services.msc and verify that dbvserver service was removed and dbvcontrol service is running:
Once dbvcontrol is installed and started, you can verify accessibility by going to following URL:
https://<control center hostname>:4433default username and password is: admin/admin
If you can’t access dbvcontrol, go to dbvcontrol host, edit the file C:\Program Files\Dbvisit\standbymp\conf\dbvcontrol.ini and set empty value for parameter Gui.WebListenAddress:
save the file, restart dbvcontrol service and try again.
3.4 Importing v9 or v10 DDC file into dbvcontrol dashboard
Before starting this procedure, ensure that the DDC file (dbv_<DDC>.env) was copied by the automated upgrade process into standbymp\oracle\conf. If not, contact Dbvisit Support for further steps
This procedure is entirely same as with Linux OS. After logging in to dbvcontrol, choose New Configuration (1) and Start with Oracle (2):
Make sure to select primary server:
and click on Import Configuration:
After the import the licence will be invalid:
You will need to enter & update licence key to version 12 as per: https://dbvisit.atlassian.net/wiki/spaces/DSMPV12/pages/4511793191 .
We recommend to test sending & applying one archivelog and checking Automated standby update: https://dbvisit.atlassian.net/wiki/spaces/DSMPV12/pages/4447600649
The time gap will be corrected after 1st successful archivelog apply.
3.5 Post Steps
This is the final step of the upgrade process on Windows. You should let the synchronization run for few days and if there are no issues, delete the backup you created previously and also manually remove dbvctl daemon service. This can be done by running command:
C:\Users\vagrant>sc delete dbvctl-TEST01
[SC] DeleteService SUCCESSYou should also delete dbvctl windows scheduler jobs if you didn’t use dbvctl daemons for synchronization.
4. Rollback Upgrade
If for any reason the upgrade wasn’t successful, you can easily revert to previously installed version. The steps in this section are valid for Windows and Linux
You will need to perform following steps:
4.1 Stop the existing dbvisit processes or services
refer to https://dbvisit.atlassian.net/wiki/spaces/DSMPV12/pages/4403298346 on how to stop existing dbvisit processes or services. If upgrade failed during installation and no processes are running, you can skip this step.
4.2 Restore the backup you created before the upgrade
Delete all files created by failed upgrade from DBVISIT BASE. Fully restore the backup of the DBVISIT BASE folder you created into the original location. Use this folder location as a reference example where restored folders should be placed:
Default directory structure for bin folder on Linux:
/usr/dbvisit/standbymp/binDefault directory structure for bin folder on Windows:
C:\Program Files\Dbvisit\standbymp\bin4.3 Start dbvisit processes or services
To start again version 10 or version 9 services and processes, refer to:
For version 9:https://dbvisit.atlassian.net/wiki/spaces/DS9QSG/pages/1244987646
For version 10:https://dbvisit.atlassian.net/wiki/spaces/DS10QSG/pages/2415198642
Windows Only:
If failed upgrade left you in state where the dbvisit services were deleted from the system services, you can create them manually after you restore the backed up folder. You will need to re-create them manually with dbvsmgr binary found in DBVISIT_BASE\:
dbvsmgr.exe -i dbvagent -a <Domain>\<User> -p <PasswordHere>
dbvsmgr.exe -i dbvnet -a <Domain>\<User> -p <PasswordHere>
dbvsmgr.exe -i dbvserver -a <Domain>\<User> -p <PasswordHere>You can change user running the service and its startup type easily after creation by running services.msc and modifying service properties.
Start the newly created services. You may also need to re-create dbvctl* daemon services, if you have already deleted them: