You are on page 1of 4

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 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 release. It is recommended that you downl oad the Opatch utility and the GI PSU 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/ chown -R grid:oinstall $ORACLE_HOME/OPatch $ORACLE_HOME/OPatch/opatch version The version output of the previous command should be 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/ 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.

it lists the Oracle components that are installed in t he home.0/infra/OPatch 1. The command will fail if the Oracle Inventory is not set up properly. 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. Apply the DB patch.0/infra OPatch Automation for a Software Only Oracle RAC Home Installation 1. As the database home owner execute: .sh -dbhome $ORACLE_HOME 2. one invocation of Opatch can patch the GI home.2. check the consistency of inventory informati on for GI home and each database home to be patched. As the database home owner (oracle) execute: /install/11gR2/psu/12311357/custom/server/12311357/custom/scripts/prepatch .rsp You should see at the end: patch /install/11gR2/psu/11724916 apply successful for home /u01/app/g rid/11.2. Run the following command patch GI home As root user execute: opatch auto /install/11gR2/psu -ocmrf /home/grid/ocm. If this ha ppens. Extract the Patch Set Update (PSU) cd /install/11gR2/psu unzip p12311357_112020_LINUX. contact Oracle Support Services for assistance. Add the directory containing the opatch to the $PATH environment variable.Validation of Oracle Inventory Before beginning patch application. Run the pre script for DB component of the patch. You can also roll back the p atch with the same selectivity. one or more Oracle RAC database OPatch Automation for GI Home Installation Depending on command line options specified. For e xample: export PATH=$PATH:/u01/app/grid/11.

1 Introduction to Oracle Database catbundle. As the database home owner execute: /install/11gR2/psu/12311357/custom/server/12311357/custom/scripts/postpatc h. re fer to Section 3.sql s cript as follows: cd $ORACLE_HOME/rdbms/admin sqlplus /nolog SQL> CONNECT / AS SYSDBA SQL> STARTUP SQL> @catbundle. "Known Issues" in the PSU Documentation. Connect as SYSDBA and run the catbundle. For information about the catbundle.sql execution is reflected in the dba_registry_history view by a row associated with bundle series PSU.0. 2. Run the post script for DB component of the patch.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>.sql. perform these steps on only one node.sql psu apply SQL> QUIT The catbundle. If there are errors. For each database instance running on the Oracle home being -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.log where TIMESTAMP is of the form YYYYMMMDD_HH_MM_SS. 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.2. 1. conne ct to the database using SQL*Plus.$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.2. . For a RAC environ ment. see My Oracle Support Note 605795. Data Warehouse. 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.sql script.

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