Generic PSU patching considerations

 Patching in a  MIXED version GI/RDBMS env

  • Patch Set Update – Bugs fixed in each PSU (Doc ID 1123863.1)
 Apply patches in a mixed RAC env

RAC PATCHING QUICK REF: Applying CRS PSU, CRS Bundle, GI PSU, Windows Bundles 10.2 - 11.2 (Doc ID 1446371.1)
  Example 2: Grid/ASM home; DB, DB and DB

1. Apply the latest Grid PSU to the GI home. Do NOT apply it to any of the database homes.
2. Apply the latest Grid PSU to the DB home. (This will also automatically apply the latest DB PSU to that home.)
--> GRID PSU can/should be applied to both GRID and RDBMS home

This would translate to :
  - Using opatch auto to apply PSU to the GRID and RDBMS Homes 
  - After that patch database by applying PSU :  
     $GRID_HOME/OPatch/opatch auto  /patch_media   -oh /u01/app/oracle/product/11203/racdb -ocmrf ....
    --> Note I have not yet tested this !

In case of any error please be prepared to manually apply PSU as stated in 
Readme : Patch 19791428 - Combo of OJVM Component DB PSU + GI PSU (Oct2014)
        2.4 Patch Installation ( of course skip 3. Apply the GI PSU patch.) Grid Infrastructure Patch Set Update Patches

  • Grid Infrastructure Patch Set Updates – List of Fixes in each GI PSU (Doc ID 1517790.1)
The table below shows the Grid Infrastructure Patch Set Update patches available for Each link takes you to a 
document with more information about that specific Patch Set Update.
    Document    Version    Download link
    17272731 (Oct 2013) Grid Infrastructure Patch Set Update (GI PSU)    Patch:17272731
    16742216 (Jul 2013) Grid Infrastructure Patch Set Update (GI PSU)    Patch:16742216
    16083653 (Apr 2013) Grid Infrastructure Patch Set Update (GI PSU)    Patch:16083653
    14727347 (Jan 2013) Grid Infrastructure Patch Set Update (GI PSU)    Patch:14727347
    14275572 (Oct 2012) Grid Infrastructure Patch Set Update (GI PSU)    Patch:14275572
    13919095 (Jul 2012) Grid Infrastructure Patch Set Update (GI PSU)    Patch:13919095
    13696251 (Apr 2012) Grid Infrastructure Patch Set Update (GI PSU)    Patch:13696251
    13348650 (Jan 2012) Grid Infrastructure Patch Set Update (GI PSU)    Patch:13348650

Gerneric GI PSU considerations

  • GI PSUs are cumulative and include the Database PSU and associated CPU program security content.
  • Opatch auto is the preferred patch command
  • Opatch auto patches both GI and RDBMS installation
  • Opatch auto for GI patches patches GRID and any database version to
  • For prior RDBMS versions like you add. need to apply the related PSU
  • If you are installing DB PSU version or later, including all, and onwards, then these PSU releases use composite patching. With composite patching the patch version that you need to resolve a conflict may be lower than the DB PSU version that you are installing. You are advised to read Note:1376691.1 for details of composite patches before investigating conflicts on these releases in order to understand why a lower version patch might be applicable.
  • Clusterware/Grid Infrastructure patch  should always be at higher version than the RAC Database homes on the cluster ( refer to Document 337737.1 for details )

Opatch Installation in a RAC env

Always install the latest OPatch utility  ( at least version or later )
Patch 6880880 :      OPatch patch of version for Oracle software releases 11.2.0.x (DEC 2013)

PSU considerations

    This is a marker bug for the (Oct 2013) Grid Infrastructure  Patch Set Update (PSU).
    This Patch Set Update can be downloaded here: Patch:17272731    
    For information about Patch Set Updates please read Note:854428.1 .
    This Grid Infrastructure Patch Set Update includes:
     - The (Oct 2013) Database Patch Set Update (see bug 16902043)
     - Plus all fixes which are included in the Security Patch Update for October 2013 - for 
       details see Note:1571391.1
     - Plus a number of other fixes related to Grid Infrastructure  including all fixed from the (Jul 2013) GI PSU (Bug 16742216)

    For a cumulative list of fixes in the latest GIPSU see Note:1517790.1
    Known Issues
      See Note:1571652.1 for details of Known Issues with this  Grid Infrastructure Patch Set Updat


