Home » SQL & PL/SQL » SQL & PL/SQL » PL/SQL Cursor Fetch error
PL/SQL Cursor Fetch error [message #187745] |
Tue, 15 August 2006 06:36  |
miltony
Messages: 5 Registered: March 2006
|
Junior Member |
|
|
I am using cursor with host arrays. I will repeatedly fetch rows 3 at a time. After fetching 300 rows, I am getting error with code 01002. Can anyone help me in solving this problem.
I also want to know, what is the maximum amount of data that we can fetch for a cursor.
Thanks in advance,
Milton Y.
[Updated on: Tue, 15 August 2006 06:42] Report message to a moderator
|
|
|
|
|
Re: PL/SQL Cursor Fetch error [message #187751 is a reply to message #187748] |
Tue, 15 August 2006 06:56   |
JRowbottom
Messages: 5933 Registered: June 2006 Location: Sunny North Yorkshire, ho...
|
Senior Member |
|
|
How many rows are there that can be returned in your query?
My guess would be that you are hitting cause 1) in the docs - you do a fecth, get the last row, and then try to fetch again.
Without seeing the code, and generally having more info, it's hard to be more specific.
|
|
|
|
Re: PL/SQL Cursor Fetch error [message #187760 is a reply to message #187751] |
Tue, 15 August 2006 07:26   |
miltony
Messages: 5 Registered: March 2006
|
Junior Member |
|
|
There are 350 rows to be returned by the query.
I had loaded 290 rows from 350 into another database. It worked fine with the cursor. When I loaded another 10 rows from the remaining 60, it is giving error.
The code is such that a fetch into 174 columns with total record length 1060.
|
|
|
Re: PL/SQL Cursor Fetch error [message #187764 is a reply to message #187760] |
Tue, 15 August 2006 08:24  |
JRowbottom
Messages: 5933 Registered: June 2006 Location: Sunny North Yorkshire, ho...
|
Senior Member |
|
|
Quote: | Without seeing the code, and generally having more info, it's hard to be more specific.
|
I can think of half a dozen things off the top of my head that you could have done.
Rather than go through them all one at a time, why don't you show us the code.
Even better, see if you can create a small test case that reproduces the problem. The odds are better than 50/50 that you'll discover the cause of the problem when you try to do that.
|
|
|
Goto Forum:
Current Time: Thu May 15 12:49:43 CDT 2025
|