This is the step by step document to upgrade OEM12cR4 to OEM13cR2. Mentioned below are some important prerequisites, make sure to you do not skip anyone of them before starting your upgrade.
Prerequisites
· Check the certification matrix to make sure your existing environment is certified for this upgrade. I have already gather the required details.
· EM13cR2 OMS requires Oracle 12.1.0.2 as repository database.
· EM13cR2 agents don’t support Enterprise Linux earlier than version 6.
· Back up your repository database and OMS.
· Another important point to take is the timezone of Repository Database and OMS machine. Since in our case we have both OMS and Database on the same machine so it does not matter. However if the timezone is not same then, Upgrade will fail at ‘Plug-ins Perquisites check’ step.
Certification Matrix
Since our Existing environment is on RHEL Linux 6 so the certification matrix is based on that.
There are few plugin’s which have been obsoleted in new release 13c. Check if there are any obsolete plug-ins in your current system. Un-deploy obsolete plugins if exists both from OMS and Agent before proceeding with upgrade to EM13.2:
- 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)
Upgrade Process.
Step 1: Copy EMKey to the Management Repository.
Note: EMKey is used during upgrade, EM13c will need to access EMKey. { secret key to encrypt password}
$OMS_HOME/bin/emctl config emkey -copy_to_repos |
Step 2: Make sure you have “optimizer_adaptive_features” disabled in your repository database, if not run the below mentioned SQL command.
SQL> alter system set optimizer_adaptive_features=false scope=spfile; |
Step 3: If you have upgraded your database recently, make sure that database compatibility parameter equal to the database version.
SQL> alter system set compatible=”12.1.0.2.0″ scope=spfile |
To make the new changes take effect, please restart your database.
Step 4: Download the OEM13cR2 Setup from Oracle Website. Use the below mentioned URL to download 6 files included in setup.
http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-linux64-3237624.html
Step 5: Copy Software on the installation server.
Make you copy all 5 files in one single folder. NOTE: Please do not unzip any file, EM13c installation doesn’t need you to unzip the files. In EM13c we have “em13200_linux64.bin” as executable we have to run this file as “oracle” user.
Step 6: Run the Setup and enter MOS Details.
The first screen that pops-up will request your credentials for MOS. This is optional not mandatory if you want to receive updates from Oracle you can put your credentials or you can leave it blank as well. “CLICK NEXT” to proceed.
Step 7: Software Update (Optional)
Next step is the software update window, here you will be prompted if you want to check for any new updates available for your new release on which you ware upgrading. Since 13c is released recently so it already contains all latest updates, still if you want to check you can do that by simply providing your MOS credentials as shown below in the screenshot.
Step 8: Pre-requisite Checks
At this step setup performs a check to make sure all the pre-requisites are passed successfully. Make sure you do not have Warning or Failed status for any one of the pre-requisites. Some warnings can be ignored but make you fix the “Failed” pre-requisites before proceeding to the next step as it can FAIL you upgrade later.
Step 9: Installation Types
In this step you will be prompted to select the “Installation Type”, since we are doing the upgrade we will select “Upgrade as existing Enterprise Manager System”. For upgrade there is only one option available “One-System Upgrade”.
Select the radio button as shown in the screenshot below and click on “NEXT”.
Step 10: Installation Details.
In this step you will be prompted to enter the middleware home location for new Oracle Enterprise Manager 13c. Make sure you provide the correct location as this is the directory where all binaries for OEM13c going to be stored.
Step 11: Database Connection Details.
Here you have to provide the connection details for your OMR database. Since we are doing the upgrade of our existing environment, “Connect Descriptor” field is already filled. You have to provide “SYS and SYSMAN” passwords.
EM13c gives as option to disable DDMP during the upgrade.
If you are planning to stop your EM for POST upgrade maintenance then it is recommended to DISABLE DDMP jobs. Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the historical data of your old Enterprise Manager. Depending on how much data stored, it may take same time.
Also, before proceeding to next step make you have you have already backed-up your OMR. Select the check-box and click on “NEXT”.
Before you proceed, make sure you have applied latest PSU on your database to avoid failure during your repository upgrade.
Note: If you haven’t stopped the OMS and agent running on your OMS and OMR server (if OMS and database are on separate machines) , please stop them now. Once OMS and Agent are down then click on NEXT.
Run the below mentioned commands to stop OMS and Agent respectively.
$OMS_HOME/bin/emctl stop oms -all | |
$AGENT_HOME/agent_inst/bin/emctl stop agent |
Although you stop the agents, you may still get a warning about them. Ignore it and continue to upgrade.
Step 12: Database Configuration Check.
When you click on “NEXT” in “Database Connection Details” window in the last step, it performs come checks for the existing database.
You may or may not receive warning depending on your database configuration.
Some of the warnings can be fixed automatically by the installer when you click “YES”, some of them you have to fix manually. In-order to avoid your upgrade to FAIL in middle make sure you fix all the warnings and then click “NEXT”.
Step 13: Plug-in Upgrade, select additional Plug-in’s if you want to install any of them during this installation..
This displays all your existing plug-ins which will be upgraded during this process. Please read thoroughly and click on “NEXT”. Also if you want to install and additional plugin’s in this install, select from the list.
Step 15: Enter Weblogic Details
Please enter the details of Weblogic server for your OEM13c installation. Make sure you choose new location for your OMS instance outside your Middleware home. Also enter your weblogic password.
Step 16: Shared Location Details for BI Publisher
If you already had BI Publisher installed and configured in your existing environment then BI Publisher automatically gets upgraded during upgrade to OEM13c. The checkbox shown in the below screenshot will be checked and grayed out by default only if BI Publisher is already configured.
Step 17: Ports Configuration
Do not make any changes until the mentioned ports are already being used. Accept the default ports and click on NEXT.
Step 18: Review Details
Review the information you entered, and then click the upgrade button to start upgrade process. The time for this upgrade will depend on hardware of your system.
Step 19: Run root.sh script as ROOT user to complete the installation. [root.sh script is located in the middleware home]
Step 20: Final & Final Details
Step 21: POST Upgrade Steps.
Login to your 13c console using the sysman user and perform the POST-upgrade tasks. Navigate to the “upgrade agents” page under the “setup menu” to upgrade your agents.
Regards
ADDKS
Hello,
Great article. I followed the steps exactly but the screen in Step 9 only gives an option to do a new install. No option for Upgrade. Any ideas at all what I might be missing?
Thanks!
LikeLike
Hi Kev,
Seems the setup is not able to detect you existing OMS, can you please send me some more details on my email “sharma.deepak345@gmail.com”
Thanks
Deepak
LikeLike
Are images are not available?
LikeLike
I’ll you the document on your personal, email address. not sure what is causing this issue. i am working on fixing it.
Thanks
Deepak
LikeLike