You have probably heard that Oracle released Enterprise Manager Cloud Control 13c on Friday. It’s the first product from Oracle with the number 13 in its release label. It seems Oracle doesn’t care about the bad luck of 13 🙂 The new version comes with great features and maybe the most significant one is the unification of hardware and software management. In Oracle Enterprise Manager 13c, some of the important hardware management features of “Ops Center” have been included into the Cloud Control product. My company is not a beta tester of Enterprise Manager, so I wanted to upgrade our EM12c system as soon as possible to test the new features by myself. I upgraded our EM12c system yesterday. Well, as I expected, the upgrade process was easy but you should be careful about prerequisites. Carefully check the certification matrix (in My Oracle Support website) before you decide to upgrade your system! EM13c OMS requires Oracle 188.8.131.52 as repository database, and EM13c agents don’t support Enterprise Linux earlier than version 6. We have redhat Enterprise Linux 5.x targets and our repository database was 184.108.40.206 so I have upgraded our repository database and decided to use the “old agents” with EM13c until we upgrade our servers to Enterprise Linux 6.x.
Please take a look at Enterprise Manager Cloud Control Upgrade Guide, before you start upgrading and make sure that you have backed up the repository database and OMS! I’ll try to provide a step by step guide on upgrading EM12c to EM13c running on Linux system, but this is just to give you an idea about overall process, you should always read and follow the official guide.
Important addition from Sumesh: If you have the below obsolete plug-ins in your EM220.127.116.11/4/5 system, then undeploy them from OMS and Agent before proceeding with upgrade to EM13.1:
- EMC Symmetrix Array (oracle.em.sesy)
- EMC Celerra Storage (oracle.em.secs)
- EMC CLARiiON Array (oracle.em.secl)
- Microsoft Biz Talk Server (oracle.em.smbs)
- Exalogic Elastic Cloud Infrastructure (oracle.em.soee)
Make sure the Repopsitory Database and OMS machine are in the same time zone. Eg. UTC or PDT. If the timezone is not same then, Upgrade will fail at ‘Plug-ins Prequisites check’ step.