Patching and Upgrades - Oracle Exadata Recipes: A Problem-Solution Approach - page 342

Assuming that your versions are correct and expected, update the remaining RPMs using the
following command:
# yum --enablerepo=exadata_dbserver_11.2_x86_64_latest update
After a successful validation, you will typically be required to verify your kernel and ofa versions, clear the yum
cache, relink your Oracle binaries, and reboot your server.
Applying QDPE Patches
In this section, you will learn how to apply a typical QDPE patch to the Oracle RDBMS, Grid Infrastructure (GI), and
diskmon binaries on the Exadata Compute Nodes. First, change directories to the database patch staging directory
and install the OPatch patch into each of your RDBMS and GI homes. OPatch is delivered in p6880880_112000_
Linux-x86-64.zip ; you will very likely already have OPatch installed in each Oracle home, but before applying the
QDPE patches, you will need the version that is included in the QDPE patch installed in each home.
Once OPatch is installed, create your Oracle Configuration Management response file in each RDBMS and GI
home to avoid being prompted for your My Oracle Support credentials when opatch runs:
[oracle@cm01dbm01 bin]$ cd $ORACLE_HOME/OPatch/ocm/bin
[oracle@cm01dbm01 bin]$ ./emocmrsp
OCM Installation Response Generator 10.3.4.0.0 - Production
Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved.
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: [e-mail]
Provide your My Oracle Support password to receive security updates via your My Oracle
Support account.
Password (optional):
The OCM configuration response file (ocm.rsp) was successfully created.
[oracle@cm01dbm01 bin]$
... Repeat on all nodes for both the RDBMS and GI Home
Next, validate the inventory on each RDBMS and GI home using the following commands. Use the Oracle
software owner when validating the RDBMS Oracle Home and the Grid Infrastructure owner when validating the
GI Home, and run the validation against each patch contained under the unzipped patch directory according to the
patch README file:
[grid@cm01dbm02 ]$ $GI_HOME/OPaych/opatch lsinventory -detail -oh /u01/app/11.2.0.3/grid
[oracle@cm01dbm01 ~]$ $ORACLE_HOME/OPatch/opatch lsinventory -detail -oh \
/u01/app/oracle/product/11.2.0.3/dbhome_1
After unzipping the individual QDPE patch contents, check for patch conflicts using opatch on both the RDBMS
and GI Oracle Homes:
[grid@cm01dbm01 ~]$ /u01/app/11.2.0.3/grid/OPatch/opatch prereq CheckConflictAgainstOHWithDetail \
> -phBaseDir /u01/stg/14207418/Database/11.2.0.3_QDPE_Jul2012/14103267/14103267
Oracle Interim Patch Installer version 11.2.0.3.0
... Output omitted
Invoking prereq "checkconflictagainstohwithdetail"