Solution : https://service.sap.com/sap/support/notes/2104 (SAP Service marketplace login required)
Summary :
This SAP Note addresses various runtime terminations marked by "INVALID_CURSOR" issues such as DBIF_RSQL_INVALID_CURSOR, DBIF_DSQL_INVALID_CURSOR, among others. These problems occur when mass data processing is disrupted by a database commit and then attempts to continue within the same session. Particular situations like in-loop COMMIT or ROLLBACK operations, screen transitions due to CALL SCREEN commands, and message handling in ABAP debugger can trigger these issues. The recommended solution involves configuring the rdisp/wpdbug_max_no profile parameter to allocate more work processes for debugging, potentially increasing the parameter rdisp/wp_no_dia to handle additional load.
Key words :
- dbif_rsql_invalid_cursor- dbif_dsql_invalid_cursor- dbif_dsql2_invalid_cursor- dbif_rtab_invalid_cursor, programsor screens require regeneration, screen change takes place, profile parameter rdisp/wpdbug_max_nofor, abap/4 logical databases - depending, loop loops overthe database, parameter rdisp/wp_no_dia, rdisp/wpdbug_max_no = 10sets, symptom key word, invalid_cursorrun-time terminations
Related Notes :
| 331662 | DBIF_RSQL_INVALID_CURSOR when executing RM06ENP1 |
| 121008 | RMBABG00: Data volume invoice verification |
| 675 | Unexpected abends in SELECT loops (COMMIT) |