Files to Move During Oracle Grid Infrastructure Out-Of-Place Patching

Grid Infrastructure, Patching 1 Minute

Like with Oracle Database, I strongly recommend patching Oracle Grid Infrastructure using the out-of-place method. It has many advantages over in-place patching

A while ago, I wrote about the files you must move during Oracle Database out-of-place patching. There are quite many files to consider. A blog reader left a comment asking about a similar blog post for Oracle Grid Infrastructure, so here it is.

Listener

The listener runs out of the GI home. When you patch out-of-place, the listener must also start in the new GI home.

If you patch using any of the below methods, it will move the listener for you:

The two methods also move listener.ora as part of the process.

If you use opatchauto you should note that the tool moves listener.ora when preparing the new GI using opatchauto apply ... -prepare-clone. You can run that command hours or days before you move the listener. If you add things to listener.ora in between, you must also add it to listener.ora in the new GI home.

Conclusion

There is really nothing to worry about when you patch Oracle Grid Infrastructure out-of-place. The above-mentioned two tools will take care of it for you.

Happy Patching

Published

4 thoughts on “Files to Move During Oracle Grid Infrastructure Out-Of-Place Patching”

  3. I’ve been using out-of-place patching for a long time on-prem (none Exa). When I started to use ExaCS in OCI I was surprised to see the Oracle is not using it there. Any idea why they don’t do it for giHome since they are doing it for dbHome on ExaCS in OCI?

    Like

  4. Hi Kjell,
    I’m glad to hear that you have used out-of-place patching of GI for a long time with a positive experience. I don’t know the exact reason why OCI services don’t use out-of-place for GI. I hope one day the tooling is changed to benefit from the many advantages of out-of-place patching.
    Regards,
    Daniel

    Like

Leave a comment