SAP Knowledge Base Article - Preview

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

Symptom

During an ERP migration to SAP HANA 2.0, the process fails and the SAP HANA indexserver trace shows lock timeout errors similar to:

  • 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]

The blocking connections belong to the _SYS_STATISTICS user/schema.

As a consequence, the SAP HANA tenant may be restarted and a recovery is triggered.


Read more...

Environment

SAP HANA DB Version 2.0

Product

SAP HANA, platform edition 2.0

Keywords

SAP HANA, ERP migration, HANA 2.0, lock-wait time out exceeded, lock timeout, _SYS_STATISTICS, statistics server, nameserver.ini, indexserver.ini, tenant restart, DB migration, SUM, DMO , 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.