OracleHome Consideration
  In a pre-11.2 Clusterware environment you will have:
     - A single Clusterware (CRS) home
     - One or more Database (RDBMS) homes at the same or at a lower release level than the Clusterware home (to the 
       4th dot in the release)
     - Optionally a separate dedicated RDBMS home to run ASM (Automatic Storage Management) at the same or at a 
       lower release level than the Clusterware home  (to the 4th dot in the release)
     - In pre-11.2 installations, ASM was implemented using the RDBMS binary installation so this should be treated 
       as a typical RDBMS home

  In a 11.2 Grid Infrastructure environment you will have:
    - A single Grid Infrastructure (GI) Home that implements both ASM and the Clusterware
      Note: Starting with 11gR2 all upgrades of and to Grid Infrastructure MUST be performed "out-of-place" (into 
      a new software home) for this reason there may be more than one clusterware home, however only one will be 
      the active.  
      This "inactive" Clusterware or GI home should be removed once satisfied that the upgrade was successful.
    - One or more database (RDBMS) homes at the same or at a lower release level than the GI home (to the 4th dot 
      in the release)

Patchset considerations
    - Starting with 11gR2, patchset releases are now full releases and no longer require a "base" release, e.g. can be installed directly without having to install first.
    - Prior to 11gR2 - even though the CRS and RDBMS base releases were provided on 
      separate media (downloadable zip file or separate DVD/CD) - the patchsets 
      for both products were delivered as one i.e. the same patchset could be applied to
      the CRS as well as the RDBMS home.
    - Starting with 11gR2 the patchsets for Grid Infrastructure and RDBMS are delivered separately
      (as they are full releases).
    - Clusterware patchsets can be applied in a rolling fashion, while database patchsets cannot. 
      For example, you can rolling upgrade clusterware to,  but you have to shutdown database on all 
      nodes to upgrade to database    

PSU considerations      
    - As the name implies PSUs are patches that are applied on top of a given patchset release. They 
      are released on a quarterly basis and contain fixes for known critical issues for the patchset. 
      PSUs are subject to thorough testing and do not include changes that would alter the functionality 
      of the  software.  With this in mind, PSUs are designed to provide "low risk" and "high value" allowing 
      for customers to more easily adopt proactive patching strategies. 
    - Consider the following PSU facts:
      - All PSUs are installed via "opatch" and are not considered an "upgrade".
      - Database PSUs always contain the CPU for the respective quarter that the PSU is released in.  PSUs and CPUs 
        are NOT compatible meaning if you apply the Database PSU and then want to apply the July 
        CPU this would result in the rollback of the Database PSU.  That said, once a PSU patching strategy 
        is adopted it must be maintained.
      - Independent PSUs are released for both the Database and Clusterware or Grid Infrastructure installations.
           Clusterware PSUs (pre-11.2) are refered to as CRS PSUs
           Grid Infrastructure PSUs are refered to as GI PSUs
       - GI PSUs do contain the Database PSU for the corresponding release, e.g. GI PSU contains the  Database PSU Database PSUs hold true to their name
       - Clusterware PSU refers to CRS PSU for pre-11gR2 and GI PSU for 11gR2.

       -  GI PSUs are always cumulative meaning that you can apply higher version GI PSU directly without having to 
          apply a lower version one first. For example, the GI PSU can be applied to a home without 
          having to apply GI PSU first.
       - Database PSUs can be subject to overlay PSU packaging.  In these cases, the PSUs are still cumulative, but 
         a higher  PSU may require a lower PSU to be applied first; for example, to apply database PSU, 
         you must apply database PSU first.  If a previous PSU is a prerequisite to a 
         later PSU the requirement will be clearly documented in the PSU readme.
       - Unlike other Grid Infrastructure patches (discussed later), 11gR2 GI PSUs contains both GI PSU and Database PSU 
        (YES, both GI and DB PSU) for a particular  quarter. 
        For example, GI PSU contains both the GI PSU and the Database PSU.  
        Once the GI PSU is applied, "opatch lsinventory" will show that both GI PSU and DB PSU are applied  
      - Only CRS PSUs, GI PSUs or other Clusterware/GI patches can be applied to a Clusterware/GI home.

   - In CRS environments, a Clusterware patch (interim, MLR, bundle or PSU) applies to all homes (CRS, ASM and database), 
     while a Database patch applies to the ASM and Database home only
   - In Grid Infrastructure environments, a GI patch (interim, bundle or PSU) applies to all homes (GI and Database), 
     while a Database patch could be  applicable to GI/ASM home if the fix applies to ASM (in this case patch README 
     will tell clearly that it applies to GI/ASM home) 
   - Common identifier in patch README:
            # Product Patched : ORCL_PF ==> Applies to database and pre-11.2 ASM home
            # Product Patched : RDBMS ==> Applies to database and pre-11.2 ASM home
            # Product Patched : CRS/RDBMS ==> Applies to both clusterware and database homes


  • OPatch/Patch Questions/Issues for Oracle Clusterware (Grid Infrastructure or CRS) and RAC Environments (Doc ID 1339140.1)

Leave a Reply

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