Applies to:
Oracle Server – Enterprise Edition – Version: 10.2.0.1 to 11.1.0.7
Information in this document applies to any platform.
Goal
This article helps to plan oracle database patching sequence to the latest/required patchset version with in the same release (ex: 10.2.0.1 to 10.2.0.4) along with CPU/PSU/One-off-patch installations.
Solution
Basically there are two entities in Oracle Database environment
– Oracle Database Software
– Oracle Database
Most of the database patching activities involve, following sequence
– Update “Oracle Database Software” using ‘./runInstaller’ or ‘opatch apply’
… known as “Installation” Tasks.
– Update “Oracle Database” (catupgrd.sql or catbundle.sql …etc) to make it compatible for newly patched “Oracle database Software”
… known as “Post Installation” tasks.
Patchset OR CPU/PSU (or one-off) patch contains Post Installation tasks to be executed on all Oracle Database instances after completing the Installation tasks. If you are planning to apply a patchset along with required one-off-patches (either CPU or PSU or any other one-off patch), then you can complete the Installation tasks of Patchset+CPU/PSU/one-off patches at once and then execute Post Installation tasks of Patchset+CPU/PSU/one-off patches in the same sequence as they were installed. This approach minimizes the requirement of database shutdown across each patching activity and simplifies the patching mechanism as two tasks: Software update and then Database update.
For example, on currently running 10.2.0.1 Oracle Database environment, if you are planning to install 10.2.0.4 Patchset + Latest CPU / PSU patch , then following are the steps
1. Shutdown/stop all database instances/services that are running from the (10.2.0.1) OracleHome being patched.
2. Take complete cold backup of the following
– Oracle Home
– Central Inventory
(directory pointed by inventory_loc in /var/opt/oracle/oraInst.loc OR /etc/oraInst.loc)
These two directories are very much required (for restore operations) if you want to remove the patchset (after installation) due to some reason. Refer section “Removing the patchset software” in patchset README.
3. Download and Install 10.2.0.4 (or latest) patchset.
Refer Download Instructions Note (to avoid file corruption issues during download) provided at end of this article and ensure that file is downloaded/transferred/unzipped properly on Oracle Server.
Refer README and complete the “Pre-installation and Installation” tasks.
But do not start/execute Post-Installation tasks in this step.
4. Download and install latest opatch utility from metalink “Patch 6880880”
Refer Download Instructions Note (to avoid file corruption issues during download) provided at end of this article and ensure that file is downloaded/transferred/unzipped properly on Oracle Server.
Be sure to obtain the correct OPatch for your platform and Oracle version
Oracle 9.2 and 10.1 – OPatch 101000
Oracle 10.2 – OPatch 102000
Oracle 11.1 – OPatch 111000
Oracle 11.2 – OPatch 112000
Refer README file for version of the opatch utility shipped in this patch and then use following steps to install latest opatch utility. Example, if downloaded file is p6880880_102000_SOLARIS64.zip
% cp p6880880_102000_SOLARIS64.zip $ORACLE_HOME
% cd $ORACLE_HOME
% mv ./OPatch ./OPatch_OLD
% unzip p6880880_102000_SOLARIS64.zip
% $ORACLE_HOME/OPatch/opatch version
5. Download and install Latest CPU (Critical Patch Update) OR PSU (Patchset Update).
Latest PSU (Patchset Update) already includes latest CPU patch released.
Note 854428.1: Introduction to Database Patch Set Updates
If PSU is not released/planned for your platform/oracle-version, then you can download and install latest/available CPU patch for your oracle version.
Refer Download Instructions Note (to avoid file corruption issues during download) provided at end of this article and ensure that file is downloaded/transferred/unzipped properly on Oracle Server.
Refer README and complete “Pre-installation and Installation” instructions.
But do not start/execute Post-installation tasks.
6. Download and install any other recommended/mandatory/required patches for your environment.
Refer Download Instructions Note (to avoid file corruption issues during download) provided at end of this article and ensure that file is downloaded/transferred/unzipped properly on Oracle Server.
Refer “Known issues and alerts” article released for the patchset version you have installed at step 3.
Note 161818.1 Oracle Server (RDBMS) Releases Support Status Summary
“Known issues and alerts” article for 11.1.0.x can be identified from following article
Note 454507.1 ALERT: Oracle 11g Release 1 (11.1) Support Status and Alerts
“Known issues and alerts” article for 10.2.0.x can be identified from following article
Note 316900.1 ALERT: Oracle 10g Release 2 (10.2) Support Status and Alerts
“Known issues and alerts” article for 10.1.0.x can be identified from following article
Note 263719.1 ALERT: Oracle 10g Release 1 (10.1) Support Status and Alerts
Example:
If your plan is to apply patchset version 10.2.0.4 (in step-3), then following is the article for “Known issues and alerts of 10.2.0.4” found from “Note 316900.1”
Note 555579.1 10.2.0.4 Patch Set – Availability and Known Issues
7. Now execute “Post Installation” tasks of patchset/patches on “Oracle Database” instance running from the OracleHome (just been patched), in the same order as they installed.
– Refer Patchset (Ex: 10.2.0.4) README and complete the Post Installation tasks (ex: catupgrd.sql).
– Refer CPU or PSU patch README and complete the Post-installation tasks (ex: catbundle.sql and view_recompile).
– Refer README of any other patch(es) installed at step-6 and complete the Post Installation tasks (if present).
8. If there are more than one “Oracle Database” instance running from the Oracle Home, then repeat the step-7 for all database instances one after the other.
9. Now your database patching activity is completed.
Download Instructions Note:
Please consider following points to avoid common issues (that may cause zip file corruption) during download from metalink / oracle technology network.
– If not downloading the patchset/patch directly to the oracle server, then transfer downloaded zip file to the Oracle server in BINARY format.
– Verify the checksum of the downloaded zip file on the Oracle server against the value on the patch download page (“View Digest” button).
– Unzip the downloaded zip file ONLY on the Oracle server.