Oracle started Bundle Patch from April2016 by renaming ‘Database Patch for Engineered Systems and Database In-Memory’ to “Database Proactive Bundle Patch”. These were originally limited to Windows and Exadata systems and now its available to Non-windows, Non-Exadata systems as well.

Bundle Patch (BP)
• a collection of fixes to address bugs in a given feature, product, or configuration
For example: Windows Database Bundle Patch, Database Patch for Exadata, Database Proactive Bundle Patch
• a superset of PSU
• may span multiple stack components
For example: “Database Patch for Exadata” includes fixes both Database and Grid Infrastructure
• As of April 2016, the Database Patch for Engineered Systems and Database In-Memory has been renamed to “Database Proactive Bundle Patch”

Database patch content for the various pro-active patch methods might be visualized like this:
• SPU contains only the CPU program security fixes
• PSU contains the CPU program security fixes and additional high-impact/low-risk critical bug fixes
• BP includes all PSU fixes along with fixes targeted at the specific BP environment

Altering the Patching Method
If you wish to change between patching methods then you can do this when upgrading to a new Patch Set Release. For example, if you are on using DB PSU you might then upgrade to and start using “Database Proactive Bundle Patch” (DBBP) instead.

To change patching methods whilst staying on the same Patch Set Release / 4 field version you typically need to:

-Fully rollback the current method patch/es
-This may need you to rollback some interim patches too – make a note of any interim patches rolled back
-Apply / install the new method patch/es to at least the same CPU cycle
-Acquire and apply any interim patches required to maintain the same fixes as were in place before
-You cannot mix BP and DB PSU (or SPU) patching methods in the same ORACLE_HOME.
eg: If you install “Database Proactive Bundle Patch” on a system then you cannot subsequently install a later “Database PSU” (DB PSU) on top of that. You would need to stay on the DBBP path OR fully roll out the DBBP patches and apply DB PSU patches to switch patching methods.

Below are the steps for applying Patch 23273686: DATABASE PROACTIVE BUNDLE PATCH (JUL2016)

1. Download the patch 23273686 and unzip .






2. If PSU patch is exists, make sure to rollback the patch completely including the interim ones.

3. Check conflicts for all patches from GRID OWNER ( ROOT)

4. Now check conflict from ORACLE OWNER ( ORACLE)

5. Check systemspace for GRID patch

5. Check systemspace for ORACLE HOME patch

6. Now run opatchauto analyzer:( from root):

7 . Create the response file :

8. Run the opatchauto apply command:



NOTE: Before applying the patches on production boxes , thorough testing is required is required. 


    1. We have a 12 node exadata machine in which every 2 nodes have a separate DB

      i.e.on node1 and 2 DB1 is running (2 node RAC)

      on node 3 and 4 DB2 is running (2 node RAC)

      on node 5 and 6 DB3 is running (2 node RAC)

      on node 7 and 8 DB4 is running (2 node RAC)

      similarly on node 11 and 12 DB 6 is running.(2 node RAC)

      Now there is an application upgrade which requires DB4 running on 07/08 to have certain DB patch. .

      Can the patch(DBBP) be applied on nodes 7 and 8 excluding all other nodes.The reason why i am asking this question is path of ORACLE_HOME is same across the cluster as it should be (but not shared)..

Leave a Reply

Your email address will not be published. Required fields are marked *

Skip to toolbar