Enterprise Manager Cloud Control 12.1.0.4 is released yesterday, and I have downloaded it immediately to upgrade our system. It was a very smooth process. The version of our Enterprise Manager was 12.1.0.3. Enterprise Manager 12.1.0.4 is compatible with 12.1.0.3 agents, so total downtime was about 30 minutes (of course it depends on your hardware). I upgraded our system using “one system upgrade” option and then upgraded all EM agents. Only a few agents are failed to upgrade, and I remember that we also had problems when deploying those agents. In this blog post, I will go through the whole process step by step.

I recommend you to read the official upgrade documentation (Thanks to Brandon to remind me to write this). As a blogger, I share my own experience. I can not guarantee that these steps will work on your environment, so you should always check the official documentation first.

As usual, you can download the new version from Oracle website. You need to download all 3 zip files to your server, create a directory and unzip them all into this directory:

Before you run the installer, we need to prepare our system for upgrading. Run emctl to copy EMKey from emkey.ora file to the management repository database:

Enter weblogic admin password as Admin User’s password and SYSMAN password for EM root password. The EMKey will be copied to the Management Repository (it will be removed automatically by the installer after the upgrade is done). Now shutdown the OMS:

Enterprise Manager will check if SYSMAN and DBSNMP has execute privilege to DBMS_RANDOM package and PUBLIC role has NO access to DBMS_RANDOM. So connect to your repository database as SYS and issue the following commands:

You also need to be sure that there are no invalid packages on repository database:

Although there were no invalid objects belong to these users, Enterprise Manager warned me about invalid objects. Maybe it doesn’t like to see that I have invalid objects in my APEX schema. I just ignored its warning.

An important warning: You should surely back up your repository database before starting to the upgrade process!

If there are no invalid objects in EM repository database and you had a valid backup, we are ready to go. Just run the installer:

Oracle Support Details

You enter Oracle support email and password or uncheck “receiving security updates” and click next.

step02

It’s released yesterday so I just skipped checking software updates.

step03

Verify that all prerequisite checks are succeeded. Click next.

step04

I have chosen the one system upgrade. As you can see it detects the correct home of the existing Enterprise Manager installation.

step05

Enter the new middleware home for upgraded Enterprise Manager, and click next to continue.

step06

Enter the SYS and SYSMAN password of the repository database. As you can see, the installer reminds you to backup your repository database. Check if you have already backup your database, and click continue. At this step, the installer also warns you about required patches, suspending jobs during upgrade. Click OK and YES to these dialogs and go to next step.

step07

Enterprise Manager will show a summary about plugins. As you can see it will update some plugins, keep some and also deploy some mandatory plugins. Click next to continue.

step08

In this step, you can add additional plugins. Check the ones you want and click next.

step09

Enter the weblogic admin password of the existing weblogic installation, and the path of OMS base location. It’s recommended to enter a path under your new middleware!

Review

Review the inputs and click install if everything looks OK.

Almost done

It took about 30 minutes on our site. After the installation is completed, you need to login as root and run a shell script. After running the script, click OK to finish the installation.

Upgrade Agents

Now all you need is to upgrade your agents. Login to Enterprise Manager, open “upgrade agents” located under “manage cloud control” in setup menu. Add the agents to the list, and click submit.

Ignore the warning

If you haven’t set privileged credentials, or you don’t want to enter this info right now, you can just ignore the warning. That’s all. As I said, it was a very smooth process and everything went fine.

