Has anyone seen this error message before. We are running enhanced retropay and getting the error message

APP-PAY-06881: Error ORA-01002: fetch out of sequence
has occurred in table pay_assignment_actions at location 4024

Can't seem to narrow it down to whether its a data issue or not.

Any advice greatfully received.

Delboy

I am inclined to think it a coding issue...

Will probably have been caused by one of:

1 Data is being retrieved/changed via a cursor which uses FOR UPDATE and there is a commit inside the FETCH loop, ie before the last row has been retrieved

2. A cursor attempts to fetch after the last row has been found (ie after the 1403 sqlerror)

3. If something alters one or more of the bind variables that a cursor might be using, and thereafter attempting to fetch instead of re-executing the query.

Apart from that, dunno mate!

Thanks CT,

I will pass your thoughts on to someone who knows what the hell that all means

Regards,

A mere confused funkie

I've seen this issue related to rollback segments too. Occasionally alongside the "Snapshot too old" error.

As you are running a standard process i would be inclined to search on Metalink Oracle's new fancy support site (if its working today) for any hits.

Not related to RUP4 by any chance??

It's not a RUP4 issue. We are live on RUP4 and have already run a retropay process on it. The only hit we got was the one CT suggested re: the commit statement in a sql function being called by a fast formula.

Delboy