Symptom
Blocked transactions and/or high number of similar statements are observed in the system.
As a possible symptom runtime dumps show blocked transactions with following system calls:
SQL: call _SYS_STATISTICS.STATISTICS_SCHEDULABLEWRAPPER('Timer',?, ?, ?, ?)
These calls are blocked by an IDLE connection from DB User: _SYS_STATISTICS
Other runtimedumps may show high number of similar statements waiting in thread method "NoAction".
It is visible that many different connections are opened by the same application.
99% of threads waiting in the following call stack:
syscall
syscall
Synchronization::BinarySemaphore::timedWait
Executor::X2::calculate
Executor::PlanExecutor::calculateX2
Executor::PlanExecutor::calculate
ptime::TrexExecutor::calculate
ptime::X2ExecutableTable::open_trex_executor
ptime::Project_copy::do_open
ptime::Table::open
ptime::Query::result_t::open
ptime::ResultSet::open_
ptime::Statement::post_execute_
ptime::Statement::execute_
ptime::PreparedStatement::execute)
ptime::ActionExecutor::executeQuery
ptime::ActionExecutor::executeQid
ptime::ActionExecutor::executeAction
ptime::SessionHandler::executeAction
.LTHUNK390.lto_priv.1
ptime::SessionHandler::receiveMessage_
ptime::SessionHandler::receiveMessage
ptime::TcpReceiver::doWork
ptime::TcpReceiver::run
TrexThreads::PoolThread::run()
TrexThreads::PoolThread::run
Execution::Thread::staticMainImp
Execution::pthreadFunctionWrapper
start_thread+0xc1
__clone+0x69
Statements show that all of these connections are generated by application name "com.dynatrace.datasource.SQL".
Read more...
Environment
SAP HANA 2.0
Product
Keywords
long-running blocking transaction, slow access, , 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.