Symptom
When executing BPC reports, the report runtime is slower than expected. Creating an ST12 trace of the report's execution shows that most of the runtime is consumed by execution of a native SQL statement triggered by the function module TREX_EXT_INDEX_CELL_TABLE_V2:
The executed native SQL statement is the following:
HASH: 6ea085309583e2436162a48b8cc62cb4
select
schema_name as dd_schema_name,
table_name as dd_table_name,
host as host,
port as port,
schema_name as db_schema_name,
table_name as db_table_name,
table_oid as table_oid,
comments as comments,
fixed_part_size as fixed_part_size,
connection_id as connection_id,
statement_id as statement_id,
record_count as record_count,
table_size as table_size,
is_logged as is_logged,
is_system_table as is_system_table,
is_column_table as is_column_table,
is_insert_only as is_insert_only,
is_tenant_shared_data as is_tenant_shared_data,
is_tenant_shared_metadata as is_tenant_shared_metadata,
session_type as session_type,
is_temporary as is_temporary,
temporary_table_type as temporary_table_type,
is_user_defined_type as is_user_defined_type,
preload as preload
from sys.m_temporary_tables
where schema_name = ?
and table_name = ?
"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...
Environment
BPC, SAP HANA Platform Edition 2.0
Product
SAP HANA, platform edition 2.0
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.