Patching plays an important role in Oracle Database. In any level of DBA’s interview, they definitely as about Patching. This article explains about the types of patches and steps which use for Applying PSU Patch On 12c RAC In Solaris.

 

Critical Patch Updates (CPU) was started in January 2005. Then Patch Set Updates (PSU) were added as cumulative patches that included prime concern fixes as well as security fixes. As of the October 2012 Critical Patch Update, Oracle has changed the terminology to better differentiate between patch types. This terminology will be used for the Oracle Database, Enterprise Manager, Fusion Middleware, and  WebLogic.

Critical Patch Update (CPU) now refers to the overall release of security fixes each quarter rather than the cumulative database security patch for the quarter. Think of the CPU as the overarching quarterly release and not as a single patch.

Patch Set Updates (PSU) are the same cumulative patches that include both the security fixes and priority fixes. The key with PSUs is they are minor version upgrades (e.g., 11.2.0.1.1 to 11.2.0.1.2). Once a PSU is applied, only PSUs can be applied in future quarters until the database is upgraded to a new base version.

Security Patch Update (SPU) terminology is introduced in the October 2012 Critical Patch Update as the term for the quarterly security patch. SPU patches are the same as previous CPU patches, just a new name. For the database, SPUs cannot be applied once PSUs have been applied until the database is upgraded to a new base version.

Bundle Patches are the quarterly patches for Windows and Exadata which include both the quarterly security patches as well as recommended fixes.

Patching steps are different for different Operating systems. Below are the steps for applying PSU patch on 12C RAC in Solaris.

The patch can be downloaded from OTN. After downloading the patch, copy it to your both the nodes and unzip there.

Here I have unzipped to the location – /softdump/12C_GRIDSOFT/PATCH

Steps of applying PSU Patch On 12c RAC In Solaris

1. Generate a response file for GRID_HOME[ FROM ROOT]

$GRID_HOME/OPatch/ocm/bin/emocmrsp -no_banner -output /softdump/12C_GRIDSOFT/PATCH/grid.rsp
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:

You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: Y
The OCM configuration response file (/softdump/12C_GRIDSOFT/PATCH/grid.rsp) was successfully created.

2. Analyze the patch from GRID_HOME[ FROM ROOT]

 

— go to Opatch location

cd $GRID_HOME/OPatch

— run analyzer

./opatchauto apply /softdump/12C_GRIDSOFT/PATCH/22191349 -analyze -ocmrf /softdump/12C_GRIDSOFT/PATCH/grid.rsp
OPatch Automation Tool
Copyright (c)2014, Oracle Corporation. All rights reserved.

OPatchauto Version : 12.1.0.1.10
OUI Version : 12.1.0.2.0
Running from : /crsapp/app/oracle/product/grid12c

opatchauto log file: /crsapp/app/oracle/product/grid12c/cfgtoollogs/opatchauto/22191349/opatch_gi_2016-04-06_19-00-43_analyze.log

NOTE: opatchauto is running in ANALYZE mode. There will be no change to your system.

OCM RSP file has been ignored in analyze mode.

Parameter Validation: Successful

Configuration Validation: Successful

Patch Location: /softdump/12C_GRIDSOFT/PATCH/22191349
Grid Infrastructure Patch(es): 21436941 21948341 21948344 21948354
DB Patch(es): 21948344 21948354

Patch Validation: Successful
Grid Infrastructure home:
/crsapp/app/oracle/product/grid12c
DB home(s):
/oracle/app/oracle/product/12.1.0.2/dbhome_1

Analyzing patch(es) on “/oracle/app/oracle/product/12.1.0.2/dbhome_1” …
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948344” successfully analyzed on “/oracle/app/oracle/product/12.1.0.2/dbhome_1” for apply.
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948354” successfully analyzed on “/oracle/app/oracle/product/12.1.0.2/dbhome_1” for apply.

Analyzing patch(es) on “/crsapp/app/oracle/product/grid12c” …
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21436941” successfully analyzed on “/crsapp/app/oracle/product/grid12c” for apply.
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948341” successfully analyzed on “/crsapp/app/oracle/product/grid12c” for apply.
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948344” successfully analyzed on “/crsapp/app/oracle/product/grid12c” for apply.
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948354” successfully analyzed on “/crsapp/app/oracle/product/grid12c” for apply.

SQL changes, if any, are analyzed successfully on the following database(s): ULAPROD

Apply Summary:
Following patch(es) are successfully analyzed:
GI Home: /crsapp/app/oracle/product/grid12c: 21436941,21948341,21948344,21948354
DB Home: /oracle/app/oracle/product/12.1.0.2/dbhome_1: 21948344,21948354

opatchauto succeeded.

3. Run autopatch on node 1

This autopatch need to be applied on all the nodes of the rac

— set ORACLE_HOME

export ORACLE_HOME=/crsapp/app/oracle/product/grid12c
cd $ORACLE_HOME/OPatch

— run opatchauto utility

./opatchauto apply /softdump/12C_GRIDSOFT/PATCH/22191349 -ocmrf /softdump/12C_GRIDSOFT/PATCH/grid.rsp
OPatch Automation Tool
Copyright (c)2014, Oracle Corporation. All rights reserved.

OPatchauto Version : 12.1.0.1.10
OUI Version : 12.1.0.2.0
Running from : /crsapp/app/oracle/product/grid12c

opatchauto log file: /crsapp/app/oracle/product/grid12c/cfgtoollogs/opatchauto/22191349/opatch_gi_2016-04-07_09-17-04_deploy.log

Parameter Validation: Successful

Configuration Validation: Successful

Patch Location: /softdump/12C_GRIDSOFT/PATCH/22191349
Grid Infrastructure Patch(es): 21436941 21948341 21948344 21948354
DB Patch(es): 21948344 21948354

Patch Validation: Successful
Grid Infrastructure home:
/crsapp/app/oracle/product/grid12c
DB home(s):
/oracle/app/oracle/product/12.1.0.2/dbhome_1

Performing prepatch operations on CRS Home… Successful

Applying patch(es) to “/oracle/app/oracle/product/12.1.0.2/dbhome_1” …
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948344” successfully applied to “/oracle/app/oracle/product/12.1.0.2/dbhome_1”.
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948354” successfully applied to “/oracle/app/oracle/product/12.1.0.2/dbhome_1”.

Applying patch(es) to “/crsapp/app/oracle/product/grid12c” …
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21436941” successfully applied to “/crsapp/app/oracle/product/grid12c”.
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948341” successfully applied to “/crsapp/app/oracle/product/grid12c”.
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948344” successfully applied to “/crsapp/app/oracle/product/grid12c”.
Patch “/softdump/12C_GRIDSOFT/PATCH/22191349/21948354” successfully applied to “/crsapp/app/oracle/product/grid12c”.

Performing postpatch operations on CRS Home… Successful

SQL changes, if any, are applied successfully on the following database(s): ULAPROD

Apply Summary:
Following patch(es) are successfully installed:
GI Home: /crsapp/app/oracle/product/grid12c: 21436941,21948341,21948344,21948354
DB Home: /oracle/app/oracle/product/12.1.0.2/dbhome_1: 21948344,21948354

opatchauto succeeded.

4. Run autopatch on node 2
5. Now check the status of CRS , and start them if not started.

About The Author

Leave a Reply