Oracle Patch – Bugs We’ve Seen

Posted in: Technical Track

When I read Note: 391116.1 with the full list, I noticed the following bugs that we’ve encountered are fixed.

Unfortunately, an important bug in posted on the Sept. 29 is not listed as fixed in this patch list. The bug has to do with both data corruption, and security vulnerabilities when running queries that can be interpreted in multiple ways by the SQL parser — depending on what schema has namespace precedence for your signon. In this regard, I would recommend anyone who is running, for example, a test or development copy of their production schemas on the same database, to read the following metalink note without delay.

Note: 392673.1 Bug 5458753 “SQL can execute in wrong schema”.

Want to talk with an expert? Schedule a call with our team to get the conversation started.

About the Author

An Oracle ACE with a deep understanding of databases, application memory, and input/output interactions, Christo is an expert at optimizing the performance of the most complex infrastructures. Methodical and efficiency-oriented, he equates the role of an ATCG Principal Consultant in many ways to that of a data analyst: both require a rigorous sifting-through of information to identify solutions to often large and complex problems. A dynamic speaker, Christo has delivered presentations at the IOUG, the UKOUG, the Rocky Mountain Oracle Users Group, Oracle Open World, and other industry conferences.

2 Comments. Leave new

well, look again. It’s on the list

Christo Kutrovsky
October 18, 2006 12:54 pm

The note sais
“Last Revision Date: 11-OCT-2006 ”

Seems like they added it after I wrote the article :)

I guess that’s why the list is not official yet.

Thanks for the note !


Leave a Reply

Your email address will not be published. Required fields are marked *