Dbvisit Standby version 7 is making use of a new directory structure in comparison to the previous version 5 and 6. The default location on Linux for version 5 and 6 was /usr/local/dbvisit but in version 7 the default location changed to /usr/dbvisit. You can however still install version 7 into any other custom location, example /opt/dbvisit. It is recommended not to install Dbvisit Standby in the home directory of the oracle Unix account (/home/oracle).
This section will provide you with the detail steps required to perform a new installation of Dbvisit Standby version 7.
Installation Steps
This section cover the installation of Dbvisit Standby on an Oracle Real Application Cluster environment.
| Note |
|---|
When installing Dbvisit Standby in a Oracle RAC environment Oracle Grid Infrastructure version 11.1 and higher is recommended. Using version 10.2 for ASM storage is not recommended and will limit the functionality of Dbvisit Standby - Graceful Switchover will not be possible. |
Dbvisit Standby will be installed on all the servers in an Oracle RAC configuration. For example if you are using a four node cluster, you need to install Dbvisit Standby on all four nodes as well as on the Standby server(s).
When installing into /usr/dbvisit approximately 70MB of space is required (per server), but as trace files and log files will be stored in this location, 200MB free space is the recommended minimum.
It is recommended to install Dbvisit Standby into the default location /usr/dbvisit or /usr/local/dbvisit (Custom locations can be specified - example /opt/dbvisit)
If you are upgrading, please see the section "Upgrade Dbvisit Standby on Oracle RAC environments"
The next 7 steps should be followed to install Dbvisit Standby in an Oracle RAC environment running on Linux.
The examples below will assume a 2 - Node Oracle RAC environment:
- Primary Nodes: dbvrlin301 and dbvrlin302
- Standby Node: dbvrlin305
- Oracle Grid Infrastructure 11.2 using ASM for storage
Step 1: Create "Dbvisit Base" Directory
The first step is to create the Dbvisit Base directory. This is the directory into which Dbvisit Standby will be installed into. The default location is /usr/dbvisit
This directory should be owned by the Oracle Database software owner.
The following steps can be executed as the "root" user to create the directory and set correct permission:
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
[root@dbvrlin301 ~]# cd /usr
[root@dbvrlin301 usr]# mkdir dbvisit
[root@dbvrlin301 usr]# chown -R oracle:oinstall dbvisit
[root@dbvrlin301 usr]# ls -ld dbvisit
drwxr-xr-x 2 oracle oinstall 4096 Aug 21 11:13 dbvisit |
Step 2: Download Latest Software
The first step is to download the latest available version from the Dbvisit web site http://www.dbvisit.com
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:
| Code Block | ||||
|---|---|---|---|---|
| ||||
oracle@dbvrlin301[/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:
| Code Block | ||||
|---|---|---|---|---|
| ||||
oracle@dbvrlin301[/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@dbvrlin301[/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@dbvrlin301[/home/oracle/7.0]: tar -xf dbvisit-standby7.0.01.tar
oracle@dbvrlin301[/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:
| Code Block | ||
|---|---|---|
| ||
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
(note that 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.
| Background Color | ||
|---|---|---|
| ||
oracle@dbvrlin301[/home/oracle/7.0/dbvisit/installer]: ./install-dbvisit-------------------------------------------------------------------------------
|
At this stage you should now have the Dbvisit Standby software installed on the first node 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:
| Code Block | ||
|---|---|---|
| ||
oracle@dbvrlin301[/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 all RAC Nodes including the Standby Server
Dbvisit Standby needs to be installed on all the Primary nodes, the same as above, once this is complete, also install Dbvisit Standby on the Standby server following the exact same steps.
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
| Code Block | ||
|---|---|---|
| ||
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
| Code Block | ||
|---|---|---|
| ||
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:
| Code Block | ||
|---|---|---|
| ||
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
oracle@dbvlin101[/usr/dbvisit/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.