Sunday, September 7, 2014

Latest Bundle Patch for EM12c and White paper for reducing downtime when patching the OMS

Friends,
Enterprise Manager 12.1.0.4 was released in June 2014, and the 12.1.0.4 OMS Bundle patches  have also been released in July 2014. If you have recently upgraded your Enterprise Manager OMS  to 12.1.0.4, it is recommended to apply the latest available bundle patch to your 12.1.0.4 OMS.
For the list of the available Bundle patches or System patches, please refer to the My Oracle Support note “Enterprise Manager 12.1.0.4.0 (PS3) Master Bundle Patch List” (Doc ID 1900943.1). As per this document, the latest bundle patch was released on July 31st 2014 and is System Patch 12.1.0.4.2 which is Patch Number 19176910.
This is a single System patch that includes all the OMS-Side Plug-in Bundles released in July 2014 (Cloud, DB, FMW, Fusion Applications Plug-in (FA), Siebel, Storage Management Plug-in (SMF), Oracle Virtual Infrastructure Plug-in (OVI), and Virtualization Plug-in (VT)).
The previous bundle patch was 12.1.0.4.1 (released on July 2, 2014) which was Patch Number 18945232. This is now superseded by the latest bundle patch 12.1.0.4.2 i.e. Patch Number 19176910 as stated above.
Downtime on the Enterprise Manager OMS will be needed when applying the bundle patch. However, if you have multiple OMS servers (recommended for a large enterprise), then it is possible to reduce the downtime.
You can refer to the new whitepaper on OTN “Reducing Downtime while patching Multi-OMS Environments” for the steps you can take to reduce downtime.  The opatchauto command is used to generate scripts to automate the steps that are required to patch such a scenario.
This blog post was originally published at this link.
Regards,
Porus.

No comments:

Disclaimer

Opinions expressed in this blog are entirely the opinions of the writers of this blog, and do not reflect the position of Oracle corporation. No responsiblity will be taken for any resulting effects if any of the instructions or notes in the blog are followed. It is at the reader's own risk and liability.

Blog Archive