Wouldn’t “Automatic SQL Plan Management” be the 11g “killer app”? I’m just wondering… be careful it is part of Oracle Tuning Pack 11g! Before you answer this question, lets illustrate with an example how the “non-automatic”, “no tuning Pack” SQL Plan Management works.
About six weeks ago, I wrote, with my colleagues here at Pythian, an open letter to Larry Ellison, imploring him and Oracle to free API-level access to Automated Workload Repository (AWR) and Active Session History (ASH). This letter has received amazing support from the community, with 158 “signatories” at last count, and many other positive comments.
We received an informal but cordial response from Oracle two or three days after we couriered the letter to them, which said we could expect a formal reply soon.
“Real Time SQL Monitoring” is a 11g Tuning Pack new feature. You can easily access it when the Tuning Pack is set. Anyway, It’s very impressive even if it doesn’t look to be fully functional (Is it me ?). I guess Enterprise Manager provides a fantastic GUI for this feature. This post is for you if you don’t always use it…
I just read a fascinating article on clustering architectures for databases from Kevin Closson of Polyserve (now HP). All I can say is that he has one of the most informed and incisive views and insights on clustering, SMP, high-availability and high-performance environments in the industry. I thought I would share this with the broader community because I think a lot of MySQL, SQL Server and EnterpriseDB folks who need to read this and think about this subject might otherwise miss it, simply because they may not be regular readers of Kevin’s blog.
Hubert Depesz Lubaczewski has published the 57th edition of Log Buffer, the weekly review of database blogs, on .
I rushed into my favorite book, Oracle Database Licensing Information – 11g Release 1. Guess what? We now have 4 new opportunities to do business with Oracle. I still miss the price list. As if you could look at a new Release without the price ;)
It would not have been fair to show how Oracle 11g optimizer can now re-parse a query based on the execution statistics associated with a bind value compared to the previous executions of the same query with different bind values. It would not have been fair, to show you that without showing what happens when the second execution is faster that the first one, even with a sub optimal plan. This is what I’ll do now !
Basically, what is done in the example below it the opposite of what I’ve done in my previous post.
The example in this post is intended to be use as a demonstration of the new bind peeking algorithm of 11g. You’ll have to understand how it works before screaming! If it significantly enhances the behavior of the optimizer, I’ll show you in a next post it also has its own drawbacks, you’ll have to overcome…
To avoid being too far behind you guys that are already upgrading to 11g, I’ve decided to invest on 11g during the Beta Program. This has been a lot of fun and I wish I can share some of my findings with you. For example, did you know that 11g can go faster without any change at all ? The queries here will illustrate the change made to the Nested Loop Algorithm in 11g :
Thanks to Jeremy Schneider for quick info that Oracle 11g is available for download on OTN.