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.
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.
SLOB on steroids v0.1: Use it at your own risk. First of all, let me state that I’m falling in love with SLOB :).
Interval partitioning – this 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 post will offer some insight on how Oracle Parallel Query works.
First of all, if you are using NFS to store Oracle database data files, I strongly advise you to enable Oracle Direct NFS (DNFS) to access these files. However, if you are not using NFS, DNFS is probably not of interest to you, and you should stop reading here. But, if you want to set it up, let’s go!
A while ago, I was paged by a client having backup job failure. Doing my routine as usual, I started the investigation by looking at the job execution log. Connected to the box was a strange output. Here it is!
Sharing knowledge not only is beneficial to others, but also enhances one’s own knowledge and broadens the spectrum. Blogging is all about sharing and this Log Buffer Edition brings together some great blog posts from around the database arena.
Recently, I was upgrading a database from 126.96.36.199 to the current 188.8.131.52 version. The database was using ASM, but I should notify at the beginning that the configuration is for a Stand-Alone Server and not RAC. Basically, the first things to be done for this procedure are part of the following checklist…
A new trial version of DBD::Oracle has been churned out. This release is mostly about Martin J. Evans going all ninjawesome on minor bug fixes as well as paving the way for an upcoming refactoring/speed boost of ora_verbose. As usual, the new version will be soaked for at least 2 weeks before it will turn into its fit-for-general-consumption v1.46 incarnation. Testers, please give this baby a whirl. The full changelog follows for the curious-minded.