I want to show you a small example how to apply the January CPU Patch on a 184.108.40.206 Database. Please keep in mind that this is only a sample. Refer to the Patch Readme and Oracle Documentation before you apply this Patch on one of your Systems. A special note here. Even Oracle points in MOS Note 1611875.1 that there will no be CPU Patch for Oracle GI. The Patch Readme says at point 3.1.1 that this Patch will also be applied on the GI Home. Refer to the Patch Readme for more Information.
Before you begin check the OPatch version you use. You will need 220.127.116.11.5 or later to install this CPU Patch. Check MOS Note 274526.1 How To Download And Install The Latest OPatch Version for more Information or directly go to URL https://updates.oracle.com/download/6880880.html . To check the OPatch Version you can use this command.
[oracle@server1 db_ee_2]$ $ORACLE_HOME/OPatch/opatch version OPatch Version: 18.104.22.168.6 OPatch succeeded.
Check for existings Patch conflicts
cd /u01/patch/17478514/ $ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./ Oracle Interim Patch Installer version 22.214.171.124.6 Copyright (c) 2013, Oracle Corporation. All rights reserved. PREREQ session Oracle Home : /u01/app/oracle/product/11.2.0/db_ee_2 Central Inventory : /u01/app/oraInventory from : /u01/app/oracle/product/11.2.0/db_ee_2/oraInst.loc OPatch version : 126.96.36.199.6 OUI version : 188.8.131.52.0 Log file location : /u01/app/oracle/product/11.2.0/db_ee_2/cfgtoollogs/opatch/opatch2014-01-16_23-02-30PM_1.log Invoking prereq "checkconflictagainstohwithdetail" Prereq "checkConflictAgainstOHWithDetail" passed. OPatch succeeded.
Patch the Oracle Database
[oracle@server1 17478514]$ $ORACLE_HOME/OPatch/opatch apply Oracle Interim Patch Installer version 184.108.40.206.6 Copyright (c) 2013, Oracle Corporation. All rights reserved. Oracle Home : /u01/app/oracle/product/11.2.0/db_ee_2 Central Inventory : /u01/app/oraInventory from : /u01/app/oracle/product/11.2.0/db_ee_2/oraInst.loc OPatch version : 220.127.116.11.6 OUI version : 18.104.22.168.0 Log file location : /u01/app/oracle/product/11.2.0/db_ee_2/cfgtoollogs/opatch/17478514_Jan_16_2014_23_03_33/apply2014-01-16_23-03-33PM_1.log Applying interim patch '17478514' to OH '/u01/app/oracle/product/11.2.0/db_ee_2' Verifying environment and performing prerequisite checks... All checks passed. Provide your email address to be informed of security issues, install and initiate Oracle Configuration Manager. Easier for you if you use your My Oracle Support Email address/User Name. Visit http://www.oracle.com/support/policies.html for details. Email address/User Name: You have not provided an email address for notification of security issues. Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y This node is part of an Oracle Real Application Cluster. Remote nodes: 'server2' Local node: 'server1' Please shutdown Oracle instances running out of this ORACLE_HOME on the local system. (Oracle Home = '/u01/app/oracle/product/11.2.0/db_ee_2') Is the local system ready for patching? [y|n] y User Responded with: Y Backing up files... Patching component oracle.rdbms, 22.214.171.124.0... Patching component oracle.rdbms.rsf, 126.96.36.199.0... Patching component oracle.sdo, 188.8.131.52.0... Patching component oracle.sysman.agent, 10.2.0.4.5... Patching component oracle.xdk, 184.108.40.206.0... Patching component oracle.rdbms.dbscripts, 220.127.116.11.0... Patching component oracle.sdo.locator, 18.104.22.168.0... Patching component oracle.nlsrtl.rsf, 22.214.171.124.0... Patching component oracle.xdk.rsf, 126.96.36.199.0... Patching component oracle.rdbms.rman, 188.8.131.52.0... OPatch found the word "warning" in the stderr of the make command. Please look at this stderr. You can re-run this make command. Stderr output: ins_emagent.mk:113: warning: overriding commands for target `nmosudo' ins_emagent.mk:52: warning: ignoring old commands for target `nmosudo' /u01/app/oracle/product/11.2.0/db_ee_2/sysman/lib/ins_emagent.mk:113: warning: overriding commands for target `nmosudo' /u01/app/oracle/product/11.2.0/db_ee_2/sysman/lib/ins_emagent.mk:52: warning: ignoring old commands for target `nmosudo' Verifying the update... The local system has been patched. You can restart Oracle instances on it. (...)
If you have applied the CPU Patch on you Database Homes you will need to load the SQL Files into your Database, to do this start your Oracle Database and change your directory to $ORACLE_HOME/rdbms/admin
oracle@server1 admin]$ sqlplus / as sysdba SQL*Plus: Release 184.108.40.206.0 Production on Thu Jan 16 23:14:57 2014 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 220.127.116.11.0 - 64bit Production With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP, Data Mining and Real Application Testing options SQL> @catbundle.sql psu apply
If you have succesfully updated your database, one of the last step is to upgrade the RMAN Recovery Catalog (if you have one in use).
Sample: RMAN> UPGRADE CATALOG;
Hope that this helps and give you a overview of the Patching process.