This year’s last log buffer edition looks at the marvelous and splendid blog posts of Oracle, SQL Server and the MySQL databases which promise to bring more and more next year. This Log Buffer #301 promises to be the anchor for yet another action packed blogging carnival next year.
Shortly before we all went on break for the holiday, Oracle announced the new BDA X3-2. Now I have time to properly sit down with a glass of fine scotch and dig into the details of what is included in the release. Turns out that there are quite a few changes packed in. We are getting new hardware, new Hadoop, new Connectors and new NoSQL. Tons of awesome features are included. Let’s get into it.
In this post, I’ll demonstrate how to deploy the pre-built Oracle VM templates to create a two-node 11gR2 RAC cluster in Oracle VirtualBox.
If you are reading this, it means that world moves on and somebody somewhere was wrong in predicting the end of it. The ageless Log Buffer Edition presents you yet again some cool blog posts just before the holiday season to top up your excitement. This Log Buffer #300 is as sweet as the holidays and as sumptuous as Aussie BBQ. Enjoy
I was recently looking at an issue where a large database server was running out of temp space. The issue had happened in the past, so the goal was to identify what had been causing the system to run out of temp. Although ORA-1555 messages will appear in the database alert log (with query text) when a query runs out of temporary space, they only talk about the query that was “unlucky” enough to be attempting to get space when the tablespace was full, not who was using the temp space.
Prepare your database for the apocalypse with these 10 easy tips.
What happens when you update the crontab on a critical system to accommodate year-end processing? What happens when, despite all your diligence and devotion to human reliability guidelines, you perform a simple slip, and instead of typing crontab -e, you type crontab -r? Well, the documentation tells you what happens:
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. (