SAP Knowledge Base Article - Preview

3220938 - Killed long-lived suspended cursor. tid=<>, connId=<>, duration(s)=<>, lifetime(s)=<>

Symptom

  • A long running suspended cursor is killed on a Tenant HANA DB. The below entries from the Kernel sentinel trace are observed in the indexserver trace and alert files :
       
     indexserver_alert_hostname.trc
     ++++++++++++++++++++++++++++++++++
       [114326]{-1}[-1/-1] 2022-06-21 20:41:31.778284 e KernelSentinel   KernelSentinelJob.cpp(00747) : Killed long-lived suspended cursor. tid=1560367060, connId=316082, duration(s)=43320, lifetime(s)=43200, workloadClass=_SYS_DEFAULT  


     indexserver_hostname.3xxx0.000.trc
     ++++++++++++++++++++++++++++++++++++++
     [114326]{300412}[44/1560532628] 2022-06-21 20:41:31.765015 i TraceContext     TraceContext.cpp(01347) : UserName=, StatementHash=860091cf6b41ce474d6cd7c1745e95d6, StatementExecutionID=844437902421035
     [114326]{300412}[44/1560532628] 2022-06-21 20:41:31.765015 i SQLSessionCmd    Statement.cc(06531) : session control command is performed by 300412, client ip=, client port=0, query=ALTER SYSTEM DISCONNECT SESSION '316082'
       [114326]{300412}[44/1560532628] 2022-06-21 20:41:31.772489 i SQLSessionCmd    sm_manager.cc(02124) : cancel requested:, globalSessionId=316082 anchorGlobalSessionId=316082, requestId=844437902421039, cancelTime=1655854891772481. requested by:    globalSessionId=300412, anchorGlobalSessionId=300412, application=, applicationUser=,     XSApplicationUser=SYSTEM, applicationComponentName=, applicationComponentType=, clientHost=, clientIp=. cancel reason: By connection close/lost

  

  • ABAP Dumps like the following may be observed in ST22 for the terminated client session.
      
      Category               ABAP programming error
      Runtime Errors         DBSQL_SQL_ERROR
      Except.                CX_SY_OPEN_SQL_DB
      ABAP Program           CL_FINS_ACDOC_SELECT==========CP
      Application Component  FI-GL
        Date and Time          21.06.2022 20:41:31 (BRAZIL)

      ----------------------------------------------------------------------------------------------------
      ----------------------------------------------------------------------------------------------------
      |Short Text                                                                                        |
      |    SQL error "SQL code: -10807" occurred while accessing table "ACDOCA".                         |
      ----------------------------------------------------------------------------------------------------
      ----------------------------------------------------------------------------------------------------
      |What happened?                                                                                    |
      |    Database error text: "SQL message: Connection down: [89006] System call 'recv'                |
      |     failed, rc=104:Connection reset by peer {xxx.xxx.xxx.xxxx:port ->                             |
        |    xxx.xxx.xxx.xxxx:port}"                                                                       |

        ----------------------------------------------------------------------------------------------------

 

  • Mini Check (KBA 1999993) alerts may also report garbage collection issues like : M0841 Oldest active update transaction current (h)  11.07 <= 3.00 X 2169283

 

  • A review of the historic garbage collection blocker(s) shows a long running cursor in a 'suspended/idle' state under "STATUS_DETAILS" : HANA_GarbageCollection_Blockers_History_2.00.060+.txt' (Note 1969700)

         
 


Read more...

Environment

SAP HANA, platform edition 2.0 >= SPS06

Product

SAP HANA, platform edition 2.0 ; SAP S/4HANA 1909

Keywords

KBA , HAN-DB , SAP 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.