SAP Knowledge Base Article - Preview

3698480 - IDOC deletion being interrupted and generating DBSQL_SQL_ERROR dumps.

Symptom

  • IDOC Deletion execution is canceled after a long runtime. 
  • You can see that a dump is generated after the job is canceled with the following information:

    Category               ABAP programming error
    Runtime Errors         DBSQL_SQL_ERROR
    Except.                CX_SY_OPEN_SQL_DB
    Application Component  BC-MID-ALE
    ----------------------------------------------------------------------------------------------------

    ----------------------------------------------------------------------------------------------------
    |Short Text                                                                                        
    |    SQL error "SQL code: -10807" occurred while accessing table "<table_name>".                          
    ----------------------------------------------------------------------------------------------------

    ----------------------------------------------------------------------------------------------------
    |What happened?                                                                                    
    |    Database error text: "SQL message: Connection down: [89006] System call 'recv'                
    |     failed, rc=104:Connection reset by peer {<ip_address> ->                               
    |     <ip_address> TenantName:(none) SiteVolumeID:0:3 SiteType:NONE                          
    |     ConnectionID:<connection_id> SessionID:****}"                                             
    ----------------------------------------------------------------------------------------------------

  • In the Indexserver trace files you can see that a long-living cursor was suspended and it was probably blocking garbage collection.

    [0000000]{-1}[-1/-1] 0000-00-00 00:00:00.000000 e KernelSentinel   KernelSentinelJob.cpp(01689) : There are too many un-collected versions on table '<table_name>' (TABLE_OID = <table_name>, NUM_VERSIONS = 179913, MIN_READ_TIMESTAMP = 7712315034).
    The cursor possibly blocks the garbage collection: 

    [0000000]{000000}[00/00000] 0000-00-00 00:00:00.000000  i SQLSessionCmd    Statement.cc(06623) : session control command is performed by <connection_id>, client ip=, client port=0, query=ALTER SYSTEM DISCONNECT SESSION '<connection_id>' 

    [0000000]{-1}[-1/-1] 0000-00-00 00:00:00.000000  e KernelSentinel   KernelSentinelJob.cpp(00748) : Killed long-lived suspended cursor. tid=0, connId=<connection_id>, duration(s)=44556, lifetime(s)=43200, workloadClass=_SYS_DEFAULT 


Read more...

Environment

SAP HANA database

Product

SAP HANA, platform edition all versions

Keywords

sql error -10807, connection down, recv failed, suspended cursor lifetime, garbage collection, IDoc deletion, SAP HANA, database interruption, long-running transaction, Kernel Sentinel, DBSQL_SQL_ERROR , KBA , HAN-DB-ENG , SAP HANA DB Engines , 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.