ORA-01002: fetch out of sequence
- 1 Answers
- 3271 Views
- I also Faced
- E-Mail Answers
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 |
ORA-02428: could not add foreign key reference
ORA-12211: TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA
ORA-28520: error initializing heterogeneous data dictionary translations
QSM-02101: mv references a synonym in the FROM list
ORA-12198: TNS:could not find path to destination
ORA-00721: changes by release string cannot be used by release string
DRG-51019: unable to open or illegal format for fuzzy match data file: string
ORA-28557: unknown string for database link to non-Oracle system
ORA-13385: error in network manager: [string]
ORA-24332: invalid object type
ORA-14097: column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
ORA-01023: Cursor context not found (Invalid cursor number)
Oracle Errors 
