Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles
New Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 

 
 

ORA-01002: fetch out of sequence tips

Oracle Error Tips by Donald Burleson

 

The Oracle oerr utility  notes this on the ora-01002 error:

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 re-executing 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) Re-execute the statement after rebinding, then attempt to fetch again.

ORA-01002 can have multiple causes including:

  • A PL/SQL loop does fetches without notice
  • Attempting to fetch from a cursor that is no longer valid (fetching from a row which has been retrieved).
  • Fetching after a COMMIT has already been issued and a cursor is opened with the FOR UPDATE clause.
  • Issuing a fetch before re-executing a SQL after rebinding placeholders.

You may want to try using cursor attributes to dodge ORA-01002 in the future. To resolve a current ORA-01002, there are three actions you can perform:

  1. After the last record is received, do not issue a fetch
  2. Inside a fetch loop on a SELECT FOR UPDATE, do not use a COMMIT
  3. Try fetching again after re-executing the statement (after rebinding)

 

 

��  
 
 
Oracle Training at Sea
 
 
 
 
oracle dba poster
 

 
Follow us on Twitter 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  

and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright © 1996 -  2017

All rights reserved by Burleson

Oracle ® is the registered trademark of Oracle Corporation.

Remote Emergency Support provided by Conversational