Symptom
SELECT statements against the changelog of IMO DSOs are exhibiting a worse than expected performance and are effectively hanging. An example statement may look like this:
SELECT "O1"."DOC_NUM" AS "DOC_NUM" ,"O1"."DOC_ITEM" AS "DOC_ITEM"
,"O1"."PSTNG_DATE" AS "PSTNG_DATE" ,"O1"."DOC_YEAR" AS
"DOC_YEAR" ,"O1"."RECORDMODE" AS "RECORDMODE" ,"O1"."PROCESSKEY"
...
FROM "/BIC/B0001722000" "O1" WHERE
( ( ( ( "O1"."DATAPAKID" BETWEEN '000001' AND '000001'
) ) AND ( ( "O1"."REQUEST" = 'ODSR_....'
) ) ) ) ORDER BY "O1"."DATAPAKID" , "O1"."RECORD";
The relevant threads are usually hanging with a call stack similar to the following one:
TRexUtils::BitVector::setRange
UnifiedTable::MVCCObject::generateOLAPBitmap
UnifiedTable::MVCCReader::generateValidList
TrexStore::UdivsMVCC::reCreateUdivList
TrexStore::UdivListContainerMVCC::reCreateUdivList
TrexStore::UdivListContainerMVCC::getAllCommitted
TrexStore::UdivListManagerImpl::getAllCommitted
TRexAPI::TRexApiSearch::lockSearchIndexes
TRexAPI::TRexApiSearch::doSearch
TRexAPI::TRexApiSearch::search
TRexAPI::Partitioning::Search::searchPartitionedIndex
TRexAPI::TRexApiSearch::doSearch
TRexAPI::TRexApiSearch::search
TRexAPI::TRexApiSearch::requestToOneServer
TRexAPI::TRexApiSearch::searchNet
TRexAPI::TRexApiSearch::doSearch
TRexAPI::TRexApiSearch::search
TrexCalculationEngine::CustomCpp::ceDsoChangelogSearchOp::doSearch
TrexCalculationEngine::CustomCpp::ceDsoChangelogSearchOp::execute
TrexCalculationEngine::CustomCpp::ceCustomCppPop::executePopInternal
Read more...
Environment
SAP HANA, platform edition 2.0
Product
SAP HANA, platform edition 2.0
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.