...
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.
| Note |
|---|
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
...
- 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 dbvrlin301 is the a primary server and dbvlin102 dbvrlin305 is the single instance 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@dbvlin101oracle@dbvrlin301[/usr/dbvisit/dbvnet]: ./dbvnet-test -s dbvlin102dbvrlin305:7890 >>> Determining Dbvnet status on server dbvlin102dbvrlin305:7890... Dbvnet on server dbvlin102dbvrlin305:7890 is running. |
Test 2: Full Test - 10MB file is copied (and verified) between primary and standby
| Code Block | ||
|---|---|---|
| ||
oracle@dbvlin101oracle@dbvrlin301[/usr/dbvisit/dbvnet]: ./dbvnet-test -f dbvlin102dbvrlin305:7890 >>> Determining Dbvnet status on server dbvlin102dbvrlin305:7890... Dbvnet on server dbvlin102dbvrlin305:7890 is running. >>> Running file transfer round trip on server dbvlin102dbvrlin305:7890... Creating file '/tmp/dbvnet-test.tmp' containing 10 MB of data... - done. > Transferring 'dbvnet-test.tmp' to server dbvlin102dbvrlin305:7890 Progress: 0%...20%...40%...60%...80%...100% [2609 KB/s] - done. > Retrieving file "dbvnet-test.tmp" from server dbvlin102dbvrlin305: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. |
...
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@dbvlin101oracle@dbvrlin301[/usr/dbvisit/dbvnet]: ./dbvnetd stop oracle@dbvlin101oracle@dbvrlin301[/usr/dbvisit/dbvnet]: ps -ef|grep dbvnet oracle 12641 12446 0 09:20 pts/1 00:00:00 grep dbvnet oracle@dbvlin101oracle@dbvrlin301[/usr/dbvisit/dbvnet]: ./dbvnetd start oracle@dbvlin101oracle@dbvrlin301[/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 all primary nodes in the RAC configuration as well as the 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.
...
Example below is connecting to the GUI on dbvlin101 dbvrlin301 (172.16.1.111131) using https and port 8443.
...