‎2019 Jul 10 3:50 PM
Hello
how to handle Non-Catchable exception in abap
like "EXSQL_DSQL_DUPLICATE_CURSOR"
thank you
‎2019 Jul 11 10:11 AM
Oh yes, I see. I saw the word duplicate, but not the word cursor.
The advice remains - you need to make sure the error doesn't happen, rather than try to catch it. There is clearly a programming error - your trying to open a cursor that's the same as the one you've already got. The documentation says
The specified cursor is already open. An OPEN command command in Native SQL has a specified cursor, which the cursor administration knows is already open.
Rather than Native SQL, use the CL_SQL_... classes. Then you'll get catchable errors.
‎2019 Jul 10 6:10 PM
Make sure there are no duplicates before executing the code.
‎2019 Jul 11 6:42 AM
Hi
yes , i use only one cursor in my code
‎2019 Jul 11 7:26 AM
Duplicate records.
‎2019 Jul 11 8:31 AM
my query is not has duplicate record
the Short Text of error is "The specified cursor is already open."
but i do not have specify that the cursor is open or not
thanks
‎2019 Jul 11 7:44 AM
Whatever the exception is, a "Non-Catchable exception" cannot be "handled". It just stops.
But maybe you can prevent the exception from happening... So you should tell us more about your code!
‎2019 Jul 11 8:23 AM
Hello Sandra
i now that this error may be occured for example when Fetch Next Cursor into work area ,does not match corresponding field of query with work area
Anyway i wants handle "non-catchable" exception in my abap code .
That is not possible
thanks
‎2019 Jul 11 10:11 AM
Oh yes, I see. I saw the word duplicate, but not the word cursor.
The advice remains - you need to make sure the error doesn't happen, rather than try to catch it. There is clearly a programming error - your trying to open a cursor that's the same as the one you've already got. The documentation says
The specified cursor is already open. An OPEN command command in Native SQL has a specified cursor, which the cursor administration knows is already open.
Rather than Native SQL, use the CL_SQL_... classes. Then you'll get catchable errors.
‎2019 Jul 11 11:24 AM
Thank you Matthew Billingham
in Native SQL ,before open my cursor how to define its open , for close it .
if the cursor is not close or program encounter with short dump , the cursor is open in background and Apparently its maintain in sap system cash.
‎2019 Jul 11 12:36 PM
As I said:
Rather than Native SQL, use the CL_SQL_... classes. Then you'll get catchable errors.