2967396 - Long running idle cursors by J2EE_CONFIGENTRY table

There are long running cursors detected and disconnected as follows.

1. Runtime Dump

M_DEV_KERNELSENTINEL_ACTION_HISTORY[0] - (id= 409, type= dev:local, flags= AddVolumeID Crashdump RTEdump, priv= <none>)

TYPE | REASON | ACTION_TIME | TARGET_CONNECTION_ID | TARGET_UPDATE_TID | ACTION_TAKEN
LONGRUNNING_IDLE_CURSOR | idle duration: 43268 > timeout: 43200 | 1599361687836000 [local] | 217509 | 0 | Disconnect session

2. indexserver_xxx.trc

KernelSentinel KernelSentinelJob.cpp(00546) : Killed long-running idle cursor. tid=0, connId=250069, duration(s)=46286, lifetime(s)=43200, workloadClass=_SYS_DEFAULT

3. Detected IDLE Cursor Statements are same as follows.

1900261 How to handle HANA Alert 42: 'Long-Running Cursors'

1) SELECT P.HOST, P.PORT, C.LOGICAL_CONNECTION_ID, C.CLIENT_HOST, C.CLIENT_PID,
P.STATEMENT_STATUS, P.STATEMENT_STRING, SECONDS_BETWEEN (P.LAST_EXECUTED_TIME, CURRENT_TIMESTAMP) IDLE_TIME, P.START_MVCC_TIMESTAMP
FROM M_PREPARED_STATEMENTS P, M_CONNECTIONS C
WHERE P.HOST = C.HOST AND P.PORT = C.PORT AND P.CONNECTION_ID = C.CONNECTION_ID AND C.CONNECTION_ID > 0
AND SECONDS_BETWEEN (P.LAST_EXECUTED_TIME, CURRENT_TIMESTAMP) > 0
AND P.STATEMENT_STATUS <> 'NONE';

2) Select * from "_SYS_STATISTICS"."HOST_LONG_IDLE_CURSOR_BASE"

3) Common statements from those SQL Statements with suspended status.
- SELECT "FBLOB" FROM "J2EE_CONFIGENTRY" WHERE "CID" = ? AND "NAMEHASH" = ? AND "NAME" = ? AND "ISFILE" = ?
THe STATEMENT_HASH for above SQL is 969667ed5f022a232f710b5a5af51dff.

Image /data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP HANA, platform edition 2.0 

J2EE, CONFIGENTRY, SUSPENDED, long-running, cursor, LONGRUNNING, J2EE_CONFIG, J2EE_CONFIGENTRY , KBA , HAN-DB-CLI , SAP HANA Clients (JDBC, ODBC) , HAN-DB , SAP HANA Database , HAN-DB-MON , SAP HANA Monitoring , Problem