DBD::Oracle v1.54 is on its way to CPAN. In this iteration, no new feature, but a large amount of bug fixes.
It has come again. This magic time of the year when, in-between the hangovers of Christmas and the hangovers of the New Year bashes, one takes a longing look back at the ending year, and make mad plans, wistful wishes and grandiose resolutions for the new one. So, for a moment, let me indulge in this tradition and let my gaze wander at the distances that stretch forward and behind, while my mind drift back and forth betwixt what has been and what shall be. But gently. ‘Cause lemme tell you, that was damn good eggnog (so please be kind and don’t click so hard with the mouse, will you?).
What better way to start the year than to bring a fresh new breath to an old favorite? And thus, as you read this a new version of Git::CPAN::Patch should be making its way to CPAN. This new version is a massive refactoring of the module’s guts, which will affect both end-users and developers. For the best. Mostly. Or so I hope.
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.
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.
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:
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. (
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.
Recently a client of ours who used opsview to manage their resources needed to place some of their hosts into downtime in conjunction with some other cron-scheduled tasks. In order to implement that functionality, I created this simple script that should work with most installations of opsview, or with a few modifications, can be modified…
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.