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:
mkdir /u01/setup unzip em12104_linux64_disk1.zip -d /u01/setup unzip em12104_linux64_disk2.zip -d /u01/setup unzip em12104_linux64_disk3.zip -d /u01/setup
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:
$OMS_HOME/bin/emctl config emkey -copy_to_repos_from_file \ -repos_host db-cloud.hostname.com -repos_port 1521 -repos_sid EMREP \ -repos_user sysman -emkey_file $OMS_HOME/sysman/config/emkey.ora Oracle Enterprise Manager Cloud Control 12c Release 3 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. Enter Admin User's Password : Enter Enterprise Manager Root (SYSMAN) Password :
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:
$OMS_HOME/bin/emctl stop oms -all
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:
grant execute on DBMS_RANDOM to DBSNMP; grant execute on DBMS_RANDOM to SYSMAN; revoke execute on DBMS_RANDOM from PUBLIC;
You also need to be sure that there are no invalid packages on repository database:
select owner,object_name, object_type from all_objects
where status='INVALID' and owner in
('SYS','SYSTEM','SYSMAN','MGMT_VIEW', 'DBSNMP','SYSMAN_MDS');
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:
cd /u01/setup ./runInstaller
You enter Oracle support email and password or uncheck “receiving security updates” and click next.
It’s released yesterday so I just skipped checking software updates.
Verify that all prerequisite checks are succeeded. Click next.
I have chosen the one system upgrade. As you can see it detects the correct home of the existing Enterprise Manager installation.
Enter the new middleware home for upgraded Enterprise Manager, and click next to continue.
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.
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.
In this step, you can add additional plugins. Check the ones you want and click next.
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 the inputs and click install if everything looks OK.
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.
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.
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.