Keep your patch versions between Grid Infrastructure and Databases Homes in synch

Patch RecommendationI’ve had some interesting discussions with Anil Nair, our RAC Product Manager and a customer in the past days. The customer was looking for a definite statement that they can have a higher version of Patch Set Updates (PSUs) or Proactive Bundle Patches (BPs) in the Database homes than in the Grid Infrastructure home managing the resources.

Can you have different PSU/BP versions between Database and GI homes?

Yes, you can have a higher version PSU or BP in the Database home than in the Grid Infrastructure home managing the resources. This is implicitly documented in MOS Note 337737.1 – Oracle Clusterware (CRS/GI) – ASM – Database Version Compatibility where it says:

The Oracle Grid Infrastructure (GI) /Clusterware (CRS) version must be of the highest version down to the 4th digit in the possible combinations at all times.

Therefore you can deviate that this rule does not apply for the 5th digit anymore. Anil and I discussed that this may be documented a bit more clear – and he will take care.

Should you have different PSU/BP versions between Database and GI homes?

Well, this question is a bit harder. I can see why some customers have a higher patch level (5th digit) in the Database homes than in their GI homes. Actually some of my customers have this setup as well. GI is pretty stable above a certain patch level and often gets not treated with the same importance than the database homes as the need for patching in database homes is more obvious and visible. When it’s stable don’t touch it. And honestly speaking, patching is no fun – but hard work.

But we strongly recommend that you keep your patch levels in synch. If you apply the GI PSU of April 2017 then please apply the Database PSU or BP of April 2017 as well. These are the combinations we test internally. Please bear in mind that while the GI and DB are separate entities, they are tightly integrated and work cohesively. This way you mitigate the potential risk of an untested issue by having differences in the 5th digit.

And as a final hint:
Grid Infrastructure PSUs (and BPs) can be applied always in a rolling fashion causing no downtime. Just saying …



8 thoughts on “Keep your patch versions between Grid Infrastructure and Databases Homes in synch

  1. Hi mike
    On a mixed rdbms home under GI Clusterware Do I need to apply DB PSU or GI PSU on those rdbms homes?
    This is what I have on my env
    2 server Linux
    1 home GI
    2 homes RDBMS RDBMS

    Best regards

    • William,

      on the GI homes you’ll apply the GI PSU.
      On the databases homes I’d recommend you to apply the Database BP for 12c – and for your installation the Database PSU for


  2. Pingback: Man with two wife's situation - ODA Database Patching |

  3. Pingback: Riding on two horses - ODA Database Patching |

  4. Hello Mike,
    How’s the situation with the new RU/RUR versioning scheme? Can we run RDBMS RU/RUR > GI RU/RUR?

  5. Hi Mike,
    We have a customer with a GI and DB home, not having applied any PSU since 2014.
    They ask us to do a move to a new server and an upgrade to version 12.2.
    Is it possible (on the old server) to only patch the DB home with the latest PSU?
    I will explain why….
    Next step in the project is to move the databases to a new server. On that new server we will install GI 12.2 (and apply the latest RU for GI 12.2) and create physical standby databases in DB home.
    After a failover to the new server, last step is to upgrade the databases to 12.2 on this new server.
    I think it is a good idea to patch the databases with the latest PSU before upgrading to 12.2, but I see no need to apply 12.1 PSU because of the move to a new server.
    What do you think about this?

    Best regards,

Leave a Reply

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

* Checkbox to comply with GDPR is required


I agree

This site uses Akismet to reduce spam. Learn how your comment data is processed.