On Friday 13 of June 2012, I was an on-call Oracle DBA. I got to work on a high priority client’s request. One of our client’s financial team was executing final steps of a year closing process in their ERP production environment and had a problem. The step that I received a complain about took 2 hours and still didn’t complete.
Some parts of the world are going through winter in swing while others are savoring summer (or suffering through it!). This variation in weather is beautifully in-sync with the variety of blog posts sprouting all over the web, especially regarding database technology. This mixed flavor of database blogs is captured once again by this Log Buffer Edition.
Since a third person just asked me how to prepare for OCM exam in last 2 days, I decided to make my answer publicly available. I will leave you to discover the formal path yourself and give you a guideline in terms of the how-to and length of the preparation.
This is not the first time I have run into this issue – in the past I (and who knows how many more Oracle DBAs) have had to deal with handling jobs from a different user, which usually ends in a big error. The answer to my prayers was the undocumented dbms_ijob package.
Database bloggers are blowing their trumpets at full throttle, warming up the hearts of readers across the globe with cool tips, nifty tricks, and glimmering gems. This Log Buffer Edition picks those gems and offers them to you.
After a little more than two weeks of soaking without any issues (yay!), version 1.45_00 of DBD::Oracle has been promoted to general use as v1.46.
And because some contributors have been very busy in the meantime, the next trial version, v1.47_00, is also already on its way to CPAN. This new version offers a few bug fixes (more details in the changelog excerpt below) as well as a rework of the platform-specific troubleshooting guides as POD documents. As usual, it’ll be left around for a minimum of two weeks before it gets promoted to v1.48. Happy upgrade!
Often, a hardware is updated at the same time as a database version. In such cases, we migrate a database from an original location to a new server upgrading the database version and sometimes changing operational system. If this is your situation, you can use the upgrade process to minimize the system’s downtime to 1 hour, independently from the size of the database you migrate.
Before I dig into the mechanics under the hood of the Hadoop beastie (which is the part, I assume, that is going to be heady as hell), I thought it would be a good idea to play a little bit with some of its applications to give me a feel for the lay of the land.
This blog post is a short summary of one of our migration strategies used to migrate Oracle 10g databases to ODA balancing the requirements of minimal downtime and efforts/costs of the project.
Backup is one of the most important topics for any Oracle DBA. It is our primary responsibility to make sure that at any point in time we can recover a database. Some time ago, I created a survey (my very first one): “Why do you use RMAN catalog DB for your Oracle DB backups?” In this blog post, I will share the survey’s results.