Symptom
A query caused server crash while a node took 'Hash' join.
Currently, the same crash was reproduced on customer DB, whenever the same query was executed
Customer found workaround for this issue. The sql can run normally when disable hash join
or setting max_hash_rows to a very low value (let optimizer didn't choose hash join).
But the application is a self-service platform , all the sql were automatic generated by application server,
customer could not disable hash join temporaryly with specific sql.
* IQmsg & stack =>
I. 04/01 10:38:48. 0000032219
I. 04/01 10:38:48. 0000032219 **************************************************
I. 04/01 10:38:48. 0000032219 *** SAP IQ Abort:
I. 04/01 10:38:48. 0000032219 *** From: stcxtlib/st_server.cxx:1708
I. 04/01 10:38:48. 0000032219 *** PID: 7482
I. 04/01 10:38:48. 0000032219 *** Message: caught signal 11, program abort
I. 04/01 10:38:48. 0000032219 *** Thread: 140396275009280 (TID: 3614)
I. 04/01 10:38:48. 0000032219 **************************************************
...
..
.. DumpAllThreads..
.. hos_ABORT..
.. SigHndlr+0x4f
..
.. hos_dfe_SINT64_CMP_W_NULLS ..
.. df_DataForComparison::EvaluateComparison ..
.. dfjo_Merge::FillStoreWithNextMatchingGroup ..
.. dfjo_MergeBase::FirstFetch ..
.. dfjo_MergeKeyed::FetchOpus ..
.. dfo_GroupByUnordered::FirstFetch ..
.. dfo_GroupByUnordered::FetchOpus ..
.. dfo_cOrderByParaIn::ExecWork ..
.. workAllocator::DoWork ..
Read more...
Environment
IQ 16.0 SP8.39(+)
Product
Keywords
"SINT64_CMP_W_NULLS" ; "dfjo_Merge::FillStoreWithNextMatchingGroup" ; , 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.