2458005 - Dump DBIF_RSQL_INVALID_RSQL/ DBSQL_TOO_MANY_OPEN_CURSOR occurs at program SBAL_DELETE

• SBAL_DELETE report is running on the system, either in Dialog mode either as a Background Job, in order to remove logs from Application Log tables.
   
• When running this report, it gets canceled due to DBSQL_TOO_MANY_OPEN_CURSOR dump (it can also be DBIF_RSQL_INVALID_RSQL dump).
  
  For instance, you can see on JobLog:
    Date             Time          Message text
    dd.mm.yyyy hh:mm:ss   Job started
    dd.mm.yyyy hh:mm:ss   Step 001 started (program SBAL_DELETE, variant <Variant_Name>, user ID <BTC_user>)
    dd.mm.yyyy hh:mm:ss   Database commit done every 100 logs
    dd.mm.yyyy hh:mm:ss   Internal session terminated with a runtime error DBSQL_TOO_MANY_OPEN_CURSOR (see ST22)
    dd.mm.yyyy hh:mm:ss   Job canceled
   
• Relevant information is displayed over ST22 dump:
  

  Termination occurred in the ABAP program "SBAL_DELETE" - in
  "DELETE_WITH_CURSOR".
  The main program was "SBAL_DELETE ".

  In the source code you have the termination point in line 1234
  of the (Include) program "SBAL_DELETE".
  The program "SBAL_DELETE" was started as a background job.
  Job Name....... "XXXXXXX"
  Job Initiator.. "XXXNNN"
  Job Number..... NNNNNN

• Dump DBSQL_TOO_MANY_OPEN_CURSOR can also happen showing information similar to:
  

  Termination occurred in the ABAP program "SAPLSTRD" - in
  "TRINT_READ_NAMESPACE_FROM_PAT".
  The main program was "SBAL_DELETE ".

  The termination occurred in ABAP program "SBAL_DELETE", in
  "DELETE_AUTHORITY_CHECK". The main program was "SBAL_DELETE ".

SAP AS NetWeaver system.

DBIF_RSQL_INVALID_RSQL, DBSQL_TOO_MANY_OPEN_CURSOR, SBAL_DELETE, DELETE_WITH_CURSOR, DELETE_AUTHORITY_CHECK, SOLMAN_BTC, SOLMAN_BATCH , KBA , BC-SRV-BAL , Basis Application Log , Problem