How a clone can help us with a patch (updated to 12c)

Whenever we are going to apply a patch or a patch set update (PSU), the traditional procedure involves stopping all processes running on the Oracle home directory involved, which forces us to stop providing service to start the patching, a process that although it is relatively easy and simple, is subject to eventual failures that, if they occur, can lead to a crisis situation in which the DBA must identify the problem and try to solve it, or choose to rollback. In this article I have published in Oracle Technology Network I explain how to do it, enjoy the reading!
OTN article
OTN article

Did you find this article interesting? Did you have any doubts? Do you want to suggest a topic to cover? Leave me your comments or contact me right now!

Leave a Reply

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

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

Related Posts

Plugin non-CDB + Data Guard
Multitenant is mandatory in Oracle 26ai. Learn how to upgrade from 19c non-CDB to 26ai, including full migration to CDB with Data Guard.
AU rollback: rollback
Patching with AutoUpgrade became very easy, but rolling back still had to be done by hand. Not anymore. Learn how to do it with AutoUpgrade.
Plugin non-CDB
Multitenant is mandatory in Oracle 26ai. Learn how to upgrade from Oracle 19c Non-CDB to 26ai, including the full migration to Container Database (CDB).

Need Help?

Fill in these details and I will be in touch as soon as possible.