As of May 2026 The only version of Dbvisit Standby supported on AIX and Solaris operating systems is version 9. This version is publicly available for download here:
https://dbvisit.com/try-standby
The documentation and install guides are located here:
https://dbvisit.atlassian.net/wiki/spaces/DS9QSG/overview
Sections below include additional recommendations and clarifications to the existing user guide.
When deploying this version on UNIX systems, the following considerations must be taken into account:
A) Dbvserver component support
(AIX and Solaris)
Dbvserver components cannot be run on AIX or Solaris. If users need to use GUI, it is needed to install dbvserver component either on Linux or Windows machine (both platforms are supported).
B) Dbvnet component support
(AIX and Solaris)
Dbvnet component isn't compatible with neither AIX nor Solaris. Intermittent Issues can be observed during transfer with dbvnet. Because of this, the only supported method for synchronisation and communication between the primary and standby servers is through SSH.
When creating a new DDC file, users must choose SSH as the primary layer for communication:
https://dbvisit.atlassian.net/wiki/spaces/DS9QSG/pages/1244987937/Creating+the+DDC+File
Do you want to use SSH to connect to the standby server? Note that if you are
using SSH, passwordless SSH authentication between the hosts must already be
configured. By default Dbvnet will be used.
=>USE_SSH is [N]: Y
Your input: Y
Is this correct? <Yes/No> [Yes]: Yes
Choice is Y
Similar option is available in GUI:
You must select this option for AIX and Solaris.
It is possible to switch to SSH after DDC creation using:
C) Dbvisit Daemon process support
(AIX and Solaris)
Dbvisit uses daemon process for automating the archivelog synchronization between primary and standby server:
The advantage of daemon process is near-immediate detection of new archivelog on primary, lowering RPO as much as possible.
Dbvisit daemon process is fully supported on AIX and Solaris with the following exception:
While it is possible to use dbvisit CLI and GUI for starting the daemon process, stopping the process must be only done directly in the OS via kill -9 command
Daemon process can be identified as follows:
ps -ef | grep dbvctl | grep start
oracle 952142 1 0 May 3 - 26:41 ./dbvctl -D start --mode GUI -d PRODIn this example "PROD" is the name of DDC configuration. Once the process is identified, kill -9 to stop it:
kill -9 952142This action needs to be performed on the primary and standby servers separately.
It is necessary to manually stop and start daemon process in these cases:
- Stop and start immediately once any DDC parameter is changed
- Stop before the switchover process and start after the switchover process
- Stop before starting DR test and start after reinstate is finished
D) Supporting newer Solaris systems with OpenSSH 9.3
(Solaris only)
The update from OpenSSH 8.4 to OpenSSH 9.3 contains an incompatible change which prevents Dbvisit from using the SSH communication layer: https://www.openssh.com/txt/release-9.0
To resolve this incompatibility, once you configure DDC with SSH as per doc page:
https://dbvisit.atlassian.net/wiki/spaces/DS9QSG/pages/1244987937/Creating+the+DDC+File
perform additionally on the primary and standby hosts:
- Make the wrapper script:
# vi /usr/bin/scp2 #!/bin/sh exec /usr/bin/scp -O "$@"
Change the permissions of /usr/bin/scp2 as same as /usr/bin/scp.
- Change the DDC parameters:
（Before） CP=/usr/bin/scp （After） CP=/usr/bin/scp2
Comments