2.1.1. Recommended Operating System Packages
Before installing the Dbvisit Standby it is recommended that the following operating system package (if using Linux) be installed prior to installing Dbvisit Standby version 10 Dbvserver component. In most installations, the packages would already be installed and no additional software would be required.
RHEL 8 is by default missing also package "libnsl" - install it by running "yum install libnsl"
Confirming if these packages are installed can be done using the "rpm -qa" command, example on Oracle Linux 7.2.
[root@dbv103 dbvserver]# rpm -qa|egrep 'zlib|glibc|libaio'
2.1.2. The Dbvisit Standby Base (DBVISIT_BASE)
The location into which Dbvisit Standby software is installed into is referred to as the Dbvisit Standby base, also known as the DBVISIT_BASE.
The default location is as follow:
|Unix Based Systems||Windows Based Systems|
It is strongly recommended that you make use of the default location when installing Dbvisit Standby.
On Unix, it is important to pre-create this directory and make sure the owner and group used for this directory are the same as what was used for the Oracle Database Software installation. In most cases, this will be the Unix user "oracle" and group "oinstall" or "dba"
Note: It is recommended you have a minimum of 512MB of free space in this location to cater to the installation.
DBVISIT_BASE is also used to store active redolog during the switchover. Make sure, that there is also additional space available equal to the size of your redolog file
2.1.3. Network Connectivity
IPV6 is not supported. Please, ensure you are using only IPV4 protocol.
It is recommended to make sure that the primary and standby servers are aware of the others name and IP address. Using DNS entries or using entries in the “hosts” file can be used to do this.
The central web server (Dbvserver) should also be installed on a central location (its own server if possible) and this system must also be able to connect to the primary and standby servers.
Example entries in host file (note that xxx.xxx.xxx.xxx is IP addresses):
Dbvisit Standby version 10 makes use of Dbvnet by default for network communication between the primary and standby database servers, however, it is still possible (and fully supported) to make use of SSH for communication if required. Using SSH is only allowed and supported on UNIX based systems.
It is recommended that you make sure the following ports are open on each of the servers to allow for communication between them, as well as to allow the end-user to connect to the Dbvisit Web GUI:
- Dbvisit Networking (Dbvnet)
- The default port used is 7890
- Dbvisit Agent (Dbvagent)
- The default port used is 7891
- Dbvisit GUI (Dbvserver)
- The default port used for HTTPS is 4433
- Note that HTTP is not an option and that HTTPS must be used.
- If SSH is used instead of Dbvnet, the default SSH port 22, should also be open and passwordless authentication (SSH equivalence) must already be configured. If SSH is used, the account running Dbvisit Standby must be the same as the Oracle database software owner.
The below figure should explain this as well.
Note: in most cases, you will need to allow these ports to be open in your IPTABLES or any other local firewall configuration if you are using Linux, or you will have to update your Windows firewall settings if a Windows is used.
2.1.4. Network Connectivity when using Oracle RAC
Note that in Dbvisit Standby version 10, Oracle RAC configurations are treated the same as version 9 and 8 which is different from earlier versions.
If you want to upgrade from version 7 to version 10, we recommend you perform a clean new version 10 installation and create a new DDC file. This is due to a large number of changes Dbvisit Standby version 10 brings with regards to Oracle RAC configurations.
In Dbvisit Standby version 10, we recommend that you run Dbvisit Standby only on one of the Oracle RAC nodes and make use of shared storage.
For more detail please see these sections:
When installing Dbvisit Standby version 10 in an Oracle RAC configuration, the following will be required:
A new Virtual IP and Name for each of the Primary and Standby database clusters (if both are Oracle RAC, otherwise if the standby server is a single instance - single node server, no Virtual IP and Name will be required for the standby as the standby server details will be used as is).
Example, you have a 2 node Oracle RAC cluster with node1 and node2 with the following example IP configuration (extract from /etc/hosts)
192.168.1.11 node1.demo.net node1
192.168.1.12 node2.demo.net node2
192.168.1.13 node1-vip.demo.net node1-vip
192.168.1.14 node2-vip.demo.net node2-vip
10.0.1.11 node1-priv.demo.net node1-priv
10.0.1.12 node2-priv.demo.net node2-priv
# 192.168.1.15 racdb-scan.demo.net racdb-scan ## note these SCAN addresses should be in the DNS not hosts file
# 192.168.1.16 racdb-scan.demo.net racdb-scan ## note these SCAN addresses should be in the DNS not hosts file
# 192.168.1.17 racdb-scan.demo.net racdb-scan ## note these SCAN addresses should be in the DNS not hosts file
You will now configure Dbvisit Standby version 10 on this cluster which will run on only one of the nodes at a time - no need to run Dbvisit Standby on both RAC nodes.
Shared storage for the Dbvisit Standby installation will be used - example /usr/dbvisit might be using a shared ACFS filesystem.
To allow appropriate communication from the standby to the correct primary RAC node that is running the Dbvisit Standby version 10 software, a Virtual IP (name) is created, an example in the case above configuration the following can be added:
192.168.1.18 dbvracdb-vip.demo.net dbvracdb-vip
For more detail on creating this Virtual IP, please see the Oracle Documentation with regards to the command "appvipcfg"
Below is an example of the steps to create the Virtual IP on a Linux based RAC configuration and starting it on node1 (These commands are only executed on one of the nodes - example node 1 and is done as the "root" user)
appvipcfg create -network=1 -ip=192.168.1.18 -vipname=dbvracdb-vip -user=root
crsctl status resource dbvracdb-vip -p
crsctl setperm resource dbvracdb-vip -u user:oracle:r-x
crsctl setperm resource dbvracdb-vip -u user:grid:r-x
crsctl start resource dbvracdb-vip -n node1
2.1.5. Default TEMP Directory
When installing Dbvisit Standby and you may get the following error "Error: Can't locate libperl.so"
Error: Can't locate libperl.so
When Dbvisit Standby is executing, including Dbvnet and Dbvserver, temporary files are extracted and used from the default system temp location.
On most Unix system this will be /tmp The problem, in this case, is that the /tmp mount point was mounted using the "noexec" option.
Using the mount command you can quickly review the settings:
oracle@dbvlin103[/home/oracle/10.0/dbvisit/installer]: mount |grep tmp
tmpfs on /dev/shm type tmpfs (rw,size=2G,rootcontext="system_u:object_r:tmpfs_t:s0")
tmpfs on /tmp type tmpfs (rw,noexec,size=2G)
In some cases where environments are locked down, this might be seen.
There are two possible options to get past this.
1. Ask the system administrator to mount the /tmp filesystem without the "noexec" option.
2. Create a new temporary directory and set the TMPDIR environment variable to point to this location, for example:
oracle@dbvlin103[/home/oracle/10.0/dbvisit/installer]: mkdir /home/oracle/tmp
oracle@dbvlin103[/home/oracle/10.0/dbvisit/installer]: export TMPDIR=/home/oracle/tmp
If using TMPDIR option you will need to make sure you update the .bash_profile or.profile or other environment configuration files to ensure that this path is set before you execute Dbvisit Standby processes.