26 Responses to “Upgrading Enterprise Manager Cloud Control 12.1.0.3 to 12.1.0.4”

  1. Courtney says:

    Just out of curiosity, how big is your site?   Upgrade timing can increase on larger sites so I’m trying to get a baseline for other customers ;)

    • Gokhan Atil says:

      It’s a small site, containing less than 50 hosts and 300 targets. EM12c OMS and Repository Database are running on same host.

  2. Great news. I’m hoping my upgrade goes as well. I’ll probably try an upgrade at home on the weekend. If that goes well, pencil in one for work soon…

    Cheers

    Tim…

  3. Brandon Cole says:

    http://docs.oracle.com/cd/E24628_01/upgrade.121/e22625/upgrading_12101_PS1_gtgstrtd.htm#CIHJGEEB

    I don’t see that you have mentioned reading the actual upgrade documentation and you have left out some very serious checks that I don’t see being performed and the docs state will ruin your installation if not completed.

    • Gokhan Atil says:

      Brandon, thanks for your comment. As you see, it has completed without any problem (nothing ruined), but you’re absolutely right that I should have mentioned the documentation. Although I checked the documentation, I forgot to write it. I’ll add it to post. On the other hand, most of them are not related my system (such as database service instance creation requests, snapshots of EM tables, BI Publisher etc ) and some of them are already implemented (because I have an uptodate repository database 11.2.0.4)

  4. Tony Price says:

    So EM12c 12.1.0.4 is certified with 12.1.0.1 database repository.

    Is anyone considering upgrading repository database to 12.1.0.1 with this upgrade?

  5. Merhaba Gökhan Hocam ben linux üzerinde 12.1.0.3′den upgrade yaptım 12.1.0.4′e.

    Daha sonra linux üzerinde ki agent’leri de upgrade yaptım fakat windows agent’ler 12.1.0.3 olarak gözüküyor ve listede 12.1.0.4 windows agent yok.Windows  12.1.0.4 agent dosyası var mı,varsa nereden indirebilirim bu dosyayı?Şimdiden Teşekürler

    • Gokhan Atil says:

      Selam Kenan,

      Henüz windows için 12.1.0.4 agentları yayınlanmadı. Bir iki haftaya yayınlanır diye düşünüyorum.

  6. samidee says:

    Hi, thanks for the article,

    is it possible to uninstall old middleware home after succefull install?

    thanks and regards

  7. Thank you for this. I’m in the planning stages, using this documentation as well as the official documentation from Oracle.

    In my 12.1.0.3 installation I see these invalid synonyms, the comment for each one says ‘deprecated’. I don’t see a reference to them anywhere, if it’s okay to continue. I’m digging deeper to figure out why they are invalid, but perhaps I don’t need to.

    owner object_name
    MGMT_VIEW MGMT$DELTA_COMPONENTS
    MGMT_VIEW MGMT$DELTA_COMPONENT_DETAILS
    MGMT_VIEW MGMT$DELTA_FS_MOUNT
    MGMT_VIEW MGMT$DELTA_HARDWARE
    MGMT_VIEW MGMT$DELTA_ONEOFF_PATCHES
    MGMT_VIEW MGMT$DELTA_ORACLE_HOME
    MGMT_VIEW MGMT$DELTA_OS_COMPONENTS
    MGMT_VIEW MGMT$DELTA_OS_COMP_DETAILS
    MGMT_VIEW MGMT$DELTA_OS_KERNEL_PARAMS
    MGMT_VIEW MGMT$DELTA_PATCHSETS
    MGMT_VIEW MGMT$DELTA_PATCHSET_DETAILS
    MGMT_VIEW MGMT$DELTA_VENDOR_SW
    MGMT_VIEW MGMT$DELTA_VIEW_DETAILS
    MGMT_VIEW MGMT$ECM_CONFIG_HISTORY
    SYSMAN_RO MGMT$DELTA_COMPONENTS
    SYSMAN_RO MGMT$DELTA_COMPONENT_DETAILS
    SYSMAN_RO MGMT$DELTA_FS_MOUNT
    SYSMAN_RO MGMT$DELTA_HARDWARE
    SYSMAN_RO MGMT$DELTA_ONEOFF_PATCHES
    SYSMAN_RO MGMT$DELTA_ORACLE_HOME
    SYSMAN_RO MGMT$DELTA_OS_COMPONENTS
    SYSMAN_RO MGMT$DELTA_OS_COMP_DETAILS
    SYSMAN_RO MGMT$DELTA_OS_KERNEL_PARAMS
    SYSMAN_RO MGMT$DELTA_PATCHSETS
    SYSMAN_RO MGMT$DELTA_PATCHSET_DETAILS
    SYSMAN_RO MGMT$DELTA_VENDOR_SW
    SYSMAN_RO MGMT$DELTA_VIEW_DETAILS

  8. Okay, so forget that last comment, sorry. It was one of those quite confusing synonym things where I had to access the object to make it VALID. Sometimes a DESCRIBE worked, other times a SELECT * was needed.
    I hate that.

  9. Hi,

    Maybe someone here can help:

    I try to upgrade EM 12.1.0.3 to EM 12.1.0.4.

    When the Repository-Upgrade is fails and in the Logfile I can not see anything
    about what’s going wrong.

    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Completed…
    INFO: oracle.sysman.top.oms:Starting both repos upgrade and transx loading in parallel
    INFO: oracle.sysman.top.oms:Running the repository in the upgrade mode
    INFO: oracle.sysman.top.oms:The command run for transx is /opt/oracle/product/EM_12.1.0.4/oms/sysman/admin/emdrep/bin/RepManager -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=podb2.lan.hbd)(PORT=1521)))(CONNECT_DATA=(SID=pdboem2))) -action transx  -repos_user SYSMAN -dbUser SYS -mwHome /opt/oracle/product/EM_12.1.0.4 -mwOraHome /opt/oracle/product/EM_12.1.0.4/oms
    INFO: oracle.sysman.top.oms:/bin/sh: module: line 1: syntax error: unexpected end of file
    INFO: oracle.sysman.top.oms:/bin/sh: error importing function definition for `module’
    INFO: oracle.sysman.top.oms:processing arguments
    INFO: oracle.sysman.top.oms:compiling arguments for validation
    INFO: oracle.sysman.top.oms:stty: standard input: Invalid argument
    INFO: oracle.sysman.top.oms:stty: standard input: Invalid argument
    INFO: oracle.sysman.top.oms: Enter SYSMAN user password   :
    INFO: oracle.sysman.top.oms:stty: standard input: Invalid argument
    INFO: oracle.sysman.top.oms:stty: standard input: Invalid argument
    INFO: oracle.sysman.top.oms:Verify :
    INFO: oracle.sysman.top.oms:Enter password for: SYSMAN
    INFO: oracle.sysman.top.oms: process_id:1dnhqxd3bexuq
    INFO: oracle.sysman.top.oms:[Initializing the EM RCU Runner, Running the Schema Action, Schema Action Completed Successfully]
    INFO: oracle.sysman.top.oms:The transx command execution is completed with the status 0
    INFO: oracle.sysman.top.oms:process_id:
    INFO: oracle.sysman.top.oms:The plug-in Repository Upgrade has failed its perform method

    I tried also the RepManager command on command line which succeeded and gave exactly the same output.

    I am lost somehow since I can not see any error message I can work with anywhere :/

    Any idea what’s going wrong here?

    best regards,

    Rainer

  10. Steve S. says:

    Thanks for the post. One thing to note is the upgrade document recommends installing the gc_inst outside of the middleware home like in previous 12c versions.

    Cheers,
    Steve

  11. Hemant Patel says:

    My installer was hung at 62% with below messages in the log as well. I checked the database alert log and trace files. I found the Oracle document “Detailed Steps for Troubleshooting ORA-00600 [kdsgrp1] (Doc ID 1492150.1)”.  The “Troubleshooting Steps” 1 and 2 were helpful in resolving my issue. OEM was successfully upgraded from 12.1.0.3 to EM 12.1.0.4. HTH.

    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…
    INFO: oracle.sysman.top.oms:Still Running…

  12. Stephane says:

    Hi Atil,

    Would you please let know if you have the same issue regarding CRC or md5sum check?

    here:

    Oracle Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4)
    for Linux x86-64 :
    -Download em12104_linux64_disk1.zip (2,195,693,096 bytes) (cksum – 4176170445) cksum OK

    -Download em12104_linux64_disk2.zip (1,877,449,643 bytes) (cksum – 3219437597cksum is different :1825566964

    Download em12104_linux64_disk3.zip (2,727,123,784 bytes) (cksum – 2554054536) cksum OK

    I re-downloaded several time em12104_linux64_disk2.zip and also from Edelivery having same problem!

    Stephane

    • Gokhan Atil says:

      Hi Stephane,

      Here’s my checksum result:

      cksum em12104_linux64_disk2.zip
      3219437597

      • Stephane says:

        Atil,
        Thank you for the confirmation. I am having
        a weird problem with this zip file.

        cheer up for your blog!

  13. Stephane says:

    Hi Atil,

     

    I have open a proactive SR with MOS (aka Metalink) regarding my OEM 12 R1.

    I am weighing the Pros and Cons : upgrade or fresh install with 12c R4 (and patch).

    here Oracle support feedback, what do you think about it?

    As discussed earlier please check the following 2 approaches we can try 1) The one currently we are working on + Apply BP1 patches on OMS + Apply BP1 patches on all the agents + Upgrade 12.1.0.1.1 OMS to 12.1.0.3 + Upgrade all agents to 12.1.0.3 Advantages >> This approch will ensure all the historical data about the targets monitored is intact >> All the created jobs users etc will be carried forward to new version Disadvantage >> Takes lot of time to apply BP1 on all the agents >> Needs downtime and incase of failure need to restore back to start again 2) To directly go to 12.1.0.4 Release + Install 12.1.0.4 OMS on a new host + Install agents in parallel with agent (12.1.0.1) on all the targets + Once everything is up and all targets are correctly monitored using + Stop 12.1.0.1 Advantages >> No down time required, the monitoring will be going on inn 12.1.0.1 setup which is untouched >> You can roll back safely without affecting the 12.1.0.1 setup Disadvantages >> You will loose all the historical data >> All the jobs, users, notification rules need to be created manually 

    I am looking to have a second opinion, please let me know what would be your approach ?

    Cheers

    Stephane Berhault

    • Gokhan Atil says:

      Stephane, it depends on you. If historical data is important for you, if you have set up lots of job, incident rules etc, you may prefer upgrade path. Applying BP1 patches could be really challenging (and surely time consuming).

      I don’t need to keep historical data (disk usage stats are very useful but I can live without them). We have less than 100 targets, 2-3 jobs and not-well customized incident handling rules. So I would surely go with a fresh installation for my system.

      • Stephane says:

        Atil,

        Thank you for your quick answer. Like you said applying BP1 is quite challenging. My colleagues in France did it and lost their entire OEM after BP1 failure.

        I am going to do a fresh install with OEM 12c Release 4.
        Have you already apply the patch?

        Patch 18945232: ENTERPRISE MANAGER 12.1.0.4.1

        take care

Trackbacks/Pingbacks

  1. Enterprise Manager 12.1.0.4.0 – Post Upgrade Tasks | Maaz Anjum's Blog - […] With the new release of Enterprise Manager, I upgraded my 12.1.0.3.0 installation successfully using the superb documentation here. It …

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">