Symptom
- Connection to SAP IQ NLS could crash.
- Sometimes, a core file is generated.
- In dev_w worker process log, a memory address and OS SIGSEGV (Signal l1) issue can be seen.
Excerpt of dev_w log
B Loading DB library '/usr/sap/<SID>/D00/exe/dbsybslib.so' ...
B Library '/usr/sap/<SID>/D00/exe/dbsybslib.so' loaded
B Version of '/usr/sap/<SID>/D00/exe/dbsybslib.so' is "777.05", patchlevel (0.500)
C trace file set
B Connect to RISEAID as DBA with SYBASE_CONTYPE=IQ SYBASE_SERVER=<IQ Server Hostname> SYBASE_PORT=30038 SYBASE_IQ_ENGINE=<IQ engine name> SYBASE_DBNAME=SAPIQDB SYBASE_IQ_LOCKWAIT=600
C using lock wait time 600 for Sybase IQ.
C load of IQ library libdbodbc17.so successful.
M si_code = 1
M Sending process ID = 0
M Real user ID of sending process = 0
M SEGV_MAPERR: Address not mapped to object
M (nil) (Memory location which caused fault)
M ------------------ C-STACK ----------------------
dw.sap<SID>_D00[S](LinStackBacktrace(void**, int, int)+0xa9)[0x559f353b35ca,0x7225ca]
dw.sap<SID>_D00[S](LinStack(_IO_FILE*)+0x4d)[0x559f353b7253,0x726253]
dw.sap<SID>_D00[S](CTrcStack2+0x4b)[0x559f353b3007,0x722007]
dw.sap<SID>_D00[S](SigIGenAction+0x9ce)[0x559f377a592e,0x2b1492e]
M ------------------ c-stack end ------------------
M ***LOG Q0E=> SigIGenAction, signal ( 11) [sigux.c 1928]
M caught SIGSEGV (11)
M ThSigHandler (terminate=0, reason=Signal)
M in_ThErrHandle: 1
M ThIErrHandle: set thRc ERROR-CORE-ABORTED_BY_SIGNAL for T4_U5916_M0
M ThResetEmMagic: reset em magic for T4_U5916_M0_I0
M ThIErrHandle: handle 'ThSigHandler: Signal' for T4_U5916_M0 (step TH_WORK_SYNC, thRc ERROR-CORE-ABORTED_BY_SIGNAL, action RETURN_FOR_DUMP)
X MmxCheckOpenHandles: No open MMX handles
Read more...
Environment
- SAP IQ Server 16.1
- SAP IQ Network Client 16.1
- SAP BW 2.0
Product
Keywords
"Signal 11" ; "SEGV_MAPERR: Address not mapped to object" ; SEGV_MAPERR ; nil ; "Memory location which caused fault"; memory ; fault ; , KBA , BW-SYS-DB-IQ , BW on HANA with Sybase IQ Near-line Storage , BC-SYB-IQ , Sybase IQ , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview