Upgrade OEM 12c to 13c
Here, in this article, I’m demonstrating an upgrade from cloud control 12c to 13c on a linux machine. It is required to take a look at the https://docs.oracle.com/cd/E63000_01/EMUPG/preface.htm#EMUPG101 upgrade document before proceeding further and make sure that all the pre-requisites are met.
Few things to consider before you proceed with the upgrade.
1. OMS 13c repository database needs to be on 188.8.131.52 version. So, if the repository database is on a pre-12c release, then you need to upgrade it before upgrading the Cloud control.
2. Cloud control 13c is not supported on OEL/RHEL 5 and so are the 13c agents. You cannot upgrade cloud control 12c on linux machine less than version 6 to 13c.
Environment details is as below:
The environment used here has the Cloud control 12c installed on OEL 6 with the repository database of version 184.108.40.206 which is a non-CDB and has the 12c agents deployed on linux machine of release 6 (OEL 6).
Cloud Control 12c OMS hostname: ora1-2 Repository database version: 220.127.116.11
Make sure that the “COMPATIBLE” parameter on the OMS respository database is set to 18.104.22.168.0.
SYS@omsdb> show parameter compatible NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ compatible string 22.214.171.124.0 noncdb_compatible boolean FALSE SYS@omsdb> SYS@omsdb> show parameter adaptive
If the adaptive optimizer feature (optimizer_adaptive_features) is enabled, then it needs to be disabled on the OMS repository database before upgrading it.
NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ optimizer_adaptive_features boolean TRUE optimizer_adaptive_reporting_only boolean FALSE parallel_adaptive_multi_user boolean TRUE SYS@omsdb> SYS@omsdb> alter system set optimizer_adaptive_features=false; System altered. SYS@omsdb> show parameter adaptive NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ optimizer_adaptive_features boolean FALSE optimizer_adaptive_reporting_only boolean FALSE parallel_adaptive_multi_user boolean TRUE
If there are any invalid objects in the OMS Repository database, then those need to be validated.
Take a backup of the current OMS. Refer the documentation “http://docs.oracle.com/cd/E24628_01/install.121/e24089/ha_backup_recover.htm#EMADV9639” on how to backup the OMS.
Copy the EMKEY from the exsting OMS to the existing management repository. EMKEY is the encryption key which is used by Enterprise Manager to encrypt/decrypt sensitive data such as passwords, preferred credentials.
[oracle@ora1-2 ~]$ echo $OMS_HOME /u02/oms12c/oms [oracle@ora1-2 ~]$ $OMS_HOME/bin/emctl config emkey -copy_to_repos Oracle Enterprise Manager Cloud Control 12c Release 4 Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : The EMKey has been copied to the Management Repository. This operation will cause the EMKey to become unsecure. After the required operation has been completed, secure the EMKey by running "emctl config emkey -remove_from_repos". [oracle@ora1-2 ~]$ $OMS_HOME/bin/emctl status emkey Oracle Enterprise Manager Cloud Control 12c Release 4 Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved. Enter Enterprise Manager Root (SYSMAN) Password : The EMKey is configured properly, but is not secure. Secure the EMKey by running "emctl config emkey -remove_from_repos". [oracle@ora1-2 ~]$
Stop all the components of OMS which includes WebTier, OMS and AdminServer.
[oracle@ora1-2 u03]$ /u02/oms12c/oms/bin/emctl stop oms -all Oracle Enterprise Manager Cloud Control 12c Release 4 Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved. Stopping WebTier... WebTier Successfully Stopped Stopping Oracle Management Server... Oracle Management Server Successfully Stopped AdminServer Successfully Stopped Oracle Management Server is Down [oracle@ora1-2 u03]$
If there is an agent configured for the OMS server, then stop that too.
[oracle@ora1-2 ~]$ /u02/12cagent/core/126.96.36.199.0/bin/emctl stop agent Oracle Enterprise Manager Cloud Control 12c Release 4 Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved. Stopping agent ... stopped.
Copy all the EM13c software parts into a staging directory. I have them copied into directory “/u03/em13csoftware”.
[oracle@ora1-2 u03]$ ls -lrt /u03/em13csoftware | grep -i "em" -rw-r--r--. 1 oracle oinstall 1315250699 Jun 11 15:54 em13100_linux64-2.zip -rw-r--r--. 1 oracle oinstall 2145473190 Jun 11 16:05 em13100_linux64-3.zip -rw-r--r--. 1 oracle oinstall 2141357330 Jun 11 16:15 em13100_linux64-4.zip -rw-r--r--. 1 oracle oinstall 331590923 Jun 11 16:16 em13100_linux64-5.zip -rw-r--r--. 1 oracle oinstall 841114290 Jun 11 16:20 em13100_linux64.bin
Set the executable permission on the file “em13100_linux64.bin” which is the executable binary file.
Execute the em13100_linux64.bin file to invoke the 13c GUI component.
[oracle@ora1-2 em13csoftware]$ chmod +x em13100_linux64.bin [oracle@ora1-2 em13csoftware]$ ls -lrt em13100_linux64.bin -rwxr-xr-x. 1 oracle oinstall 841114290 Jun 11 16:20 em13100_linux64.bin
[oracle@ora1-2 em13csoftware]$ ./em13100_linux64.bin 0%...............................................................100% Launcher log file is /tmp/OraInstall2016-06-12_11-28-00AM/launcher2016-06-12_11-28-00AM.log. Starting Oracle Universal Installer Checking if CPU speed is above 300 MHz. Actual 3180.718 MHz Passed Checking monitor: must be configured to display at least 256 colors. Actual 16777216 Passed Checking swap space: must be greater than 512 MB. Actual 10236 MB Passed Checking if this platform requires a 64-bit JVM. Actual 64 Passed (64-bit not required) Checking temp space: must be greater than 300 MB. Actual 22122 MB Passed Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2016-06-12_11-28-00AM ====Prereq Config Location main=== /tmp/OraInstall2016-06-12_11-28-00AM/stage/prereq EMGCInstaller args -scratchPath EMGCInstaller args /tmp/OraInstall2016-06-12_11-28-00AM EMGCInstaller args -sourceType EMGCInstaller args network EMGCInstaller args -timestamp EMGCInstaller args 2016-06-12_11-28-00AM EMGCInstaller args -paramFile EMGCInstaller args /tmp/sfx_Wr9ToQ/Disk1/install/linux64/oraparam.ini EMGCInstaller args -nocleanUpOnExit DiskLoc inside SourceLoc/u03/em13csoftware EMFileLoc:/tmp/OraInstall2016-06-12_11-28-00AM/oui/em/ ScratchPathValue :/tmp/OraInstall2016-06-12_11-28-00AM
Provide the mail ID followed by password if you wish to receive the support updates and click NEXT.
I would not like to search for the software update and hence chosing the SKIP option and clicking NEXT.
Run the pre-requisite checks and if any discrepancy, then fix them before proceeding further.
Since we are upgrading to 13c EM, select the “Upgrade an existing Enterprise Manager system” option and under this select the “One-System Upgrade” by selecting the 12c EM home.
Enter the middleware home location. I’m installing 13c under the location “/u02/13c”.
Oracle automatically captures the connect description details for the repository database. Provide the SYS and SYSMAN password.
Also confirm that the Management Repository is backed up by checking the box. If you wish to stop the Enterprise Manager for post-upgradation maintenance, then check the “Disable DDMP jobs” and click NEXT button. In that case, the post-upgradation maintenance activity needs to be carried out manually. DDMP is Deferred Data Migration which is to migrate the format of the data from the previous release Enterprise Manager to the format used in 13c.
If there are any pre-requisite checks at OMS repository database level failed, then review the recommendations provided. Click YES, if you would like the installer to take necessary actions else NO for a manual fix.
Review the information on the plugins that will be upgraded and click Next.
Select the additional plugins that you want to deploy and click Next.
Fill in the WebLogic server details by specifying the password for the Weblogic User Name and also providing the OMS Instance Base Location.
If you want to configure and enable BI publisher, you can select it here, else click Next.
Review the default ports listed and click Next.
Review the list of information provided and click on Upgrade to begin the upgrade.
Run the “allroot.sh” script as ROOT user when prompted.
[root@ora1-2 ~]# /u02/13c/allroot.sh Starting to execute allroot.sh ......... Starting to execute /u02/13c/root.sh ...... /etc exist /u02/13c Finished execution of /u02/13c/root.sh ......
Review and note down the URLs
Login to the EM 13c through the browser with SYSMAN as the user and the password which was being used previously.
Accept the License Agreement to proceed further.
Review the OEM 13c summary page.
If you had disabled DDMP jobs while upgrading EM, you should consider to carry out the post upgrade tasks.
Login to the EM 13c through the browser. On the summary page, click SETUP. Under this, select “Manage Cloud Control” and then the “Post Upgrade Tasks” option.
Click the “Start” option to start the post upgrade tasks.
Review the status of the post upgrade tasks.
Upgrading a 12c agent to 13c:
As said previously, 13c agents can be configured on a Linux target machine whose version is not below 6. So, if you already have the 12c agent installed on a Linux machine which is less than version 6, then this cannot be considered to upgrade to 13c agent. But, you can still use the old agent (12c agent) with EM 13c.
For the purpose of this demo, I had a 12c agent installed on my OMS host which is of version 6. So, I’m considering to upgrade this agent to 13c.
Agent Host name: ora1-2 Agent Version: 12c Agent Host Flavor: OEL 6
Login to the EM 13c through the browser. On the summary page, click SETUP. Under this, select “Manage Cloud Control” and then the “Upgrade Agents” option.
Click on the Add option under the “Agents for upgrade” option to view the list of agents that can be upgraded to 13c.
Select the agent you desire to upgrade and click OK.
Review the information and click on Submit to upgrade the agent.
After the agent upgrade, review the status manually.
12c agent under location:
[oracle@ora1-2 bin]$ cd /u02/12cagent/ [oracle@ora1-2 12cagent]$ ls -lrt total 32 drwxr-xr-x. 3 oracle oinstall 4096 May 24 2014 core drwxr-xr-x. 12 oracle oinstall 4096 Jun 7 13:24 plugins -rw-rw-r--. 1 oracle oinstall 179 Jun 13 20:30 agentimage.properties -rw-r--r--. 1 oracle oinstall 693 Jun 13 20:35 agentInstall.rsp drwxr-xr-x. 3 oracle oinstall 4096 Jun 13 20:35 backup_agtup drwxr-xr-x. 5 oracle oinstall 4096 Jun 13 20:40 sbin drwxr-xr-x. 9 oracle oinstall 4096 Jun 13 20:49 agent_inst drwxr-xr-x. 28 oracle oinstall 4096 Jun 13 20:50 agent_188.8.131.52.0
Agent upgrade installer creates a new directory called “agent_184.108.40.206.0” under the previous 12c agent directory.
[oracle@ora1-2 12cagent]$ cd agent_220.127.116.11.0/bin/ [oracle@ora1-2 bin]$ ./emctl status agent Oracle Enterprise Manager Cloud Control 13c Release 1 Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved. --------------------------------------------------------------- Agent Version : 18.104.22.168.0 OMS Version : 22.214.171.124.0 Protocol Version : 126.96.36.199.0 Agent Home : /u02/12cagent/agent_inst Agent Log Directory : /u02/12cagent/agent_inst/sysman/log Agent Binaries : /u02/12cagent/agent_188.8.131.52.0 Core JAR Location : /u02/12cagent/agent_184.108.40.206.0/jlib Agent Process ID : 28044 Parent Process ID : 27922 Agent URL : https://ora1-2.mydomain:3872/emd/main/ Local Agent URL in NAT : https://ora1-2.mydomain:3872/emd/main/ Repository URL : https://ora1-2.mydomain:4903/empbs/upload Started at : 2016-06-13 20:40:14 Started by user : oracle Operating System : Linux version 2.6.32-71.el6.x86_64 (amd64) Number of Targets : 36 Last Reload : 2016-06-13 20:43:33 Last successful upload : 2016-06-13 20:50:53 Last attempted upload : 2016-06-13 20:50:53 Total Megabytes of XML files uploaded so far : 0.29 Number of XML files pending upload : 0 Size of XML files pending upload(MB) : 0 Available disk space on upload filesystem : 30.18% Collection Status : Collections enabled Heartbeat Status : Ok Last attempted heartbeat to OMS : 2016-06-13 20:50:38 Last successful heartbeat to OMS : 2016-06-13 20:50:38 Next scheduled heartbeat to OMS : 2016-06-13 20:51:39 --------------------------------------------------------------- Agent is Running and Ready [oracle@ora1-2 bin]$
© Shivananda Rao P, 2012 to 2017. Unauthorized use and/or duplication of this material without express and written permission from this blog’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Shivananda Rao and http://www.shivanandarao-oracle.com with appropriate and specific direction to the original content.
The views expressed here are my own and do not necessarily reflect the views of any other individual, business entity, or organisation. The views expressed by visitors on this blog are theirs solely and may not reflect mine