Thursday, June 09, 2011

Learn: Patch 12311357 - 11.2.0.2.2 GI PSU

This post is not write How to Patch 12311357 - 11.2.0.2.2 GI PSU, Because you can read it on "README.html" file in "p12311357_112020_*.zip". I just write what I used Patch 12311357 on my system. I have 2 nodes on Grid Infrastructure (RAC): Oracle Grid Infrastructure(11.2.0.2.0) + Oracle Database 11g (11.2.0.2.0).***NO Interim patches installed***
Read & Do & Learn !!!
*** GRID_HOME=/u01/app/11.2.0/grid , ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1 ***

1. OPatch Utility Information - OPatch utility version 11.2.0.1.5 or later (download at My Oracle Support patch 6880880). Don't just download, unzip and use it. You should install it in GRID_HOME/OPatch and ORACLE_HOME/OPatch (all nodes). Because: error!!!
The opatch minimum version check for patch SRC/PATCH/12311357 failed for GRID_HOME
The opatch minimum version check for patch SRC/PATCH/11724916 failed for GRID_HOME
Opatch version check failed for oracle home GRID_HOME
Opatch version check failed
update the opatch version for the failed homes and retry
$ id
uid=440(oracle) gid=200(oinstall) groups=200(oinstall),201(dba),202(oper
$ cd GRID_HOME
$ unzip SRC/p6880880_112000_Linux-x86-64.zip
Archive: SRC/p6880880_112000_Linux-x86-64.zip
replace OPatch/crs/patch112.pl? [y]es, [n]o, [A]ll, [N]one, [r]ename: A

$ cd ORACLE_HOME
$ unzip SRC/p6880880_112000_Linux-x86-64.zip
Archive: SRC/p6880880_112000_Linux-x86-64.zip
replace OPatch/crs/patch112.pl? [y]es, [n]o, [A]ll, [N]one, [r]ename: A

$ GRID_HOME/OPatch/opatch version
Invoking OPatch 11.2.0.1.5

OPatch Version: 11.2.0.1.5

OPatch succeeded.

$ ORACLE_HOME/OPatch/opatch version
Invoking OPatch 11.2.0.1.5

OPatch Version: 11.2.0.1.5

OPatch succeeded.
*** do it all nodes ***

2. OCM Configuration - The OPatch utility will prompt for your OCM (Oracle Configuration Manager) response file when it is run.
# opatch auto SRC/PATCH -oh GRID_HOME
Executing /usr/bin/perl GRID_HOME/OPatch/crs/patch112.pl -patchdir SRC -patchn PATCH -och GRID_HOME -paramfile GRID_HOME/crs/install/crsconfig_params
opatch auto log file location is GRID_HOME/OPatch/crs/../../cfgtoollogs/opatchauto2011-06-09_14-30-45.log
Detected Oracle Clusterware install
Using configuration parameter file: GRID_HOME/crs/install/crsconfig_params
OPatch is bundled with OCM, Enter the absolute OCM response file path:
If you do not have the OCM response file (ocm.rsp), You can create it.
# GRID_HOME/OPatch/ocm/bin/emocmrsp
However, this need to connect https://ccr.oracle.com !!! I can not access internet from my System. How can I do?
***You can also invoke opatch auto with the -ocmrf <OCM response file path> option to run opatch auto in silent mode.***
I downloaded new OPatch and installed on somewhere it can access Internet:
$ ./OPatch/ocm/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: surachart@domain
Password (optional):
file (ocm.rsp) was successfully created.
Password is optional... You don't fill in. just Enter !!! ..
when you have ocm.rsp file. So, Use opatch auto SRC/PATCH -oh GRID_HOME -ocmrf ocm.rsp

3. Validation of Oracle Inventory - check the consistency of inventory information for GI home and each database home
$ opatch lsinventory -detail -oh <GRID_HOME>
$ opatch lsinventory -detail -oh <ORACLE_HOME>
4. Download Patch and Unzip -In README.html file, Oracle recommends unzip in shared location to be able to access it from any node in the cluster. I have no shared PATH!!! So I unzip it on each node (all nodes).
$ cd SRC/PATCH
$ unzip ../p12311357_112020_Linux-x86-64.zip
4. Stop database/Stop CRS
$ srvctl stop database –d db
# GRID_HOME/bin/crsctl stop crs
5. Start Patch - use "root" user for "opatch auto"
On node01:
# opatch auto SRC/PATCH -oh GRID_HOME -ocmrf ocm.rsp
Executing /usr/bin/perl GRID_HOME/OPatch/crs/patch112.pl -patchdir SRC -patchn PATCH -oh GRID_HOME -ocmrf ocm.rsp -paramfile GRID_HOME/crs/install/crsconfig_params
opatch auto log file location is GRID_HOME/OPatch/crs/../../cfgtoollogs/opatchauto2011-06-09_14-31-12.log
Detected Oracle Clusterware install
Using configuration parameter file: GRID_HOME/crs/install/crsconfig_params

Successfully unlock GRID_HOME

patch SRC/PATCH/12311357 apply successful for home GRID_HOME
patch SRC/PATCH/11724916 apply successful for home GRID_HOME
CRS-4123: Oracle High Availability Services has been started.

# opatch SRC/PATCH -oh ORACLE_HOME -ocmrf ocm.rsp
Executing /usr/bin/perl GRID_HOME/OPatch/crs/patch112.pl -patchdir SRC -patchn PATCH -oh ORACLE_HOME -ocmrf ocm.rsp -paramfile GRID_HOME/crs/install/crsconfig_params
opatch auto log file location is GRID_HOME/OPatch/crs/../../cfgtoollogs/opatchauto2011-06-09_14-52-14.log
Detected Oracle Clusterware install
Using configuration parameter file: GRID_HOME/crs/install/crsconfig_params
patch SRC/PATCH/12311357/custom/server/12311357 apply successful for home ORACLE_HOME
patch SRC/PATCH/11724916 apply successful for home ORACLE_HOME
Then On node02:
# opatch auto SRC/PATCH -oh GRID_HOME -ocmrf ocm.rsp
Executing /usr/bin/perl GRID_HOME/OPatch/crs/patch112.pl -patchdir SRC -patchn PATCH -oh GRID_HOME -ocmrf ocm.rsp -paramfile GRID_HOME/crs/install/crsconfig_params
opatch auto log file location is GRID_HOME/OPatch/crs/../../cfgtoollogs/opatchauto2011-06-09_15-17-39.log
Detected Oracle Clusterware install
Using configuration parameter file: GRID_HOME/crs/install/crsconfig_params
Clusterware is either not running or not configured. You have the following 2 options
1. Configure and Start the Clusterware on this node and re-run the tool
2. or Run the tool with the -och <CRS_HOME_PATH> option and then invoke tool with -oh <comma seperated ORACLE_HOME_LIST> to patch the RDBMS home

# opatch auto SRC/PATCH -och GRID_HOME -ocmrf ocm.rsp
Executing /usr/bin/perl GRID_HOME/OPatch/crs/patch112.pl -patchdir SRC -patchn PATCH -och GRID_HOME -ocmrf ocm.rsp -paramfile GRID_HOME/crs/install/crsconfig_params
opatch auto log file location is GRID_HOME/OPatch/crs/../../cfgtoollogs/opatchauto2011-06-09_15-18-17.log
Detected Oracle Clusterware install
Using configuration parameter file: GRID_HOME/crs/install/crsconfig_params

Successfully unlock GRID_HOME
patch SRC/PATCH/12311357 apply successful for home GRID_HOME
patch SRC/PATCH/11724916 apply successful for home GRID_HOME
CRS-4123: Oracle High Availability Services has been started.

# opatch auto SRC/PATCH -oh ORACLE_HOME -ocmrf ocm.rsp
Executing /usr/bin/perl GRID_HOME/OPatch/crs/patch112.pl -patchdir SRC -patchn PATCH -oh ORACLE_HOME -ocmrf ocm.rsp -paramfile GRID_HOME/crs/install/crsconfig_params
opatch auto log file location is GRID_HOME/OPatch/crs/../../cfgtoollogs/opatchauto2011-06-09_15-36-22.log
Detected Oracle Clusterware install
Using configuration parameter file: GRID_HOME/crs/install/crsconfig_params
patch SRC/PATCH/12311357/custom/server/12311357 apply successful for home ORACLE_HOME
patch SRC/PATCH/11724916 apply successful for home ORACLE_HOME
*** CRS should started, after patched GRID_HOME, if not # GRID_HOME/bin/crsctl start crs ***
*** I have no ACFS, So don't write about it ***

6. Run the catbundle.sql script
For each database instance running on the Oracle home being patched, You have to run the catbundle.sql script(For a RAC environment, perform these steps on only one node).
$ cd $ORACLE_HOME/rdbms/admin
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql psu apply
SQL> QUIT
Check:
SQL> select * from dba_registry_history;

ACTION_TIME ACTION NAMESPACE VERSION ID BUNDLE_SERIES COMMENTS
----------------------------------- ---------- ---------- ---------- ---------- --------------- ------------------------------
05-SEP-10 06.22.14.370943 AM APPLY SERVER 11.2.0.2 0 PSU Patchset 11.2.0.2.0
29-NOV-10 04.26.43.893905 PM APPLY SERVER 11.2.0.2 0 PSU Patchset 11.2.0.2.0
09-JUN-11 03.54.58.093408 PM APPLY SERVER 11.2.0.2 2 PSU PSU 11.2.0.2.2
$ opatch lsinventory -bugs_fixed | grep -i 'DATABASE PSU'
10248523 11724916 Thu Jun 09 15:01:18 ICT 2011 DATABASE PSU 11.2.0.2.1
11724916 11724916 Thu Jun 09 15:01:18 ICT 2011 DATABASE PSU 11.2.0.2.2 (INCLUDES CPUAPR2011)
12311357 12311357 Thu Jun 09 14:56:37 ICT 2011 GI PSU 11.2.0.2.2 (INCLUDES DATABASE PSU 11.2.0.2.
*** Start database resource "$ srvctl start database -d db" if database not start all nodes ***

7. Validation of Oracle Inventory again.
$ opatch lsinventory detail -oh GRID_HOME
Invoking OPatch 11.2.0.1.5

Oracle Interim Patch Installer version 11.2.0.1.5
Copyright (c) 2010, Oracle Corporation. All rights reserved.

Oracle Home : GRID_HOME
Central Inventory : ORACLE_BASE/oraInventory
from : /etc/oraInst.loc
OPatch version : 11.2.0.1.5
OUI version : 11.2.0.2.0
OUI location : GRID_HOME/oui
Log file location : GRID_HOME/cfgtoollogs/opatch/opatch2011-06-09_17-36-03PM.log

Patch history file: GRID_HOME/cfgtoollogs/opatch/opatch_history.txt

Lsinventory Output file location : GRID_HOME/cfgtoollogs/opatch/lsinv/lsinventory2011-06-09_17-36-03PM.txt
--------------------------------------------------------------------------------
Installed Top-level Products (1):

Oracle Grid Infrastructure 11.2.0.2.0
There are 1 products installed in this Oracle Home.

Interim patches (2) :

Patch 11724916 : applied on Thu Jun 09 14:44:43 ICT 2011
Unique Patch ID: 13762085
Created on 1 Apr 2011, 07:09:05 hrs PST8PDT
Bugs fixed:
10151017, 10158965, 11724916, 10190642, 10129643, 10018789, 9744252
10248523, 9956713, 10356513, 9715581, 9770451, 10170431, 10425676
10222719, 9591812, 10127360, 10094201, 11069199, 10245086, 10205230
10052141, 11818335, 11830776, 11830777, 9905049, 11830778, 10077191
10358019, 10219576, 10264680, 10209232, 10102506, 11067567, 9881076
10040531, 10218814, 9788588, 9735237, 10230571, 10079168, 10228151
10013431, 10217802, 10238786, 10052956, 11699057, 10080579, 10332111
10227288, 10329146, 10332589, 10110863, 10073683, 10019218, 10229719
10373381, 11724984, 9539440, 10411618, 10022980, 10187168, 6523037
9724970, 10084145, 10157402, 9651350, 10299224

Patch 12311357 : applied on Thu Jun 09 14:40:38 ICT 2011
Unique Patch ID: 13762085
Created on 5 Apr 2011, 09:13:41 hrs PST8PDT
Bugs fixed:
12311357, 10425672, 10244210, 11655840, 10634513, 9891341, 11782423
11077756, 10376847, 10157506, 10178670, 9959110, 10314123, 10014392
10157622, 10089120, 10057296, 10053985, 9864003, 10044622, 9812970
10083789, 10073372, 9876201, 9963327, 10375649, 9336825, 10062301
10018215, 10105195, 10007185, 10071992, 10038791, 10048487, 9926027
10260251, 10052721, 10028235, 10027079, 10028343, 10231906, 10065216
10045436, 9907089, 10175855, 10284828, 10072474, 10036834, 10028637
10029900, 9974223, 9979706, 10016083, 10015460, 9918485, 9971646, 10040647
9978765, 10069541, 9915329, 10107380, 10110969, 10305361, 10029119
10233159, 10083009, 9812956, 10008467, 10036193, 10048027, 10040109
10015210, 9944978, 10033106, 9978195, 10042143, 10284693, 9679401
10111010, 10075643, 10057680, 10205290, 10124517, 10078086, 9944948
10146768, 10052529, 10011084, 10073075, 10248739, 10236074, 10128191
9975837, 10168006, 9949676, 10228079, 10015603, 10241696, 9861790
10069698, 10056808, 10087118, 10283058, 10252497, 10146744, 10326548
10157625, 10283167, 10019796, 9975343, 10216878, 9906432, 10045316
10029794, 10425675, 10061534, 10193581, 10070563, 10283549, 10311856
10150020, 10268642, 10283596

Rac system comprising of multiple nodes
Local node = node01
Remote node = node02
--------------------------------------------------------------------------------
OPatch succeeded.

$ opatch lsinventory detail -oh ORACLE_HOME
Invoking OPatch 11.2.0.1.5

Oracle Interim Patch Installer version 11.2.0.1.5
Copyright (c) 2010, Oracle Corporation. All rights reserved.

Oracle Home : ORACLE_HOME
Central Inventory : ORACLE_BASE/oraInventory
from : /etc/oraInst.loc
OPatch version : 11.2.0.1.5
OUI version : 11.2.0.2.0
OUI location : ORACLE_HOME/oui
Log file location : ORACLE_HOME/cfgtoollogs/opatch/opatch2011-06-09_17-36-13PM.log

Patch history file: ORACLE_HOME/cfgtoollogs/opatch/opatch_history.txt

Lsinventory Output file location : ORACLE_HOME/cfgtoollogs/opatch/lsinv/lsinventory2011-06-09_17-36-13PM.txt
--------------------------------------------------------------------------------
Installed Top-level Products (1):

Oracle Database 11g 11.2.0.2.0
There are 1 products installed in this Oracle Home.

Interim patches (2) :

Patch 11724916 : applied on Thu Jun 09 15:01:18 ICT 2011
Unique Patch ID: 13762085
Created on 1 Apr 2011, 07:09:05 hrs PST8PDT
Bugs fixed:
10151017, 10158965, 11724916, 10190642, 10129643, 10018789, 9744252
10248523, 9956713, 10356513, 9715581, 9770451, 10170431, 10425676
10222719, 9591812, 10127360, 10094201, 11069199, 10245086, 10205230
10052141, 11818335, 11830776, 11830777, 9905049, 11830778, 10077191
10358019, 10219576, 10264680, 10209232, 10102506, 11067567, 9881076
10040531, 10218814, 9788588, 9735237, 10230571, 10079168, 10228151
10013431, 10217802, 10238786, 10052956, 11699057, 10080579, 10332111
10227288, 10329146, 10332589, 10110863, 10073683, 10019218, 10229719
10373381, 11724984, 9539440, 10411618, 10022980, 10187168, 6523037
9724970, 10084145, 10157402, 9651350, 10299224

Patch 12311357 : applied on Thu Jun 09 14:56:37 ICT 2011
Unique Patch ID: 13762085
Created on 5 Apr 2011, 09:13:41 hrs PST8PDT
Bugs fixed:
12311357, 10425672, 10157506, 11655840, 10634513, 9891341, 11782423
11077756, 10376847, 10178670, 9959110, 10314123, 10014392, 10157622
10089120, 10057296, 10053985, 9864003, 10044622, 9812970, 10083789
10073372, 9876201, 9963327, 10375649, 9336825, 10062301, 10018215
10105195, 10007185, 10071992, 10038791, 10048487, 9926027, 10260251
10052721, 10028235, 10027079, 10028343, 10231906, 10065216, 10045436
9907089, 10175855, 10284828, 10072474, 10036834, 10028637, 10029900
9974223, 9979706, 10016083, 10015460, 9918485, 9971646, 10040647
9978765, 10069541, 9915329, 10107380, 10110969, 10305361, 10029119
10233159, 10083009, 9812956, 10008467, 10036193, 10048027, 10040109
10015210, 9944978, 10033106, 9978195, 10042143, 10284693, 9679401
10111010, 10075643, 10057680, 10205290, 10124517, 10078086, 9944948
10146768, 10052529, 10011084, 10073075, 10248739, 10236074, 10128191
9975837, 10168006, 9949676

Rac system comprising of multiple nodes
Local node = node01
Remote node = node02
--------------------------------------------------------------------------------
OPatch succeeded.
*** sorry for no rollback process ... you can read it from readme.html file ***

Wow!!! learned from patching "Patch 12311357 - 11.2.0.2.2 GI PSU"

7 comments:

DanyC said...

Nice job, thx!

Would be interesting to see if the rolling upgrade works ?

Have you tried?

Thx,
Dani

Surachart said...

Yes, It's work.
I tested it.

Sam said...

I tried yday to install the PSU patch for July 2011 and it failed on trying to rollback 12311357 (April 2011 PSU) because it seems that the directory for rollback under .patch_storage is not existing.
So cant rollback the April PSU which is causing me to be unable to move forward with the July PSU patch. There appears to be an option to forcibly rollback the April PSU 12311357 by removing it from the inventory but this will not actually copy the back up files back,
was wondering whether I can do this and resume the July 2011 PSU, will this corrupt the cluster (11202 GI)? As PSUs are cumulative can I assume that the July PSU will cover all of the files modified by the April 2011 PSU and the April 2011 PSU will not contain any extra files modified?

Surachart said...

To SAM
rollback... error and no folder... you may not rollback.

If you have this folder and compatible with previous oracle database.... I think you can use it

Patching .. oracle changes some library... you can not change oracle inventory only....

you have to rollback library...

however, please show your error....

Steve said...

I installed the April PSU, then the July PSU...then rolled back the July PSU and the April PSU was also removed and it rolled it back to 11.2.0.2. Is this expected behavior? I don't recall this being the rollback behavior in 10.

Surachart said...

I don't get your idea. If you need to remove PSU... you should make sure. You have to have previous library(for roll back).

Steve said...

The install of the July PSU is removing the April PSU by default. So, if we want to retain the ability to rollback from July to April, in the case of a failure, how to we retain the library, so in the case of the need to rollback, we can do so successfully. Thanks!