...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
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.
...
7. 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.
...
| 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 | ||||
|---|---|---|---|---|
| ||||
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.
...
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 | ||
|---|---|---|
| ||
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:PORT 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 | ||
|---|---|---|
| ||
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) ========================================================= =>dbvisit_setup only needs to be run on the primary server. Is this the primary server? <Yes/No> [Yes]: Dbvisit Database setup Options: 2) New Dbvisit Database configuration (DDC) file setup 5) Manage Dbvisit Database repository (DDR) 7) Create Standby Database (and template) 9) Uninstall Dbvisit Database repository (DDR) ========================================================= Maintain Dbvisit Database repository (DDR) Options: r) Return to main menu ========================================================= ------------------------------------------------------------------------------ Choose database: The following Oracle database(s) have a Dbvisit Database configuration (DDC) DDC Please enter choice : 1 Is this correct? <Yes/No> [Yes]: Yes Dbvisit Database repository (DDR) version: 7.0
Please press <Enter> to continue... ========================================================= Maintain Dbvisit Database repository (DDR) Options: r) Return to main menu ========================================================= |
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.
...