Symptom
A BW query exhibits an unexpectedly long runtime. Further investigation on HANA side show the following in addition:
1.
The created planviz shows that the largest part of the query runtime is spent in CeQoPop Compile:
2.
Call stacks of the involved HANA threads look similar to the one below:
...
ptime::qo_VisitorUtilImpl::check_all_internal
ptime::qo_VisitorUtilImpl::check_all_internal
ptime::qo_VisitorUtilImpl::check_all_internal
ptime::qo_VisitorUtilImpl::check_all_internal
ptime::qo_VisitorUtilImpl::check_all_internal
ptime::qo_VisitorUtilImpl::check_all_internal
ptime::qo_VisitorUtilImpl::check_all_internal
ptime::qo_VisitorUtilImpl::check_all_internal
ptime::qo_VisitorUtil::qo_check_all_exprs
...
3.
The python trace created via transaction RSRT contains several internal tables with hundreds of entries:
itab = fuzzypy.InternalTable('XXX.000.005056879E8A1EEDA49AB575FF620129_INT_FAE', [
fuzzypy.ColumnBase('X95_COSTL_KEY', fuzzypy.ColumnType('string', 0, 0, 11))]) #StringColumn, STRING(int=0, fract=0, size=0, sqlType=11), 899rows, 80.41kb
itab.set(0, [
'0003304865',
'LVP017',
...
# skipping row 150 ... 749
'UML100',
'0003520010',
'0003520016',
'UML012',
...
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Product
Keywords
KBA , HAN-DB-PERF , SAP HANA Database Performance , 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.