ORA-01002: fetch out of sequence
Answer / guest
Cause: This error means that a fetch has been attempted from
a cursor which is no longer valid. Note that a PL/SQL cursor
loop implicitly does fetches, and thus may also cause this
error. There are a number of possible causes for this error,
including: 1) Fetching from a cursor after the last row has
been retrieved and the ORA-1403 error returned. 2) If the
cursor has been opened with the FOR UPDATE clause, fetching
after a COMMIT has been issued will return the error. 3)
Rebinding any placeholders in the SQL statement, then
issuing a fetch before reexecuting the statement.
Action: 1) Do not issue a fetch statement after the last row
has been retrieved - there are no more rows to fetch. 2) Do
not issue a COMMIT inside a fetch loop for a cursor that has
been opened FOR UPDATE. 3) Reexecute the statement after
rebinding, then attempt to fetch again.
Please add more information about this Error
| Is This Answer Correct ? | 0 Yes | 0 No |
PCC-02335: body of cursor must name statement identifier
ORA-24000: invalid value string, string should be of the form [SCHEMA.]NAME
RMAN-06053: unable to perform media recovery because of missing log
TNS-00012: INTCTL: error while processing Connection Manager request
ORA-31010: XML element index string exceeds maximum insertion index string
PCC-02364: Host struct and its indicator must have the same number of fields
DRG-50909: maximum number of documents string is not an integer
TNS-12607: TNS: Connect timeout occurred
NCR-03021: NCRO: Reset the in-band line
KUP-02006: script line too long
ORA-12704: character set mismatch
KUP-04079: error fetching list of valid directories