This issue is most often seen in customers using the Solaris and AIX operating systems, since they use SSH instead of dbvnet, as recommended by Dbvisit for file transfer.
The root cause was identified as the intended change https://www.openssh.com/txt/release-9.0:
The update from OpenSSH 8.4 to OpenSSH 9.3 contains the following potentially incompatible changes: This creates one area of potential incompatibility: scp(1) when using the SFTP protocol no longer requires this quoting, and attempts to use it may cause transfers to fail. Another area of potential incompatibility relates to the use of remote paths relative to other user's home directories, for example - "scp host:~user/file /tmp". The SFTP protocol has no native way to expand a ~user path. However, sftp-server(8) supports a protocol extension "expand-path@openssh.com" to support this. In case of incompatibility, the scp(1) client may be instructed to use the legacy scp/rcp using the -O flag.
Problem Details
Problem Statement
SSH communication fails after OS upgrade with SCP changes
Applicable Error Code
ERROR_CODE:1
/usr/bin/scp: dest open ""/usr/dbvisit/standby/conf/dbv_ddc.env"": No such file or
directory
/usr/bin/scp: failed to upload file /usr/dbvisit/standby/conf/dbv_ddc.env to
/usr/dbvisit/standby/conf/dbv_ddc.env"Affected Versions
v8, v9, v10(Linux)
Affected Platforms
Solaris, AIX, Linux
Solution
On the primary server
1. Make the wrapper script with the following content
Ex: vi /usr/dbvisit/standby/scp
#!/bin/sh exec /usr/bin/scp -O "$@"
2. Grant it an execute privilege
chmod +x /usr/dbvisit/standby/scp
3. Change the Dbvisit DDC parameter.
（Before） CP=/usr/bin/scp （After） CP=/usr/dbvisit/standby/scp
4. Perform the above steps on the standby server as well.
Comments