Tuesday, October 26, 2010

Announcement: New Recommended Bundle Patch (OCT 2010) for Patch Automation- 10192980(EM & 10193144 (EM

From: Hari Prasanna Srinivasan
Sent: Monday, October 25, 2010 5:47 PM
Subject: Announcement: New Recommended Bundle Patch (OCT 2010) for Patch Automation- 10192980(EM & 10193144 (EM


Hello All,

New Recommended Bundle Patches 10192980(EM and 10193144(EM are available for download from My Oracle Support now.
This patch primarily enhances the Patching functionality offered by Oracle Enterprise Manager Grid Control.
Pre-requisite Patch:
Make sure you apply the pre-requisite patch
9705138 before applying the new patch (applicable to both and series).

For more information, refer to:
Comprehensive Overview of Recommended Bundle Patch 10192980
Comprehensive Overview of Recommended Bundle Patch 10193144
Under  support note - OMS and Agent Patches required for setting up Provisioning, Patching and Cloning in 10.2 to 11.1 GC [ID 427577.1]

This patch is a cumulative and superset of the July 2010 patch (9822322 (EM and 9843796(EM and of the previous releases, and therefore, includes all the features that were introduced as part of those Recommended Bundle Patches.

Key Fixes:

  • Supports patching of the updated Oracle Database Patch Set Updates (PSU) (starting from July2010)
  • Supports patching of Oracle Restart (Grid Infrastructure for Single Instance Databases)
  • Enhanced support for patching Standby and Primary of different data guard configurations present in the same Oracle Home.
  • Fixes around Oracle Exadata Database Machine patching through Grid Control:
    • Exadata: Clusterware patching fails in run crspostroot sript step for the DB machine bundle patch
    • Exadata: Update ignorable SQLs errors for the catexa.sql

#1 If I had applied the previous recommended patches, do I need to rollback before applying this?
Yes, if you had applied any of the patches (
9822322(EM and 9405592 (EM resp.) you would need to rollback the patch and apply this.
For rollback instructions, refer to the patch README from the support note 427577.1

#2 I recently applied the JULY cumulative patch , do I still need the new patch?
The new patch contains additional bug fixes.  (For more info see,
10192980 or 10193144 )
Oracle strongly recommends you to apply the latest patch to make sure your do not encounter these issues and you are at the current patch levels for faster issue resolution through support

#3 Are there any special instructions to apply these patches?
Yes, you need to apply the pre-requisite patch -9705138 before applying the new patches, if not already present.
Note the pre-req. patch was available for July itself, so if you had already installed its should be fine to just go with the OCT patches.

#4 Any more issues seen at customers or learning's ?
a)  "I applied the patches but the version of the deployment procedure remain the same"?
     The patch instructions are not followed up completely. Make sure you run post apply steps - PAR Deploy and SQL apply as per the readme.

b) Are Oracle Database PSUs released in October 2010 an overlay or cumulative patches ?
    Oracle DB PSU for OCT2010 for DB ( is an overlay patch and it requires the base patch either pre-installed or to be co-applied.
    Oracle DB PSUs for OCT2010 for 11.1 and 11.2 DBs are non-overlay (cumulative) patches. For more info refer to,1159443.1 -Patch Set Update and Critical Patch Update October 2010 Availability Document.
    Note: Oracle Grid Control supports application of PSUs on Databases. Apply the recommended bundle patch on EM OMS to support it.

c)  "Is patching 11.2 DBs supported in EM GC"?
   Patching 11.2 DB support is available starting EM only.

Thanks and Regards,

Hari Prasanna Srinivasan
| Principal Product Manager
Oracle System Management Products


Opinions expressed in this blog are entirely the opinions of the writers of this blog, and do not reflect the position of Oracle corporation. No responsiblity will be taken for any resulting effects if any of the instructions or notes in the blog are followed. It is at the reader's own risk and liability.

Blog Archive