Symptom
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
After a BW upgrade, specific queries using long in-lists are exhibiting a worse than expected runtime. Based on the HANA python traces (KBA 3262041), those queries look like this:
fuzzypy.ColumnBase('<key>', fuzzypy.ColumnType('string', 0, 0, 11))]) #StringColumn, STRING(int=0, fract=0, size=0, sqlType=11), 788rows, 16.22kbitab.set(0, [
'VAL1',
'VAL2',
'VAL3',
'VAL4',
'VAL5',
...
qo = fuzzypy.QueryEntry()
qo.setLocation('<SID>.500.000D3A6679981EDD99B2163098126F1C_INT_FAE')
qo.setValue('\x01\x0b<key>', '', 'EQ')
During the query runtime, call stacks like the following one are frequently visible:
ptime::qo_Normalizer::translate_to_disjunctive_normal_form
ptime::qo_TrexSearch::predicateNormalizeForPartitionPruningImpl
ptime::qo_TrexSearch::predicateNormalizeForPartitionPruning
ptime::qo_TrexSearch::findRelevantPartsWithFilters
Read more...
Environment
SAP HANA, platform edition 2.0
Product
Keywords
KBA , HAN-DB-ENG-BW , SAP HANA BW Engine , 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