Symptom
- A data manipulation language statement (SELECT, INSERT, UPDATE, DELETE) is called from an application server to a HANA Database.
- The statement terminates with this abap dump:
Category ABAP Programming Error
Runtime Errors TIME_OUT
ABAP Program SAPLSNR3
Short Text
Time limit exceeded
Error analysis
After a certain time, the program is terminated in order to free the
workspace for other users. This prevents workspaces from being blocked
unnecessarily, for example by an endless loop (DO, WHILE, ...), by
database accesses where the result set is too large or by database
accessess without a suitable index Index (full table scan).
The maximum runtime of a program is set by system profile parameter
"rdisp/scheduler/prio_[high|normal|low]/max_runtime". The current setting is
600 seconds. Once this limit has been
exceeded, the system attempts to interrupt the SQL statement or to
instruct the ABAP processor to terminate the program. It waits for a
maximum of 60 seconds. If the program is then still active, the work
process is restarted.
- This entry is written into the indexserver trace in Hana:
[145091]{362443} TraceContext TraceContext.cpp(00827) : UserName=SAPR31
[145091]{362443} SQLSessionCmd Statement.cc(05941) : session control command is performed by 362443, user=SAPR31, application user=,
application source=, client ip=10.21.10.55, client port=26451, query=ALTER SYSTEM CANCEL SESSION '318175'
[145091]{362443} SQLSessionCmd Connection.cc(07545) : cancel requested for 318175 (logical connection id is 318175
Read more...
Environment
SAP Hana Database 1.0.
Product
SAP HANA, enterprise edition all versions
Keywords
KBA , HAN-DB , SAP HANA Database , PP-MRP , Material Requirements Planning , 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.