« Flexibility and Automation Don’t Go Hand in Hand | Main | Microsoft SQL Server Upgrade Woes: 2005 to 2008 »
Oracle Database Patching Just Got More Complicated
By Eric Gross | July 17, 2009
It seems like a regular occurrence that a new species gets introduced into the Oracle DBMS patch ecosystem. Most recently the Critical Patch Update (CPU) was created to simplify security patch distribution. These CPUs brought with them a new patch application methodology (NApply) which allows for multiple patches (now known as molecules) to be applied in one fell swoop. In addition to releasing a CPU this quarter Oracle has created a new patch called a Patch Set Update (PSU) which is a superset of the current CPU with additional non-security patches included as well. Currently there is a PSU exclusively for 10.2.0.4 but the next quarter will bring with it a PSU for 11.1.0.7 also, meaning the DBA should be familiar with this new format and anticipate its scheduled release along with the corresponding CPU bundle.
Additional planning is required given this new parallel set of patches will exist going forward. Successful preparation for application of the new bundles can only be made if one understands how the CPU and PSU differ fundamentally. With this knowledge in hand, it can be aligned with customer requirements to make the right decision for their business. One issue that forces planning is the challenge that comes up after applying a PSU to an installation when you decide that you would rather apply a CPU rather than a subsequent PSU, perhaps because of an application incompatibility with a fix in the PSU.
Even though all contents of a given CPU are applied when the parallel PSU is applied, the output of OPatch looks significantly different which may cause confusion. That being said, the traditional method of validation used when applying a Critical Patch Update isn’t sufficient. This is in part due to procedural differences both on the binary level and database level which which DBAs needs familiarize themselves.
One has to wonder how long the concept of CPU will survive given the challenges in maintaining two parallel patch releases in perpetuity with different application methodologies – CPUs use NApply while PSUs revert to the standard OPatch Apply method. In any event, the DBA must acknowledge that both of these will be available indefinitely, and in addition to understanding the needs of their given organization the technical complexity of a new procedure must be managed as well.
Topics: Database Automation, Patches, Upgrades
July 24th, 2009 at 4:38 pm
[...] Oracle Database Patching Just Got More Complicated [...]