My feedback after upgrading EM12c 12.1.0.3 to 12.1.0.5

Today I’ve upgraded EM12c for a customer from the second-last version (12.1.0.3) to the last one (12.1.0.5) and the EM Repository from 11.2.0.3 to 12.1.0.2.

The upgrade path was not very easy: EM 12.1.0.3 is not compatible with a repository 12.1.0.2 and EM 12.1.0.5 requires a mandatory patch for the repository if 11.2.0.3 (or an upgrade to 11.2.0.4).

So I’ve done:

  • upgrade of the repository from 11.2.0.3 (in Data Guard configuration) to 11.2.0.4
  • upgrade of the EM from 12.1.0.3 to 12.1.0.5
  • upgrade of the repository from 11.2.0.4 to 12.1.0.2 (in Data Guard configuration), from Solaris to Linux

 

In my case, I was particularly concerned about my customer’s EM topology:

  • two OMS in load balancing
  • console secured with a custom SSL certificate
  • a good amount of targets (more than 800 total targets, more than 500 targets with status)
  • a lot of jobs and custom reports
  • a big, shared central software library
  • many other small customizations: auth, groups, metrics, templates…

I will not bother with the actual execution steps, every installation may differ, I strongly recommend to read the upgrade documentation (I know, it’s HUGE 🙁 ).

Just to resume, the upgrade guide is here: https://docs.oracle.com/cd/E24628_01/upgrade.121/e22625/toc.htm

in my case I had to read carefully the chapters 3, 4, 5, 6 and appendixes G and K.

By following every step carefully, I had no problems at all and at the end everything was working correctly: all the targets up, the load balancing working in SSL as expected, the jobs restarted and ran successfully…

It has been incredible to see how many operations the OUI has done without raising a single error!!

Ok, it’s not just a Click Next Next Next Next installation, there are a lot of steps to do manually before and afterwards, but still… very good impression.

It took a little more than one hour to upgrade the first OMS (this also upgrades the EM repository) and a little less than 20 minutes to upgrade the second one.

Let a couple of hours for checking everything before, staging the binaries, taking backups/snapshots, creating restore points… and one hours more for upgrading the central agents and cleansing the old installations.

About upgrading/moving the repository, check this good post by Maaz AnjumMIGRATE ENTERPRISE MANAGER 12.1.0.4.0 TO A PDB FROM A NON-CDB, even if you don’t plan to do it, it’s worth a read.

HTH

Ludo

The following two tabs change content below.

Ludovico

Oracle ACE Director and Computing Engineer at CERN
Ludovico is an Oracle ACE Director, frequent speaker and community contributor, working as Computing Engineer at CERN, the European Organization for Nuclear Research, in Switzerland.

7 thoughts on “My feedback after upgrading EM12c 12.1.0.3 to 12.1.0.5

  1. Pingback: My feedback after upgrading EM12c 12.1.0.3 to 12.1.0.5 - Ludovico Caldara - Blogs - triBLOG

  2. Hi Ludo,
    could You tell what was the reson to move to latest version ?
    Did the old one has some missing functionality / features ?
    Regards
    GregG

  3. Hi Greg!
    Main reasons:
    – Need to upgrade the EM repository to 12.1.0.2 (for support reasons, Roadmap etc.)
    – Need to use the AWR Warehouse (appeared in 12.1.0.4)
    – Give a try to the official MySQL plugin (appeared in 12.1.0.5)

    Now, we’re also experiencing better performance overall.

    Cheers

    Ludo

  4. Another reason to upgrade for some. Red Hat 7 is not supported for Oracle agents 12.1.0.3 or earlier. Need to run 12.1.0.4 or 12.1.0.5 agent for that version. So to get agent to 12.1.0.5, need OMS at 12.1.0.5.

  5. Hi,

    why not did you upgrade the Repository first to 12c and then OMS? Is not possible?

    Thanks.

  6. Hi Carlos,
    It was a problem of compatibility matrix.
    the new version of EM required DB 12c, but the current version of EM12c was not compatible with DB 12c, so I had to do it in two steps 🙂

    Ludovico

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.