Installation procedures for Grid Infrastructer Patch Set Update The Opatch utility has automated the patch

application for the Oracle Grid Infra structure (GI) home and the Oracle RAC database homes. It operates by querying e xisting configurations and automating the steps required for patching each Oracl e RAC database home of same version and the GI home. The utility must be executed by an operating system (OS) user with root privileg es (usually the user root), and it must be executed on each node in the cluster if the GI home or Oracle RAC database home is in Non-shared storage. OPatch Utility You must use the OPatch utility version 11.2.0.1.5 or later to apply this patch set update. Oracle recommends that you use the latest released OPatch for 11.2 r eleases, which is available for download from My Oracle Support patch 6880880 by selecting ARU link for the 11.2.0.0.0 release. It is recommended that you downl oad the Opatch utility and the GI PSU 11.2.0.2.2 patch in a shared location to b e able to access them from any node in the cluster for the patch application on each node. For each Oracle RAC database homes and the GI home that are being patched, run t he following commands as root to extract the OPatch utility. export ORACLE_HOME=/u01/app/grid/11.2.0/infra mv $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch.old unzip -d $ORACLE_HOME /install/11gR2/opatch/p6880880_112000_LINUX.zip chown -R grid:oinstall $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch/opatch version The version output of the previous command should be 11.2.0.1.5 or later. For each Oracle RAC database homes that are being patched, run the following com mands as root to extract the OPatch utility. export ORACLE_HOME=/u01/app/oracle/product/11.2.0/rac mv $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch.old unzip -d $ORACLE_HOME /install/11gR2/opatch/p6880880_112000_LINUX.zip chown -R oracle:oinstall $ORACLE_HOME/OPatch

The OPatch utility will prompt for your OCM (Oracle Configuration Manager) respo nse file when it is run. You should enter a complete path of OCM response file i f you already have created this in your environment. If you do not have the OCM response file (ocm.rsp) and you wish to use one durin g the patch application, then you should run the following command to create it. As the Grid home owner execute: $ORACLE_HOME/OPatch/ocm/bin/emocmrsp This will create the file ocm.rsp in the current directory, by default /home/gri d, this file will be use by opatch auto with the -ocmrf <OCM response file path> option to run opatch auto in silent mode.

Validation of Oracle Inventory Before beginning patch application, check the consistency of inventory informati on for GI home and each database home to be patched. Run the following command a s respective home owner to check the consistency. $ORACLE_HOME/OPatch/opatch lsinventory -detail -oh $ORACLE_HOME If this command succeeds, it lists the Oracle components that are installed in t he home. The command will fail if the Oracle Inventory is not set up properly. If this ha ppens, contact Oracle Support Services for assistance. Extract the Patch Set Update (PSU) cd /install/11gR2/psu unzip p12311357_112020_LINUX.zip

OPatch Automation for GI Home Installation Depending on command line options specified, one invocation of Opatch can patch the GI home, one or more Oracle RAC database homes. You can also roll back the p atch with the same selectivity. Add the directory containing the opatch to the $PATH environment variable. For e xample: export PATH=$PATH:/u01/app/grid/11.2.0/infra/OPatch 1. Run the following command patch GI home As root user execute: opatch auto /install/11gR2/psu -ocmrf /home/grid/ocm.rsp You should see at the end: patch /install/11gR2/psu/11724916 apply successful for home /u01/app/g rid/11.2.0/infra OPatch Automation for a Software Only Oracle RAC Home Installation 1. Run the pre script for DB component of the patch. As the database home owner (oracle) execute: /install/11gR2/psu/12311357/custom/server/12311357/custom/scripts/prepatch .sh -dbhome $ORACLE_HOME 2. Apply the DB patch. As the database home owner execute:

$ORACLE_HOME/OPatch/opatch napply -oh $ORACLE_HOME -local /install/11gR2/p su/12311357/custom/server/12311357 $ORACLE_HOME/OPatch/opatch napply -oh $ORACLE_HOME -local /install/11gR2/p su/11724916 3. Run the post script for DB component of the patch. As the database home owner execute: /install/11gR2/psu/12311357/custom/server/12311357/custom/scripts/postpatc h.sh -dbhome $ORACLE_HOME

Patch Post-Installation Instructions Loading Modified SQL Files into the Database These instructions are for a database that is created or upgraded after the inst allation of PSU 11.2.0.2.2. for any new database only if it was created by any o f the following methods: * Using DBCA (Database Configuration Assistant) to select a sample database (General, Data Warehouse, Transaction Processing) * Using a script that was created by DBCA that creates a database from a sam ple database The following steps load modified SQL files into the database. For a RAC environ ment, perform these steps on only one node. 1. For each database instance running on the Oracle home being patched, conne ct to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql s cript as follows: cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catbundle.sql psu apply SQL> QUIT The catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series PSU. For information about the catbundle.sql script, see My Oracle Support Note 605795.1 Introduction to Oracle Database catbundle.sql. 2. Check the following log files in $ORACLE_BASE/cfgtoollogs/catbundle for an y errors: catbundle_PSU_<database SID>_APPLY_<TIMESTAMP>.log catbundle_PSU_<database SID>_GENERATE_<TIMESTAMP>.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. If there are errors, re fer to Section 3, "Known Issues" in the PSU Documentation.

Create an NFS Share to repeat the previous steps to all remaining nodes