SQL0501N The cursor specified in a FETCH statement or CLOSE statement is not open or a cursor variable in a cursor scalar function reference is not open. SQLSTATE=24501
SQL0501N The cursor specified in a FETCH statement or CLOSE statement is not
open or a cursor variable in a cursor scalar function reference is not open.
SQLSTATE=24501
I am facing the above error while executing a Db2 procedure.
FETCH using a cursor at a time when the specified cursor was not open.
CLOSE a cursor at a time when the specified cursor was not open.
Reference a cursor variable in an OPEN statement and the cursor variable is not open.
Reference a cursor scalar function, such as CURSOR_ROWCOUNT function, and the cursor variable is not open.
The statement cannot be processed.
User response
Check for a previous message (SQLCODE) that may have closed the cursor. Note that after the cursor is closed, any fetches or close cursor statements receive SQLCODE -501.
If no previous SQLCODEs have been issued, correct the application program to ensure that the cursor is open when the FETCH or CLOSE statement is executed.
If a cursor variable is referenced in a cursor scalar function, verify that that the cursor is not null, is defined, and is open, else replace the cursor variable with one that is in that state.
Usually this just means that you tried to FETCH or CLOSE a cursor that isn't open. Usually this is due to a defect in your code. Maybe the OPEN failed and you didn't detect it, for example.
Prardhan N
ASKER
Yes, i have changed my for cursor statements to while cursor and error is not throwing now.
but i need to know how to use the data studio to trace the particular order value (i mean for a particular data value) for step by step
tracing of my procedure code.
Gary Patterson, CISSP
Here is a great tutorial on debugging IBM i DB2 stored stored procedures in IBM Data Studio:
The current transaction has been rolled back because of a deadlock or timeout. Reason code "68".. SQLCODE=-911, SQLSTATE=40001, DRIVER=4.18.60
The current transaction has been rolled back because of a deadlock or timeout. Reason code "68".. SQLCODE=-911, SQLSTATE=40001, DRIVER=4.18.60
facing this error while compiling the Procedure.
I have cleared the locks. but still same issue while compilation. Is this happening while prepare
Kent Olsen
Can you post the SQL that you're trying to compile?
By my count, this is the third different question posted in this single thread. Please close this question and open a new one - you may get more experts to respond.
Prardhan N
ASKER
Thanks for all your help with this regard. Appreciating your efforts.