Ansicht
Dokumentation

Unexpected abends in SELECT loops (COMMIT) <br />Tip-No.: 675 ( INFO675 )

Unexpected abends in SELECT loops (COMMIT)
Tip-No.: 675 ( INFO675 )

PERFORM Short Reference   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

Short text

Unexpected abends in SELECT loops (COMMIT)
Tip-No.: 675

Symptom

At run-time, an abend with SQL error occurs within a SELECT loop after
a commit.
"Run-time error DBIF_RSQL_INVALID_CURSOR"
(Whether the SELECT loop was created using SAP-SELECT or EXEC SQL
is not important).

Cause

Chain of causes:

1 There is a statement in one of the Select loops, that leads to a
database Commit (or Rollback).
2 A database Commit causes the database to lose the cursor.
3 The system cannot automatically continue within Select loop after
loss of cursor.

Following statements lead to a database Commit:

- All statements that cause a change of screen (CALL SCREEN,
CALL DIALOG, CALL TRANSACTION, SUBMIT, I/W-Message)

- BREAK-POINT / Debugging
. if no debug process free
. always after regeneration (in order to release generation lock).

- COMMIT WORK/ROLLBACK WORK

Solution

Within Select loops, do not use statements that lead to a database
Commit.






CPI1466 during Backup   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 1200 Date: 20240329 Time: 161008     sap01-206 ( 13 ms )