Symptom
Two different types of queries causing similar stacks:
- An IQ server got aborted with "stcxtlib/st_server.cxx:1927" message due to a problematic query.
**************************************************
*** SAP IQ Abort:
*** From: stcxtlib/st_server.cxx:1927
*** PID: 5776
*** Message: caught signal 11, program abort
*** Thread: 2167 (TID: 2158)
**************************************************
[Stacktace]
hos_ABORT
SigHndlr
_fini
dfjo_Hash::Fetch_T2_IntoHash()
dfjo_Hash::SourcePreFetch()
dfo_Join::SourcePreFetch()
dfjo_Hash::ExecWork(int&,unsigned)
DoWork(unsigned)
It seems like this crash has something to do with some specific values.
The same problematic query worked well if a specific column in WHERE clause has different conditions.
- Another way this can be encountered:
- SELECT INTO #temp2 FROM #temp1 LEFT OUTER JOIN ON T crash at s_phash::Insert
- sp_iqcheckdb verify mode run on the permanent table returns no error.
Excerpt of the stack trace
s_phash::Insert()
dfjo_Hash::Fetch_T2_IntoHash()
dfjo_Hash::SourcePreFetch()
dfo_Join::SourcePreFetch()
dfo::SourcePreFetch()
Read more...
Environment
- SAP IQ 16.0 SP10 PL15
- SAP IQ 16.0 SP11 PL01
- SAP IQ 16.1
Product
Keywords
IQ, st_server.cxx, dfjo_Hash, Fetch_T2_IntoHash, "s_phash::Insert" , , KBA , 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