View previous topic :: View next topic
|
Author |
Message |
sumivel
New User
Joined: 13 Sep 2005 Posts: 18
|
|
|
|
My cursor fetches 18,22,749 number of rows.
To reduce the run time i declared the
cursor with Rowset Positioning.
i.e FETCH NEXT ROWSET TAX_CSR FOR 100 ROWS
in the above case i am getting -904(resource
not available) after fetching some 291489
rows.
The same cursor without this multiple
row fetch logic is working fine.whereas with rowset positioning i am getting -904.
can anybody tell me the process to solve this error |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Is the -904 always after the same number of fetched rows?
What is the reason code? What other diagnostic information was presented (look in the jes sysout datasets).
What type of resource failed and what was the name of that resource?
I'd suggest you look into the "DB2 Messages & Codes" linked to from the "Manuals" link at the top of the page. |
|
Back to top |
|
|
Santoshdorge
New User
Joined: 27 Jun 2006 Posts: 48 Location: Pune
|
|
|
|
Hi,
One of the reason for -904 is limit on the number of locks aquired.
you can bind the program with isolation option CS(cursor stability)
and execute the same. |
|
Back to top |
|
|
|