Hello Gents

I have a application that work from 3 years and now on a prticular
action show this error :

java.sql.SQLException: Exhausted Resultset

The application scan a table with ~8000000 rows

Can this error depend from a bad status of the table ?

I check on the alert log of oracle and not found any message

Do someone have an idea ?

Thanks for the support

Regards LAGO

On Wed, 25 May 2005 18:47:46 GMT, Alessandro Lagostena
<alessandro.lagostena (AT) tin (DOT) it> wrote:

No, in that case an ORA- error message would have been thrown

Of course not, because nothing is wrong with the database. The problem
is with 'scanning' 8 million records
Yes. Why is it that Java programmers live in the misconception they
never ever make a mistake, that Java isn't memory hungry, and their
programs never run out of memory?
Why is it they invariably blame the database for their mistakes?
Because they don't know anything about the database and treat it as a
flat file system?
Nagging questions with obvious answers.


--
Sybrand Bakker, Senior Oracle DBA

Sybrand Bakker wrote:
I agree. There is nothing wrong with the database and scanning 8
million records maybe bad design... but the "Exhausted Resultset" error
message in this instance is most likely not attributed to just scanning
n number of records.

This particular error message is thrown if you try to fetch from a
resultset that did not return any rows. OP did not post the culprit
code... so just going by the "Exhausted Resultset" error message, I
don't think there are any memory issues here. Just bad programming
perhaps... and the reason for that is that a resultset may or may not
return any rows, a good programmer *will* check the resultset by using
next() method *prior* to fetching from it e.g.

ResultSet rset = ....;
while (rset.next()) {
// You ONLY get here if there are any rows
}

Regards
/Rauf

Alessandro Lagostena (alessandro.lagostena (AT) tin (DOT) it) wrote:
: Hello Gents

: I have a application that work from 3 years and now on a prticular
: action show this error :

: java.sql.SQLException: Exhausted Resultset

: The application scan a table with ~8000000 rows



I think after scanning 8000000 rows for 3 years you'd be pretty exhausted
too.

As mentioned by another poster, the code needs to be retired, and replaced
with something new.


--

This space not for rent.