Applying – Patch 21352646: DATABASE SECURITY PATCH UPDATE 11.2.0.4.0 (CPUOCT2015)

So we have already discussed in our previous posts how to download this patch along with OPatch utility to apply this patch.

In this post we are going to discuss how to apply this patch:

Step 1: Go to patch directory and take out README.html file to your desktop, to do that we can use WinSCP software.

1

Step 2: As this patch which we downloaded is for Oracle Database 11.2.0.4, so we have to apply this patch on 11.2.0.4 ORACLE_HOME.

Step 3: Just find out what are the instances currently running using ORACLE_HOME.

2

So only 1 Instance is running for now, DB11G, and this one using 11.2.0.4 ORACLE_HOME.

We can have multiple ORACLE_HOME in our environment, may be few will point to 10gR1, few 10gR2, few 11gR1 or may be 11gR2. We need to check ORACLE_HOME always where its is pointing to.

Step 4: Check the listener status too, it looks like, it is also started up from 11.2.0.4 binaries.

3

Step 5: Shutdown all instances and listener which is pointing to 11.2.0.4 ORACLE_HOME. If we will not do that, error will be thrown while applying the patches.

4

Just check once, whether there is anything missed.  Listener Status and Oracle Processes.

5

So we are all set to apply the Patch. We usually need to go through README.html file to perform every step.

Step 6: Open the README.html file and and perform prerequisites:

It looks like below when we open it:

6

Ideally we will start following – Point No : 3 Patch Installation Procedures for Oracle Database Release 11.2.0.4

Normally Point No 3.1.2 says about OPatch Utility and Other information about patch we are applying on RAC (3.1.1).

We can directly go to 3.2.1 which says – Patch Installation Instructions.

By default opatch utility is not being configured, we have two ways to use it. Either we call it from ORACLE_HOME directly or we configure the PATH Variable.

  1. $ORACLE_HOME/OPatch/opatch  <— First Way to use opatch utility
  2. export PATH=$ORACLE_HOME/OPatch:$PATH  <—Second way to call opatch utility.

We will check by both the ways:

[oracle@ora-linux ~]$ opatch version
-bash: opatch: command not found
[oracle@ora-linux ~]$

So opatch is not configured. No use both the ways one by one:

1st Way:

[oracle@ora-linux ~]$ $ORACLE_HOME/OPatch/opatch version
OPatch Version: 11.2.0.3.12

OPatch succeeded.
[oracle@ora-linux ~]$

2nd Way:

[oracle@ora-linux ~]$ export PATH=$ORACLE_HOME/OPatch:$PATH
[oracle@ora-linux ~]$
[oracle@ora-linux ~]$ opatch version
OPatch Version: 11.2.0.3.12

OPatch succeeded.
[oracle@ora-linux ~]$

Step 7: Apply the patch now finally – This step will have the patch applied on ORACLE_HOME:

Go to the patch directory:

[oracle@ora-linux ~]$ cd /tmp/oracle_patches/Patch_p21352646/21352646/
[oracle@ora-linux 21352646]$
[oracle@ora-linux 21352646]$ ls
17811429 17811447 18203837 19463893 19584068 19972566 19972569 20506699 20631274 21051840 21051858 21179898 21538485 21538567 README.html
17811438 18203835 18203838 19544839 19972564 19972568 20142975 20506715 21051833 21051852 21051862 21352646 21538558 patchmd.xml README.txt
[oracle@ora-linux 21352646]$

Check if there is any patch applied on this home before:

7

So there is nothing as of now in this ORACLE_HOME.

Now apply the patch:

[oracle@ora-linux ~]$ cd /tmp/oracle_patches/
OPatch_Utility_11.2.0.3.12/ Patch_p21352646/ Patch_p21555791/
[oracle@ora-linux ~]$ cd /tmp/oracle_patches/Patch_p21352646/21352646/
[oracle@ora-linux 21352646]$
[oracle@ora-linux 21352646]$ export PATH=$ORACLE_HOME/OPatch:$PATH
[oracle@ora-linux 21352646]$
[oracle@ora-linux 21352646]$ opatch napply -skip_subset -skip_duplicate
Oracle Interim Patch Installer version 11.2.0.3.12
Copyright (c) 2015, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/11.2.0.4/db_1
Central Inventory : /u01/app/oraInventory
from : /u01/app/oracle/product/11.2.0.4/db_1/oraInst.loc
OPatch version : 11.2.0.3.12
OUI version : 11.2.0.4.0
Log file location : /u01/app/oracle/product/11.2.0.4/db_1/cfgtoollogs/opatch/opatch2015-12-07_23-48-28PM_1.log

