on 09-14-2011 3:31 PM
Hi, i'm in the prepare yet now of an Update from Solution Manager 7.0 EHP1 SPs26 to SPs27!
Support Packages are loaded into SAINT and SPAM now.
After replacing the old kernel with the new one SAPEXEDB_150-10005988.SAR
and SAPEXE_150-10005984.SAR, and tp and R3trans and other files in addition
i get error messages in Tc DB50/DB59/DB02, LC10.
-
-
DB02, DB50 shows :
Name und Server : SOL - sap8
DBMRFC Funktion : DBM_EXECUTE
Kommando : dbm_version
Fehler : Fehler des DBM
Rückgabewert : -11
Fehlermeldung : tp error: connect failed due to DbSL l
-
-
The execution of Report RSSDBCHECKDBMRFC show a lot of system information.
Main Analysis
SMGW - Checking existence and correctness of registered client
SMGW - Entry dbmrfc@sapdb correct
SM59 - Checking existence and connection of RFC destinations SAPDB_DBM and SAPDB_DBM_DAEMON
SAPDB_DBM exists
SAPDB_DBM_DAEMON exists
SAPDB_DBM connection successful
SAPDB_DBM_DAEMON connection successful
SM59 - Checks were successful
CONN - Determining database state via TCP/IP connection SAPDB_DBM and SAPDB_DBM_DAEMON
DBM_EXECUTE_SDB error: dbm_system_error
Name und Server : SOL - sap8
DBMRFC Funktion : DBM_EXECUTE
Kommando : db_state
Fehler : Fehler des DBM
Rückgabewert : -11
Fehlermeldung : tp error: connect failed due to DbSL l
ERROR: Error in determination via command mode "dbmrfc db_state"
DBM_EXECUTE_SDB: dbm_system_error
Name und Server : SOL - sap8
DBMRFC Funktion : DBM_CONNECT
Fehler : Fehler des DBM
Rückgabewert : -11
Fehlermeldung : tp error: connect failed due to DbSL l ERROR: Error in determination via session mode "dbmrfc db_state"
CONN - Check was not successful
-
-
TP - Get connection information and existence of program
Connection information used by DBMRFC:
dbnode: sap8 ; dbname: SOL ; sysid: SOL ; conn: SOL ; profile: no_longer_used
Transport profile is not specified, trying to determine it
Transport profile found /usr/sap/trans/bin/TP_DOMAIN_SOL.PFL
Executing command: dbmcli -d SOL -n sap8 -tpp no_longer_used -tpi SOL -tpc SOL db_state
dbmcli output
55 Error! Connection failed to node sap8 for database SOL:
40 tp error: connect failed due to DbSL l
44 External program terminated with exit code 2
dbmcli output
ERROR: DBMCLI command with tp options was not successful
Checking, if tp executable is in directory /usr/sap/SOL/DVEBMGS66/exe (RSPARAM -> DIR_EXECUTABLE)
tp executable exists in /usr/sap/SOL/DVEBMGS66/exe
TP - Checks were not successful
-
-
ail Analysis
Checking MAXDB Version and searching independent program path via SDBREGVIEW
Independent program path exists: /sapdb/programs
Checking paths in environment variables
Checking correctness of environment variable "ld_library_path"
/usr/sap/SOL/DVEBMGS66/exe (DIR_EXECUTABLE) exists
/sapdb/programs/lib exists and placed correctly in environment variable
Environment variable "ld_library_path" exists and path is set correctly
Checking correctness of environment variable "path"
/sapdb/programs/bin exists
ERROR: /usr/sap/SOL/DVEBMGS66/exe (DIR_EXECUTABLE) was not found
Error found in one step
Checking existence of necessary libraries in /sapdb/programs/lib
libicudata.so. exists
libsapni.so exists
libsapu16.so exists
All libraries found
Checking existence of necessary executables
tp exists in /usr/sap/SOL/DVEBMGS66/exe
sapdbmrfc exists in /usr/sap/SOL/DVEBMGS66/exe
dbmrfc exists in /sapdb/programs/bin
sdbregview exists in /sapdb/programs/bin
sdbverify exists in /sapdb/programs/bin
dbmcli exists in /sapdb/programs/bin
All executables found
-
-
Checking packet installations via SDBVERIFY
SAP Utilities packets are consistent
ERROR: Base packets are inconsistent
sdbverify output
Base 7.7.07.34 64 bit in /sapdb/programs
check files... failed
/sapdb/programs/bin/starter/sdbstarter not found-> exists on host
/sapdb/programs/bin/getdbroot was modified
check dependencies... ok
check rte registration of package... ok
package data is inconsistent
sdbverify output
ERROR: Some needed directories do not exist
ERROR: Directory /sapdb/programs/pgm/starter/sdbstarter/ does not exist -> exists on host
ERROR: Directory /sapdb/programs/bin/starter/sdbstarter/ does not exist -> exists on host
ERROR: Directory /sapdb/SOL/db/pgm/starter/dbmverifypw/ does not exist -> exists on host
ERROR: Directory /sapdb/SOL/db/pgm/starter/sdbstarter/ does not exist -> exists on host
-
-
Is that normal???? The system runs before the kernel update, and i didnt replace some parts of the client!!
I downloaded the newest lib_dbsl_142-10005988.sar Database Library from SMP for SAPDB again
and the other kernel parts and replaced all again and correct the dbsdbslib.so properties to 755.
No succcess!!!
SM59 = SAPDB_DBM runs fine, SAPDB_DBM_DAEMON also works right!!!
SM49 DBMCLI-> -s dbm_version shows
OK
VERSION = 7.7.07 BUILD = DBMServer 7.7.07 Build 034-123-242-761
OS = UNIX
INSTROOT = /sapdb/SOL/db
LOGON = True
CODE = UTF8
SWAP = full
UNICODE = YES
INSTANCE = (unknown)
SYSNAME = Linux
MASKING = YES
REPLYTREATMENT = none,zlib,auto
SDBDBM_IPCLOCATION = /var/lib/sdb/dbm/ipc
DB59 Connection Test shows:
General Connection Data
Connection Name....: SOL
Database Name......: SOL
Database Server....: sap8
tp Profiles........: no_longer_used
DBM User...........: CONTROL
Test Scope
1. Execute an external operating system command (DBMCLI)
2. Determine status using TCP/IP connection SAPDB_DBM (DBMRFC command mode)
3. Determine status using TCP/IP connection SAPDB_DBM_DAEMON (DBMRFC session mode)
4. Test the SQL connection (Native SQL at CON_NAME)
DBMRFC Rel DBMCLI rel. Kernel Patch DBSL Rel. DBSL Patch SQLDBC Runtrime
7.7.07.34 7.7.07.34 701_REL 158 700.08 142 7.6.06.19
Application Server: sap8_SOL_66 ( Linux )
1. Connect. test with "dbmcli db_state" Unsuccessful
dbmcli_command_execute_error
Error! Connection failed to node sap8 for database SOL:
tp error: connect failed due to DbSL l
External program terminated with exit code 2
2. Connect. test with command mode "dbmrfc db_state" Unsuccessful
dbm_system_error
Name and Server : SOL - sap8
DBMRFC Function : DBM_EXECUTE
Command : db_state
Error : DBM Error
Return Code : -11
Error Message : tp error: connect failed due to DbSL l
3. Connect. test with session mode "dbmrfc db_state" Unsuccessful
dbm_system_error
Name and Server : SOL - sap8
DBMRFC Function : DBM_CONNECT
Error : DBM Error
Return Code : -11
Error Message : tp error: connect failed due to DbSL l
4. Connect. test with "native SQL" ( SOL ) Successful
Is maybe the parameter dbms_type the reason??????????
The database interface recognizes the type of the database system by the environment variable dbms_type.
Possible values: ora, inf, db2, db4, db6, ada
-
-
The System is builded from a heterogen. Sys Copy and i checked that the parameter! It is set to
dbms_type = ADA, case sensitiv ??? For windows systems its must set to = ada
Now i read in SDN set the parameter dbms_type to sdb??? Right?
Where is the error???
Thx
Ralf
Edited by: ralf thomas wahlen on Sep 15, 2011 11:37 AM
Hi.
The solution for my problem:
Set the environment on OS exactly: dbms_type = ADA
Set the environment : DIR_LIBRARY to /usr/sap/SOL/DVEBMGSXX/exe
moved disp + work 159 and updated to 160
replaced tp 155 incorrect tp to old version = works
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there.
Is it only an inconsistence of the kernel packages PART I and two??
I created new the TCP/IP RFC connection in SM59, SAPDB_DBM and SAPDB_DBM_DAEMON. In that connection is my error.
Recreation via DB50 and no success!! I always get that message via Report RSSDBCHECKDBMRFC
-
ERROR: Error in determination via command mode "dbmrfc db_sta
DBM_EXECUTE_SDB: dbm_system_error
dbmcli output
55 Error! Connection failed to node sap8 for database SOL:
40 tp error: connect failed due to DbSL l
44 External program terminated with exit code 2
dbmcli output
-
dbmsrv_sap8.err File from today
PID 21709: SIGNAL 15 (SIGTERM) caught, PID: 3895, thread: DBMSrv_MainThread, addr: 0x3ea00000f37, value: 0x62642f4c4f, time: 2011-09-14 08:37:01 GMT
PID 9398: SIGNAL 15 (SIGTERM) caught, PID: 3915, thread: DBMSrv_MainThread, addr: 0x3ea00000f4b, value: 0x62642f4c4f, time: 2011-09-16 06:27:45 GMT
PID 9398: -
> Emergency stack backtrace <----
PID 9398: Using 'backtrace' for stack tracing
PID 9398: (0):0x00002ac6e1041e00
PID 9398: (1):0x00002ac6e1040b3b
PID 9398: (2):0x00000000007a398e
PID 9398: (3):0x000000000079f2db
PID 9398: (4):0x000000000079b741
PID 9398: (5):0x000000000079ba5a
PID 9398: (6):0x000000000079cd62
PID 9398: (7):0x000000000077d2ba
PID 9398: (8):0x000000000052bda5
PID 9398: (9):0x000000000043fd80
PID 9398: (10):0x00000000007e61ce
PID 9398: (11):0x00000000007e70d5
PID 9398: (12):0x000000000042ea5b
PID 9398: (13):0x00002ac6e16d5304
PID 9398: (14):0x000000000042e89a
PID 9398: -
> Dump of siginfo contents <----
PID 9398: signal: 15(SIGTERM)
PID 9398: code: 0(unknown)
PID 9398: errno: 0
PID 9398: value(int): 1680821327(0x642f4c4f)
PID 9398: value(ptr): 0x62642f4c4f
PID 9398: pid: 3915
PID 9398: addr: 0x3ea00000f4b
PID 9398: -
> Register Dump <----
PID 9398: rax: 0xfffffffffffffffc rbx: 0x0000000000000018
PID 9398: rcx: 0xffffffffffffffff rdx: 0x0000000000000018
PID 9398: rsi: 0x0000000000ce1040 rdi: 0x0000000000000003
PID 9398: rsp: 0x00007fff9da59f90 rbp: 0x0000000000000018
PID 9398: r08: 0x00007fff9da5a0b0 r09: 0x0000000000000000
PID 9398: r10: 0x0000000000ce1040 r11: 0x0000000000000206
PID 9398: r12: 0x0000000000ce1040 r13: 0x0000000000000003
PID 9398: r14: 0x00007fff9da5a0b0 r15: 0x0000000000000000
PID 9398: rip: 0x00002ac6e1040b3b eflg: 0x0000000000000206
PID 9398: cs: 0x0000 gs: 0x0000
PID 9398: fs: 0x0000
PID 9398: omsk: 0x0000000000000000 cr2: 0x0000000000000000
PID 9398: trap: 0x0000000000000000 err: 0x0000000000000000
PID 9398: -
> Floating-point register dump <----
PID 9398: foper: 0x0000 frip: 0x00007fff9da59f40 fdata: 0x00002ac6e16e9ece
PID 9398: control: 0x000f status: 0x0000 tag: 0x0000
PID 9398: mxcsr: 0x48544150 mxcr_mask: 0x00000000
PID 9398: fp[0]: 0x0.000d 0000 0000 0000 * 2^0xde8d
PID 9398: fp[1]: 0x0.9e99 e16e 2ac6 0000 * 2^0x0004
PID 9398: fp[2]: 0x0.be5b 00d2 0000 0000 * 2^0x0003
PID 9398: fp[3]: 0x0.f948 0043 0000 0000 * 2^0x9f50
PID 9398: fp[4]: 0x0.9f80 9da5 7fff 0000 * 2^0xbe30
PID 9398: fp[5]: 0x0.a3b0 9da5 7fff 0000 * 2^0xc1d5
PID 9398: fp[6]: 0x0.000d 0000 000f 0000 * 2^0x732f
PID 9398: fp[7]: 0x0.0b21 e104 2ac6 0000 * 2^0x0000
PID 9398: xmm[00]: 0x00000003.00000000.00ce1040.00000000
PID 9398: xmm[01]: 0x00000018.00000000.00000000.00000000
PID 9398: xmm[02]: 0x007a398e.00000000.00000000.00000000
PID 9398: xmm[03]: 0x00000000.00000000.00000000.00000000
PID 9398: xmm[04]: 0x9da5a180.00007fff.9da5a0bc.00007fff
PID 9398: xmm[05]: 0x00799bd0.00000000.00000000.00000000
PID 9398: xmm[06]: 0x00000000.00000000.00000000.00000000
PID 9398: xmm[07]: 0x00000018.00000000.00ce1040.00000000
PID 9398: xmm[08]: 0x00ce1040.00000000.00000000.00000000
PID 9398: xmm[09]: 0x00000000.00000000.00000000.00000000
PID 9398: xmm[10]: 0x0079f2db.00000000.00000018.00000000
PID 9398: xmm[11]: 0x0079b741.00000000.00000000.00000000
PID 9398: xmm[12]: 0x00000000.00000000.00000000.00000000
PID 9398: xmm[13]: 0x9da5a0b0.00007fff.9da5a1b8.00007fff
PID 9398: xmm[14]: 0x9da5a180.00007fff.00000000.00003f90
PID 9398: xmm[15]: 0x00cd9d10.00000000.9da5a180.00007fff
PID 9398: -
> Module List <----
PID 9398: |.text Start |.text End | Module File Name
PID 9398: |0x0000000000400000|0x0000000000991000| /sapdb/SOL/db/pgm/dbmsrv
PID 9398: |0x00002ac6e0cda000|0x00002ac6e0cf5000| /lib64/ld-2.4.so
PID 9398: |0x00002ac6e0df7000|0x00002ac6e0df9000| /lib64/libdl-2.4.so
PID 9398: |0x00002ac6e0efb000|0x00002ac6e0f04000| /lib64/libcrypt-2.4.so
PID 9398: |0x00002ac6e1034000|0x00002ac6e1048000| /lib64/libpthread-2.4.so
PID 9398: |0x00002ac6e114e000|0x00002ac6e1156000| /lib64/librt-2.4.so
PID 9398: |0x00002ac6e1257000|0x00002ac6e133a000| /usr/lib64/libstdc++.so.6.0.8
PID 9398: |0x00002ac6e1455000|0x00002ac6e14a9000| /lib64/libm-2.4.so
PID 9398: |0x00002ac6e15ab000|0x00002ac6e15b8000| /lib64/libgcc_s.so.1
PID 9398: |0x00002ac6e16b8000|0x00002ac6e17ef000| /lib64/libc-2.4.so
PID 9398: -
> Symbolic stack backtrace <----
PID 9398: 0: Lmutex_unlock_17 + 0x1f
PID 9398: SFrame: IP: 0x00002ac6e1041e00 (0x00002ac6e1041de1+0x1f)
PID 9398: Module: /lib64/libpthread-2.4.so
PID 9398: -
PID 9398: 1: __read_nocancel + 0x42
PID 9398: SFrame: IP: 0x00002ac6e1040b3b (0x00002ac6e1040af9+0x42)
PID 9398: Module: /lib64/libpthread-2.4.so
PID 9398: -
PID 9398: 2: teo110_PipeBase::eo110_ReadPipe(int, void, unsigned long, unsigned long&, teo200_EventList) + 0x2e
PID 9398: Symbol: ZN15teo110PipeBase14eo110_ReadPipeEiPvmRmP16teo200_EventList
PID 9398: SFrame: IP: 0x00000000007a398e (0x00000000007a3960+0x2e)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 3: teo110_PipeBase::eo42_RawReceive(void, unsigned long, unsigned long&, teo200_EventList) + 0x1b
PID 9398: Symbol: ZN15teo110PipeBase15eo42_RawReceiveEPvmRmP16teo200_EventList
PID 9398: SFrame: IP: 0x000000000079f2db (0x000000000079f2c0+0x1b)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 4: teo45_RTEProtocolBase::eo45_ReceivePacketSeg(bool, void, unsigned int, teo42_PacketHeader&, unsigned int&, teo200_EventList) + 0xc1
PID 9398: Symbol: ZN21teo45RTEProtocolBase21eo45_ReceivePacketSegEbPvjR18teo42_PacketHeaderRjP16teo200_EventList
PID 9398: SFrame: IP: 0x000000000079b741 (0x000000000079b680+0xc1)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 5: teo45_RTEProtocolBase::eo45_Receive(bool, void, unsigned int, unsigned int&, unsigned char&, tsp01_CommErr_Enum, unsigned int, unsigned int, teo41_Swap, teo200_EventList) + 0x14a
PID 9398: Symbol: ZN21teo45RTEProtocolBase12eo45_ReceiveEbPvjRjRhP18tsp01_CommErr_EnumPjS5_P10teo41_SwapP16teo200_EventList
PID 9398: SFrame: IP: 0x000000000079ba5a (0x000000000079b910+0x14a)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 6: teo45_RTEProtocolBase::eo45_ReceiveRawDataPacket(void, unsigned int, unsigned int&, teo200_EventList) + 0x82
PID 9398: Symbol: ZN21teo45RTEProtocolBase25eo45_ReceiveRawDataPacketEPvjRjP16teo200_EventList
PID 9398: SFrame: IP: 0x000000000079cd62 (0x000000000079cce0+0x82)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 7: sqlxservrecv + 0x5a
PID 9398: SFrame: IP: 0x000000000077d2ba (0x000000000077d260+0x5a)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 8: DBMSrvComm_RTEChannel::receive(DBMSrvFrmReq_Request&, DBMSrvFrmRep_Reply&, tsp00_Enum<tsp01_CommErr_Enum, 11, unsigned char>*) + 0x55
PID 9398: Symbol: ZN21DBMSrvCommRTEChannel7receiveER20DBMSrvFrmReq_RequestR18DBMSrvFrmRep_ReplyP10tsp00_EnumI18tsp01_CommErr_EnumLi11EhE
PID 9398: SFrame: IP: 0x000000000052bda5 (0x000000000052bd50+0x55)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 9: DBMSrvThread_MainThread::DBMSrvThreadMain() + 0x2c0
PID 9398: Symbol: ZN23DBMSrvThreadMainThread16DBMSrvThreadMainEv
PID 9398: SFrame: IP: 0x000000000043fd80 (0x000000000043fac0+0x2c0)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 10: RTEThread_Thread::CThreadMain(void*) + 0x5e
PID 9398: Symbol: ZN16RTEThreadThread11CThreadMainEPv
PID 9398: SFrame: IP: 0x00000000007e61ce (0x00000000007e6170+0x5e)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 11: RTEThread_Thread::AppointMainThreadToThreadObject(int, SAPDBErr_MessageList&) + 0x325
PID 9398: Symbol: ZN16RTEThreadThread31AppointMainThreadToThreadObjectEiR20SAPDBErr_MessageList
PID 9398: SFrame: IP: 0x00000000007e70d5 (0x00000000007e6db0+0x325)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 12: main + 0x10b
PID 9398: SFrame: IP: 0x000000000042ea5b (0x000000000042e950+0x10b)
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
PID 9398: -
PID 9398: 13: __libc_start_main + 0xf4
PID 9398: SFrame: IP: 0x00002ac6e16d5304 (0x00002ac6e16d5210+0xf4)
PID 9398: Module: /lib64/libc-2.4.so
PID 9398: -
PID 9398: 14: __gxx_personality_v0@@CXXABI_1.3 + 0x10a
PID 9398: SFrame: IP: 0x000000000042e89a (0x000000000042e790+0x10a)
PID 9398: Source: start.S:116
PID 9398: Module: /sapdb/SOL/db/pgm/dbmsrv
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.