Symptom
Canceling a complex, long‑running query causes the server to crash and produce a stack trace.
A signal 11 is raised and reported in an "IQ abort" message (for example: caught signal 11 at stcxtlib/st_server.cxx:2490).
Stack trace examples reference components such
hs_btCache::~hs_btCache
s_subohcBTCursor<s_btfdiskblock,s_btfitem>::__Destruct
s_keyRangeWorkDesc::~s_keyRangeWorkDesc
s_keyRangeWorkDesc::__dftdt
unknown
s_keyRangeWorkAllocatorBase::~s_keyRangeWorkAllocatorBase
s_BTkeyRangeWorkAllocator::~s_BTkeyRangeWorkAllocator
s_ohcKeyRangeWorkAllocator::~s_ohcKeyRangeWorkAllocator
dfo_cOrderByParaIn::ShutdownSink
dfo::DestroyLastLeaf
dfo_Root::~dfo_Root
st_cursor::__Destruct
st_cursor::~st_cursor
st_cursorIQtoSA::~st_cursorIQtoSA
df_dmlcommand::~df_dmlcommand
df_OpenCursor::__dftdt
unknown
unknown
hos_attnexception::doThrow
Read more...
Environment
- SAP IQ 16.1
Product
Keywords
cancel query crash, server crash on cancel, signal 11, hos_attnexception, sqlcode -299, sqlstate 57014, stack trace, order by parallel, dfo root, hs_btcache, key range work allocator, cursor active, multiplex coordinator, aix, request logging , 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