Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


advertisement
 

The ORA-01555 Error: A PL/SQL Developer Solution

How to avoid the ORA-01555 error programmatically—that is, from the PL/SQL developer's perspective.


advertisement
he "ORA-01555 snapshot too old" error, which causes user transactions to fail, is a nightmare for Oracle DBAs and developers. It usually occurs after queries or batch processes have been running for a long time, which means that it can cause you to lose many hours of processing.

In my previous 10-Minute Solution on this subject, "The ORA-01555 Error: A DBA Solution," I explained the causes of this error and described two examples of how to avoid it from the DBA's perspective.

In this 10-Minute Solution, I show you a third example: how to avoid the ORA-01555 error programmatically—that is, from the PL/SQL developer's perspective.



How do you avoid the ORA-01555 error, which is hard to recreate and crops up inconsistently?



From the developer's perspective, you can restructure your PL/SQL code to avoid fetching across commits that cause the ORA-01555 error.



Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date