Database bloggers are blowing their trumpets at full throttle warming up the hearts of readers across the globe with cool tips, nifty tricks and gems. This Log Buffer Edition in Log Buffer #277 picks those gems and present to you.
After a little bit 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!
This process can be used for most 11G upgrade projects. Very often a hardware got updated at the same time as a database version. In such case we migrate a database from an original location to a new server upgrading database version and sometimes changing operational system. If this is your scenario then you can use the upgrade process to minimize system’s downtime to 1 hour independently from size of the database you migrate.
Before I would 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. Let’s have a look, shall we.
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 database. Some time ago I created a survey,”Why do you use RMAN catalog DB for your Oracle DB backups?” In this blog post I am sharing the survey’s results.
SLOB on steroids v0.1 (you use it on your own risk). If you don’t know what is SLOB read here.
Interval partitioning – the ability to create partitions on the fly was introduced in 11g. When the feature came out, there were several nasty bugs. One such particular “limitation” has to do with parallel group by on the partition key. If you want to see just that part, skip towards the end, but I think reading the whole blog will offer some insights in how Oracle Parallel Query works.
A couple of years back, I created WWW::Ohloh::API because it seemed to be a fun thing to do. And, trust me, it was. But now, since I’m not using that module personaly, I thought it would be a good idea to see if anyone would be willing to co-maintain it. Before I could do that, though, there was two little matters I had to deal with.
My impressions: being the first time that these kind of conferences were done in Argentina I have to say it was great, small but great. No many people knew about the event and even that the response was pretty good. It was a 3 day event with plenty of technical talks and some others talks coming from Companies who wanted to share experiences and impressions on what is coming for MySQL technologies.