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!
_________________________
L&K
CT