EM 13.5: OMSPatcher Best Practice: How to Avoid Patching Operation from Getting Timed-out or Aborted?
(Doc ID 3044565.1)
Last updated on SEPTEMBER 16, 2024
Applies to:
Enterprise Manager Base Platform - Version 13.5.0.0.0 and later Information in this document applies to any platform.
Goal
Patching the OMS using omspatcher utility takes about 30 minutes to over an hour depending on the size and contents of the OMS_HOME. This activity can be impacted by external factors like the session getting timed out, losing the network or a user interruption. In such cases, the patching is in an inconsistent state and there is no way to resume it unless you restore the OMS home and repository from the backup. This can be challenging and at times impact the downtime window.
This document contains the best practice which should get rid of the timeouts during patching. We leverage the nohup command available on unix to accomplish this.
Nohup, short for no hang up is a command in Linux systems that keep processes running even after exiting the shell or terminal. Nohup prevents the processes or jobs from receiving the SIGHUP (Signal Hang UP) signal. This is a signal that is sent to a process upon closing or exiting the terminal. In this guide, we take a look at the nohup command and demonstrate how it can be used.
Solution
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
