Pythian’s friendly Oracle e-Business Suite DBAs would like to congratulate all of our friends, clients, Pythian colleagues, prospects, new team members whom we haven’t yet met (join us!), all database geeks, and blog readers for successfully completing 2012! Have a very peaceful Christmas and the happiest year ever in 2013! May all of your pagers be quiet, and your year-end maintenance be incident-free! ;) Here comes our Christmas card to you :)
Screenings, shows, premieres and parties. Where the stars have been spotted this week? No not on the red carpet in LA, but in this Log Buffer Edition. In Log Buffer #299, stars of Oracle, SQL Server and MySQL are twinkling. Get mesmerized!!!
A client recently supplied a list of 50+ SQL IDs that should receive SQL profiles, and I’ve been working with Gwen Shapira to review the list. Further discussion showed that this list had come from the Automatic SQL Tuning feature, installed by default in Oracle 11g. The report includes a list of recommended SQL profiles ordered by “Maximum Benefit”, and in our case it included several hundred statements. The expected workflow, as far as I can gather, is to see the recommendations, look at the before- and after- execution plans, and accept the recommendations. Before blindly accepting recommendations, though, I like to see what exact changes are being proposed. They aren’t listed anywhere in the report, and require some extra work to uncover. The first step is to get the automatic SQL tuning advisor report. (
All the submissions from Pythian tree decorating teams are in! the team names are anonymous until the votes are in.
This is just a small bug fix release of the plugin. It was actually quietly released for a while now of if you have downloaded the plugin recently, you have the latest version. To be sure — check the version in the Console or you will see it in the file name.
Not many of you know that my day to day work focus is Oracle e-Business Suite :). Here goes EBS related blog post …Recently several of my team’s clients upgraded to R12.1.3 version and faced the same problem related to OACORE memory settings.
Just a short note documenting a procedure that isn’t done frequently, and I didn’t see described anywhere else. Somewhere last month a customer asked for my help in changing the SIDs on one of his RAC databases to match the new corporate standard. The database name matched the standard so we could leave that alone, but the SID needed to be changed. Here’s what we did to change it
It’s always sunny in the database arena, even if the data is engulfed in the clouds. Innovation rays keep databases illuminating and bloggers make hay in this sunshine and this Log Buffer Edition sift through all those blog post and brings you Log Buffer #298.
The environment was an Exadata environment undergoing pre-production stress testing. We used Real Application Testing to take a highly-concurrent OLTP workload, and replayed the workload with the synchronization parameter set to FALSE, effectively increasing concurrency beyond the original test system. AWR showed a large volume of buffer busy activity.
UKOUG roadmap to maintenance windows… please enjoy this copy of the recent presentation I gave at the UKOUG 2012 conference in Birmingham England. Feedback and comments always welcome.