SAP Knowledge Base Article - Preview

2905558 - ERP migration to SAP HANA 2.0 fails with "Lock-wait time out exceeded"

Symptom

  • Indexserver trace shows e.g.:

    Lock-wait time out exceeded

    - Waiting transaction

    [CONNID=219995, SESSIONID=219995, CLIENT_HOST=myhost.com , CLIENT_IP=***.**.**.** , CLIENT_PID=*****, APPUSER = user1, DBUSER=SYSTEM, ID=01, UPDATE_TRANSACTION_ID=723000, TYPE=USER, STATE=ACTIVE, ISOLATION_LEVEL=RC, LOCK_TIMEOUT_MS=1800000]

    - Blockers

    [CONNID=200005, SESSIONID=200005, CLIENT_HOST=, CLIENT_IP=, CLIENT_PID=0, DBUSER=SYSTEM, ID=65, UPDATE_TRANSACTION_ID=707985, TYPE=USER, STATE=ACTIVE, ISOLATION_LEVEL=RC]

    [CONNID=200004, SESSIONID=200004, CLIENT_HOST=, CLIENT_IP=, CLIENT_PID=0, DBUSER=SYSTEM, ID=64, UPDATE_TRANSACTION_ID=710844, TYPE=USER, STATE=ACTIVE, ISOLATION_LEVEL=RC]

  • Connection which are blocking belong to _SYS_STATISTICS
  • HANA restart the tenant and a recovery is issued.


Read more...

Environment

  • SAP ERP 6.0
  • HANA 2.0

Product

SAP ERP 6.0 ; SAP HANA, platform edition 2.0

Keywords

KBA , HAN-LM-INS-DB , Installation of HANA Database , 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.