Tag Archives: upgrades

Which would your CEO prefer

Would your CEO choose to give up a negligible amount of system performance at peak system load in exchange for a reduction of risk during system upgrades and an alternative to hours of downtime?

I suspect the answer is yes.

What’s the cost of such a technology? Believe it or not, it’s free. It’s the snapshot functionality that’s built into VMware’s vSphere Hypervisor (based on ESXi) that you can leverage once you virtualize your Oracle database or any other x86 systems. Is the performance impact truly negligible? Don’t take it from me; you can read it in Oracle’s own words.

Recently RedHat and Oracle have come out with updates to their mainstream distributions (RedHat Enterprise Linux 5.6 and Oracle Linux 5.6) and each has come out with an entirely new version (RedHat Enterprise Linux 6 and Oracle Linux 6). System and database administrators all around the world are updating their critical systems. Applying those updates to critical systems requires testing and downtime.

The best practice for operating system upgrades is to test the upgrade on the same exact hardware, software and data as in production. But are your test and production systems identical? Same motherboard? Same processors? Same amount and brand of RAM and same exact operating system packages installed? Pretty unlikely. With virtualization, all those configurations are identical.

With VMware virtualization, I can take take a clone of the entire production server while it’s live and being used by users. Now I have a truly identical copy of production to test my upgrade. Note that to do a clone of the entire production server while it’s live requires VMware vCenter which isn’t free, but vSphere Essentials (which includes vCenter) starts at $1000 as of the time of this writing.

With snapshots (which are free and don’t require vCenter), you take a snapshot (3 mouse clicks and less than 10 seconds) of the virtual machine and then do the upgrade. If you run into issues, just revert / rollback the snapshot to the state it was in when you took the snapshot. The time to do that revert / rollback is only the time necessary to reboot your virtual machine – 5 minutes? If the upgrade and testing goes smoothly, you just merge the snapshot into the virtual machine while the system is up and available to users. Total time spent doing non-upgrade activities such as backups or restores? Essentially zero.

Compare this to how you would handle a critical system without virtualization: you’d take the system offline for the upgrade, take a full backup of the system, do the upgrade (hoping it works just like it did in the similar but most likely not identical test system), have the users test, and, if there’s an issue, possibly spend hours restoring from backup. You do trust your backups… right?

Enterprise DBAs and the companies that employ them tend to be risk adverse when it comes to losing data or experiencing downtime. Virtualizing the hardware allows you to ensure your test and development systems are the exact same systems as production, thereby reducing risk of unforeseen issues during the upgrade. Utilizing snapshots allows you to very quickly take a save point of your entire server and rollback to it very quickly in the event of unforeseen issue, almost entirely eliminating (minutes vs. hours) the downtime associated with recovering from an unforeseen issue.


If you’ve been an Oracle DBA for any length of time, you’ve heard the term upgradation.  But what is an upgradation?

Is it an upgrade?  Is it a migration?  What the heck’s the difference between an upgrade and a migration?

If you’re switching operating system platforms (Windows to Linux for example), you’re migrating

If you’re switching database vendors (MS SQL Server to Oracle for example), you’re migrating

If you’re moving from Oracle 9i to Oracle 10g, you’re upgrading

If you’re moving from Oracle 11gR1 to Oracle 11gR2, you’re upgrading

If you’re moving from Oracle 11gR1 on Windows to Oracle 11gR2 on Linux, you’re performing both an upgrade and a migration.

So what is an upgradation?  Well damn if that isn’t a good question, because UPGRADATION ISN’T A WORD OR A REAL TECHNICAL TERM. In my experience, it tends to be used by people very new to the Oracle eco-system and by people who don’t have English (or American) as their primary language.

I’ve been at multiple clients where if upgradation is listed on a resume, the resume is no longer considered.  Unless a prospective candidate is otherwise amazing, I’m typically the same way.  It’s the same thing as having a misspelling on your resume.

So, make sure you don’t use upgradation on a resume and learn the difference between a migration and an upgrade.