12/20/2013

Document 1064804.1

Apply Grid Infrastructure/CRS Patch in Mixed Version RAC Database Environment (Doc ID
1064804.1)
Modified: 07-Aug-2013

Type: HOWTO

In this Document
Goal
Solution
References

APPLIES TO:
Oracle Database - Enterprise Edition - Version 9.2.0.1 to 11.2.0.4 [Release 9.2 to 11.2]
Information in this document applies to any platform.

GOAL
This document provides manual steps to apply GI/CRS patch in mixed Oracle Clusterware (GI or CRS) and RAC
environment.
Refer to note 1474914.1 to find out which patch needs to be applied to which home.

SOLUTION
In this document, we'll provide two examples of of applying patch in mixed Grid Infrastructure and RAC environment.
Case 1: Apply GI/CRS patch to pre-11.2 DB home in mixed environment (11gR2 GI + pre-11.2 DB):
Example given below is to apply 11.1.0.7 CRS PSU2 to 11.1.0.7 DB home. To apply patch 9207257 to 11.1.0.7
database home, you will need to execute steps that only applies to database home:
# 1. Verify that the Oracle Inventory is properly configured.
#
# % opatch lsinventory -detail -oh <RDBMS_HOME>
#
###########################################################################
#
# 2. Unzip the PSE container file
#
# Refer to patch readme
#
###########################################################################
#
# 3.1 In configuration A, shut down all resources thats running off database home on
#
all nodes. Note that these steps must be run in the order specified.
#
#
3.1.1 To shutdown RDBMS on all nodes, run the following command:
#
#
% $ORACLE_HOME/bin/srvctl stop database -d dbname
#
#
3.1.2 To shutdown ASM instances on all nodes, run the following command
#
Execute only if ASM is running off database home - unusually in Grid Infrastructure.
#
#
% $ORACLE_HOME/bin/srvctl stop asm -n <node_name>
#
#
3.1.3 To shutdown listeners run the following command on each node:
#
Execute only if listener is running off database home - unusually in Grid Infrastructure.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=q1iylk9uz_172&id=1064804.1

1/4

12/20/2013

Document 1064804.1

#
Execute only if listener is running off database home - unusually in Grid Infrastructure.
#
#
% $ORACLE_HOME/bin/srvctl stop listener -l <listener_name> -n <node_name>
#
# 3.2 In configuration B, shut down all resources thats running off database home on local node
#
#
3.2.1 To shutdown RDBMS instance on the local node run the following command:
#
#
% $ORACLE_HOME/bin/srvctl stop instance -d dbname -i instance_name
#
#
Then run commands (3.1.2) through (3.1.3) mentioned above.
#
###########################################################################
#
# 4. Prior to applying this part of the fix, you must invoke this script as root to unlock protected files.
#
# Skip this step
#
###########################################################################
#
# 5. Invoke prepatch.sh:
#
# As the RDBMS software owner;
# % custom/server/9207257/custom/scripts/prepatch.sh -dbhome <RDBMS_HOME>
#
# Note: In configuration A, invoke this only on one node.
###########################################################################
#
# 6. Patch the Files
#
# 6.2 Patch the RDBMS home files.
#
# As the RDBMS software owner, from the directory where the patch was unzipped;
#
# % opatch napply custom/server/ -local -oh <RDBMS_HOME> -id 9207257
#
# Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
# 7. Configure the HOME
#
# 7.2 Configure the RDBMS HOME
#
# As the RDBMS software owner execute the following;
#
# % custom/server/9207257/custom/scripts/postpatch.sh -dbhome <RDBMS_HOME>
#
# Note: In configuration A, invoke this only on one node.
#
###########################################################################
#
# 8. Now security settings need to be restored on the CRS Home. This script
# will also restart the CRS daemons. Invoke this script as root.
#
# Skip this step
#
###########################################################################
#
# 9. On success you can determine whether the patch has been installed by
# using the following command;
#
# % opatch lsinventory -detail -oh <RDBMS_HOME>
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=q1iylk9uz_172&id=1064804.1

2/4

12/20/2013

Document 1064804.1

# % opatch lsinventory -detail -oh <RDBMS_HOME>

#
###########################################################################
#
# Additional Special Notes:
# ------------------------# If there are multiple Server Homes in your configuration, then
# in step 7b, apply the patch to each home before continuing.
#
# If you later install an additional Server home, or if you skip a
# server home, then applying the patch to additional homes is easier.
# 1. Shut down all instances using that Server home
# 2. Invoke opatch as described in step 7b.
# 3. Restart the instances in that Server home
# This can be done while CRS is active.
#
#
###########################################################################
#
# Patch Deinstallation Instructions:
# ---------------------------------# To roll back the patch, follow all of the above steps 1-5. In step 6,
# invoke the following opatch commands to roll back the patch in all homes.
#
# % opatch rollback -id 9207257 -local -oh <CRS_HOME>
#
# % opatch rollback -id 9207257 -local -oh <RDBMS_HOME>
#
# Afterwards, continue with steps 7-9 to complete the procedure.
#
###########################################################################
Case 2: Apply GI patch to 11gR2 GI home in mixed environment (11gR2 GI + pre-11.2 DB):
Following steps need to be skipped for all pre-11.2 database homes as 11gR2 GI patch doesn't apply to them;
example given below is from 11.2.0.1.1 GI PSU1.
2.2.4 Save the database home configuration settings
Run the following command as the Oracle RAC database software owner
%cd <UNZIPPED_PATCH_LOCATION>
%9778840/custom/server/9778840/custom/scripts/prepatch.sh -dbhome <ORACLE_HOME>
2.2.6 Apply GI PSU patch
2.2.6.2 Rollback conflicting one-off database patches
To rollback one-off patch:
% cd <ORACLE_HOME>
% opatch -rollback -local -oh <$ORACLE_HOME> -id <ONE_OFF_PATCH bug number>
2.2.6.3 Patch the database home files
As the database home software owner, from the directory where the patch was unzipped; Run the following
command:
%cd <UNZIPPED_PATCH_LOCATION>
% opatch napply 9778840/custom/server/ -local -oh <ORACLE_HOME> -id 9778840
% opatch apply -local -oh <ORACLE_HOME> 9352237
2.2.7 Configure the database home
As the database software owner, execute the following:
%cd <UNZIPPED_PATCH_LOCATION>
%9778840/custom/server/9778840/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=q1iylk9uz_172&id=1064804.1

3/4

12/20/2013

Document 1064804.1

%9778840/custom/server/9778840/custom/scripts/postpatch.sh -dbhome <ORACLE_HOME>

REFERENCES
NOTE:1339140.1 - FAQ: OPatch/Patch Questions/Issues for Oracle Clusterware (Grid Infrastructure or CRS) and RAC
Environments
NOTE:948456.1 - Pre 11.2 Database Issues in 11gR2 Grid Infrastructure Environment

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=q1iylk9uz_172&id=1064804.1

4/4