on 08-22-2016 1:52 PM
I'm stuck in the Execution phase of Solution Manager 7.1 upgrade to SPS14.
The error I get says:
SAPup> Process with PID 16829 terminated with status 20 at 20160822150624!
SAPup> Starting subprocess with PID 16930 in phase 'UPDATE_DBSTATS_SWTC' at 20160822150657
ENV: DIR_LIBRARY=/usr/sap/<SID>/SUM/abap/bin
ENV: JAVA_HOME=/usr/sap/<SID>/DVEBMGS00/exe/sapjvm_4
ENV: LD_LIBRARY_PATH=/usr/sap/<SID>/SUM/abap/bin:/sybase/<SID>/ASE-15_0/jobscheduler/bin:/sybase/<SID>/ASE-15_0/bin:/sybase/<SID>/ASE-15_0/install:/sybase/<SID>/DBISQL/bin:/sybase/<SID>/OCS-15_0/bin:/usr/sap/<SID>/DVEBMGS00/exe/sapjvm_4/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/sap/<SID>/SYS/exe/uc/linuxx86_64:/usr/sap/<SID>/SYS/exe/run:/home/slmadm:.:/usr/sap/<SID>/hdbclient
ENV: PATH=/usr/sap/<SID>/SUM/abap/bin:/sybase/<SID>/ASE-15_0/jobscheduler/bin:/sybase/<SID>/ASE-15_0/bin:/sybase/<SID>/ASE-15_0/install:/sybase/<SID>/DBISQL/bin:/sybase/<SID>/OCS-15_0/bin:/usr/sap/<SID>/DVEBMGS00/exe/sapjvm_4/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/sap/<SID>/SYS/exe/uc/linuxx86_64:/usr/sap/<SID>/SYS/exe/run:/home/slmadm:.
*ENV: RSEC_SSFS_DATAPATH=/usr/sap/<SID>/SUM/abap/mem/rsecssfs/data
*ENV: RSEC_SSFS_KEYPATH=/usr/sap/<SID>/SUM/abap/mem/rsecssfs/key
ENV: SAPSYSTEMNAME=<SID>
*ENV: dbms_type=syb
*ENV: dbs_syb_connect_user=sapsa
ENV: dbs_syb_dbname=<SID>
ENV: dbs_syb_no_ext_check=1
ENV: dbs_syb_port=4901
*DBENV: dbs_syb_schema=SAPSR3
ENV: dbs_syb_server=solman
ENV: rsdb_ssfs_connect=1
*DBENV: (auth_shadow_upgrade)
PWD: /usr/sap/<SID>/SUM/abap/tmp
EXECUTING /usr/sap/<SID>/SUM/abap/bin/SAPuptool execdb ../var/SYBGETSERVER.TSQL
Logging to '/usr/sap/<SID>/SUM/abap/log/SYBGETSERVER.LOG'
Could not load SYB library libsybdrvodb.so. No database connection possible.Could not load SYB library libsybdrvodb.so. No database connection possible.Could not load SYB library libsybdrvodb.so. No database connection possible.1EETQ008 Error message: DBSL error 29 (db code 0): Connect failed
1EETQ003 exit code: "20"
SAPup> Process with PID 16930 terminated with status 20 at 20160822150657!
It seems like SUM tried to switch out the dbclient but somehow it managed to delete previous drivers and not install the new ones. However the sybodbc and sybjdbc drivers are present in the /sapmnt/<SID>/global/syb/linuxx86_64 folder. Also the drivers exist in /usr/sap/<SID>/SUM/abap/bin folder. The libsybdrvodb.so and libsybdrvodb8.so files both are owned by sidadm and they have the necessary required permissions (read and write) available.
R3trans -x command also returned the same error. I tried to look up some Notes regarding this problem but I was not able to find anything that worked for me. What directory is SAPuptool trying to find these drivers from? Can somebody please help?
Turns out that the .dbenv.csh file couldn't set the LD_LIBRARY_PATH correctly so that it would point to the correct directory. As a temporary solution I modified the .cshrc file and added the LD_LIBRARY_PATH assignment of directory ../SYS/global/syb/linuxx86_64/sybodbc to the variable manually and it started working.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rauno,
Check if this workaround mentioned in https://scn.sap.com/thread/3290943 helps or not.
Regards,
Ning
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Could you supply the log file SYBGETSERVER.LOG?
Additionally run R3trans -d and supply the trans.log file.
It would be helpful if you could supply the latest trace files from the /usr/sap/<SID>/SUM/abap/log location.
In the mean while check the workaround suggested in this SAP note and see if it helps. You can copy the files from the sybodbc directory to /usr/lib64 instead of symbolic links.
2115940 - sybctrl load_script Error: executing administration task failed
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your reply.
I already tried the solution suggested in 2115490 (tried copying the files - didn't work, tried creating the symbolic links - didn't work either).
"R3trans -d" produced this:
4 ETW000 R3trans version 6.24 (release 721 - 15.03.16 - 20:16:01).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 23.08.2016 - 09:07:45
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 1 opened for a given file pointer
4 ETW000 [ dev trc,00000] Tue Aug 23 09:07:45 2016
4 ETW000 [ dev trc,00000] Loading DB library '/usr/sap/<SID>/SYS/exe/run/dbsybslib.so' ...
4 ETW000 [ dev trc,00000] Library '/usr/sap/<SID>/SYS/exe/run/dbsybslib.so' loaded
4 ETW000 [ dev trc,00000] Version of '/usr/sap/<SID>/SYS/exe/run/dbsybslib.so' is "721.02", patchlevel (0.214)
4 ETW000 [ dev trc,00000] con_info_ext_support(): DBSL supports extended connect protocol
4 ETW000 ==> connect info for default DB will be read from ssfs
4 ETW000 [ dev trc,00000] Could not load SYB library libsybdrvodb.so. No database connection possible.
4 ETW000 [ dev trc,00000] Load of odbc driver for Sybase ASE failed. Connect terminated.
2EETW169 no connect possible: "DBMS = SYBASE --- "
What's funny, is that this log lies in the /usr/sap/<SID>/SUM/abap/log folder not in the sidadm home folder. But I guess this is normal since we have the installation in progress with SUM.
SYBGETSERVER.LOG contained only this:
1 ETQ000 ==================================================
1 ETQ399 Executing SQL script '../var/SYBGETSERVER.TSQL'.
2 ETQ399 Connecting to database 'syb'.
3EETQ008 Error message: DBSL error 29 (db code 0): Connect failed
4EETQ399 1 [ dbsyb.c,37582]: Could not load SYB library libsybdrvodb.so. No database connection possible.
4EETQ399 1 [ dbsyb.c, 4653]: Load of odbc driver for Sybase ASE failed. Connect terminated.
Hi Rauno,
Please check below SAP Note and see if the solution provided is applicable for your scenario:
1817091 - Could not load SYB library sybdrvodb64.dll. when connecting to a Sybase ASE for BS/BW
Thanks,
Manish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.