...
- 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–fulltest] TMPDIR SERVER:PORT
In the example below, dbvrlin301 is a primary server and 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:
...
| Code Block | ||
|---|---|---|
| ||
oracle@dbvrlin301[/usr/dbvisit/dbvnet]: ./dbvnet-test -f /tmp dbvrlin305:7890
>>> Determining Dbvnet status on server dbvrlin305:7890...
Dbvnet on server dbvrlin305:7890 is running.
>>> Running file transfer round trip on server dbvrlin305:7890...
Creating file '/tmp/dbvnet-test.tmp' containing 10 MB of data... - done.
> Transferring 'dbvnet-test.tmp' to server dbvrlin305:7890
Progress: 0%...20%...40%...60%...80%...100% [2609 KB/s] - done.
> Retrieving file "dbvnet-test.tmp" from server dbvrlin305: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. |
...