ORA-01002: fetch out of sequence
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.
Subscribe to:
Post Comments (Atom)
Troubleshooting ACFS-07981: Metadata Validation Errors
Troubleshooting ACFS-07981: Metadata Validation Errors Introduction The ACFS-07981 error indicates that an attempt to run an online file ...
-
Mastering ORA-00054: Resolving the "Resource Busy" Error The ORA-00054 error, often accompanied by the message "resource b...
-
Mastering ORA-03113: The "End-of-file on communication channel" Error The ORA-03113 error, "end-of-file on communication c...
-
Symptoms When running Create Accounting using SLA with the profile option FA: Use Workflow Account Generation set to Yes at the Site level,...
No comments:
Post a Comment