A DELETE query session goes pending status with spending CPU usage on IQ16.1 SP2.14. But the same delete query has been working well in old version SP02.03 without any symptoms.
While repro test, found below status.
It looks the delete query goes infinite loop , spendign CPU.
Repro is available ONLY when Non_Ansi_Null_Varchar ='ON', default is OFF.
Under Non_Ansi_Null_Varchar ='OFF', any delete is working well. But customer has been using the option to ON from prior versions , and now it's hard to convert the option to OFF due to existing queries.
When dumps stack during the pending status, it looks incorrectly working at 's_llhtable::hti_lookup_delete'.
Thread 187 (Thread 0x7fcc0eeb8700
.. s_llhtable::hti_lookup_delete ..
.. s_llhtable::hti_cas_delete ..
.. s_llhtable::ht_cas_delete ..
.. s_llhtable::deleteToken ..
.. s_dictionary::DeleteKeyFromHash ..
.. s_dictionary::SqueezeStrArray ..
.. s_dpNBit::Delete ..
.. hs_dp::DeleteNBit ..
.. hs_dp::DeleteInternal ..
.. hs_dp::Delete ..
.. hdb_delete_indices::Unit_of_Work ..
SAP IQ16.1 SP02.14
delete hang, drop connection, hti_lookup_delete , DeleteKeyFromHash , CR819197, , KBA , BC-SYB-IQ , Sybase IQ , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.