Applying Enterprise Manager Cloud Control 12c Bundle Patch 1 (Solaris) Part I

As you may know, EM12c BP1 was released for Solaris about 3 weeks ago. Our EM12c runs on Solaris, so I decided to apply it to our production system. To apply BP1 to EM12c environment, first we need to apply BP1 (and additional 1-2 patches) to OMS (Oracle Management Service), then apply some patches to deployed agents, and lastly, upgrade EM12c plug-ins (some of them may require additional patches to be applied to OMS). As you may guess, it’s not a piece of cake. Oracle recommends you to analyze how much effort you need to re-configure and re-deploy agents, and if it’s feasible, uninstall the existing Cloud Control and do a fresh installation.

These instructions are only valid (and tested) for EM12c running gon Solaris 10 (SPARC). You may need additional patches for Linux or AIX. My OMS is located in “/u03/oracle/Middleware/oms/”. My repository DB is “emrep” and located in a server named “erciyes”. Before I start to apply the patch, I stop all services by issuing the following command:

Important: Before you apply Bundle Patch 1, Oracle recommends to back up all EM components:

• Management Repository Database (Highly Recommended!)
• Middleware Home and EM domain
• Instance Home where OMS is installed
• Default Management Agent with OMS
• Software Library
• Oracle Inventory

If patching fails during any stage, you may have to restore these components, and this is not an unsual situation. So be sure to backup all these components.

We’ll apply BP1 (13242773), then required patches for JDeveloper and Web Services Manager (13470978 and 12321965) and 14040891 (for Bug# 14040891). Login to MOS and search for these patches and download them to a directory (I’ll use “/setup”).

Be careful that you should pick 11.1.0.5 release of patch 12321965. I marked the patch you shouldn’t pick on the image:

As usual, we need latest OPatch. Download OPatch for 11.1.0.x. I downloaded p6880880_111000_SOLARIS64.zip and extracted it into OMS directory:

Now I’ll set ORACLE_HOME and PATH variables:

and then I test it:

It worked without any problem. Now we need to download OMS BP1 13242773 from My Oracle Support. I’ll extract the file under “/setup” folder and apply the patch:

OPatch will verifying environment and perform prerequisite checks, backup files, then will roll back the subset patches and apply the BP1. It takes some time (about 1 hour depending on your server configuration).

To complete the patch update, we need to run “post_deploy.sh” but before running it, you should stop EM Jobs. So connect to Repository DB as SYSMAN and issue the following command:

Then run post_deploy.sh script, please refer to the documentation if you have multi-OMS setup. You need to enter repository DB information and SYSMAN password:

After it’s completed, connect to repository DB and check invalid objects and enable EM JOBs:

Now it’s time to apply 13470978 and 12321965 patches. We need to set environment variable ORACLE_HOME to our oracle_common directory and stop OMS:

Extract the patch file (12321965) and apply it (ORACLE_HOME should be set to oracle_common):

So we’ll keep patching with BP1 14040891. We need to set ORACLE_HOME to OMS directory, then apply the patch:

After applying the patch, we need to patch repository and register some metadata:

With the last step, we applied Bundle Patch 1 to Oracle Management Service. If you follow these steps strictly, you shouldn’t get any errors. On my next blog post, I’ll continue with applying required patches to management agents.