![]() |
Dbvisit home |
|
#1
|
|||
|
|||
|
Dbvisit Standby on Solaris may give the following:
First time Dbvisit Standby runs, Dbvisit Standby installation will be copied to tornadoX... Transferring dbv_functions to host tornadoX:dbv_functions Waiting for 5 seconds (RETRIES_WAIT_IN_SEC) until retry. 200912091727 - Problem with calculating checksum for /usr/local/dbvisit/dbv_functions on tornadoX. 5cbc259bd8a194a62fe1bcc10181d777693ef947 5324721 /usr/local/dbvisit/dbv_functions Please check permission and if program /usr/local/dbvisit/dbv_functions exists and is executable on tornadoX. Please also check network connection, else please contact Dbvisit support. Dbvisit terminated. Return code = 255 Running a test ssh command to server tornadoX and checking the return code gives: oracle@db01 $ /usr/bin/ssh tornadoX uname -a; echo $? SunOS wlg-tornado 5.9 Generic_112233-06 sun4u sparc SUNW,UltraSPARC-IIi-cEngine 255 oracle@db01 $ The ssh is working fine, but it is returning a return code of 255. This is causing Dbvisit Standby to flag the error and stop processing. It should return return code 0. Run ssh with -v option to get more details and the version: SSH Version Sun_SSH_1.0, protocol versions 1.5/2.0. This version appears to have a bug in it. You will need to install ssh patches for Solaris to fix the issue. The patches you need are: 112908-36 114356-19 Applying them on both the primary and standby servers will fix the ssh issue. Update Feb 2012 Upgrade to Dbvisit Standby version 6.0.20 or higher and set SSH_RETURN_CODE=1. If this is set, then the ssh software does not need to be upgraded as Dbvisit Standby will accept 1 as a valid return code. Last edited by Arjen Visser; 02-27-2012 at 09:11 PM. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|