ORA-01002: fetch out of sequence

I got ” ORA-01002: fetch out of sequence ” error in Oracle database.

 

ORA-01002: fetch out of sequence

 

Details of error are as follows.

 

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.
    

 

 

 fetch out of sequence

This ORA-01002 errors are related with the 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.

 

To solve this error, apply the following steps.

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.

 

To solve this error, Don’t use a FETCH on a SELECT FOR UPDATE after a COMMIT has been issued. Use cursor attributes to avoid these situations.

 

Do you want to learn Oracle Database for Beginners, then read the following articles.

Oracle Tutorial | Oracle Database Tutorials for Beginners ( Junior Oracle DBA )

 

 256 views last month,  2 views today

About Mehmet Salih Deveci

I am Founder of SysDBASoft IT and IT Tutorial and Certified Expert about Oracle & SQL Server database, Goldengate, Exadata Machine, Oracle Database Appliance administrator with 10+years experience.I have OCA, OCP, OCE RAC Expert Certificates I have worked 100+ Banking, Insurance, Finance, Telco and etc. clients as a Consultant, Insource or Outsource.I have done 200+ Operations in this clients such as Exadata Installation & PoC & Migration & Upgrade, Oracle & SQL Server Database Upgrade, Oracle RAC Installation, SQL Server AlwaysOn Installation, Database Migration, Disaster Recovery, Backup Restore, Performance Tuning, Periodic Healthchecks.I have done 2000+ Table replication with Goldengate or SQL Server Replication tool for DWH Databases in many clients.If you need Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS Consultancy and Training you can send my email adress [email protected].-                                                                                                                                                                                                                                                 -Oracle DBA, SQL Server DBA, APPS DBA,  Exadata, Goldengate, EBS ve linux Danışmanlık ve Eğitim için  [email protected] a mail atabilirsiniz.

Leave a Reply