Verifying environment and performing prerequisite checks…

The following patches are duplicate and are skipped:
[ 17811429 17811438 17811447 18203835 18203837 18203838 19463893 19544839 19584068 19972564 ]

OPatch continues with these patches: 19972566 19972568 19972569 20142975 20506699 20506715 20631274 21051833 21051840 21051852 21051858 21051862 21179898 21352646 21538485 21538558 21538567

Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
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

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = ‘/u01/app/oracle/product/11.2.0.4/db_1’)
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files…
Applying interim patch ‘19972566’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms.dbscripts, 11.2.0.4.0…

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘19972568’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.oraolap, 11.2.0.4.0…

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘19972569’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.ovm, 11.2.0.4.0…
Applying interim patch ‘20142975’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms.dbscripts, 11.2.0.4.0…
Applying interim patch ‘20506699’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.xdk.rsf, 11.2.0.4.0…

Patching component oracle.xdk.parser.java, 11.2.0.4.0…

Patching component oracle.rdbms.rsf, 11.2.0.4.0…

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘20506715’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms.rsf, 11.2.0.4.0…

Patching component oracle.rdbms, 11.2.0.4.0…

Patching component oracle.rdbms.dbscripts, 11.2.0.4.0…
Applying interim patch ‘20631274’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘21051833’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘21051840’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘21051852’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms, 11.2.0.4.0…

Patching component oracle.rdbms.dbscripts, 11.2.0.4.0…
Applying interim patch ‘21051858’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘21051862’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.sysman.console.db, 11.2.0.4.0…
Applying interim patch ‘21179898’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘21352646’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms.rsf, 11.2.0.4.0…

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘21538485’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.sysman.agent, 10.2.0.4.5…
Applying interim patch ‘21538558’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms, 11.2.0.4.0…
Applying interim patch ‘21538567’ to OH ‘/u01/app/oracle/product/11.2.0.4/db_1’

Patching component oracle.rdbms.rsf, 11.2.0.4.0…

OPatch found the word “warning” in the stderr of the make command.
Please look at this stderr. You can re-run this make command.
Stderr output:
ins_emagent.mk:113: warning: overriding commands for target `nmosudo’
ins_emagent.mk:52: warning: ignoring old commands for target `nmosudo’
/u01/app/oracle/product/11.2.0.4/db_1/sysman/lib/ins_emagent.mk:113: warning: overriding commands for target `nmosudo’
/u01/app/oracle/product/11.2.0.4/db_1/sysman/lib/ins_emagent.mk:52: warning: ignoring old commands for target `nmosudo’
Patches 19972566,19972568,19972569,20142975,20506699,20506715,20631274,21051833,21051840,21051852,21051858,21051862,21179898,21352646,21538485,21538558,21538567 successfully applied.
OPatch Session completed with warnings.
Log file location: /u01/app/oracle/product/11.2.0.4/db_1/cfgtoollogs/opatch/opatch2015-12-07_23-48-28PM_1.log

OPatch completed with warnings.
[oracle@ora-linux 21352646]$

The warning which we got above, can be safely ignored.

Step 8: Post Installation Steps

As per Step 3.2.2.1 from README.html file, we have to load modified SQL Files into the database:

For each database instance running on the Oracle home being patched, connect to the database using SQL*Plus. Connect as SYSDBA and run the catbundle.sql script as follows:

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catbundle.sql cpu apply
SQL> QUIT

To compile all objects in the database:

cd $ORACLE_HOME/rdbms/admin
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql

We are done with the patch.

Hope its helps..

Advertisements

2 thoughts on “Applying – Patch 21352646: DATABASE SECURITY PATCH UPDATE 11.2.0.4.0 (CPUOCT2015)

  1. Good blog. I am currently applying Oct15 CPU patches and ran into the same exact error, ins_emagent.mk:52:, ins_emagent.mk:113: warning: overriding.

    I do have a question about about post validation. Can I run post validation for both these CPU patches after I apply patch 21555791?
    This following order:
    sqlplus / as sysdba
    startup upgrade
    @postinstall.sql
    shutdown immediate
    exit;

    cd $ORACLE_HOME/rdbms/admin
    sqlplus / as sysdba
    SQL> startup
    SQL> @catbundle.sql cpu apply
    SQL> @utlrp.sql
    SQL> exit;

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s