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 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

Learn how to resolve and avoid the ORA-01017 error when you have Oracle Data Guard with wallet implemented.
Learn how to identify the row involved in the occurrence of the wait even "enq: TX - row lock contention"
Learn how to resolve the CRS-2304 GPnP profile signature verification failed error when starting an 11.2 database on a 19c cluster.

Need Help?

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