Upgrade 11G Oracle Managed Server to 12C using one system method.

1. OMS Upgrade from 11.1 to 12.1
By Guduru
1 | P a g e
In this document we will dive through about Oracle Management Server Upgrade from 11.1 to 12.1.
Index:
- Upgrade Approaches
- Comparison between different approach types
- Patches
- Core Plugins
- OMS window
- OMS upgrade
- Completed

2. OMS Upgrade from 11.1 to 12.1
By Guduru
2 | P a g e
Upgrade Approaches:
As per Oracle, there are three different approaches to upgrade existing OMS
(Oracle Managed Server).
1) 1- System Upgrade Approach:
- Upgrade will happen on the same host where earlier release of OEM is running
- This approach also upgrades the Oracle Management Repository in the existing
database.
- There will be reasonable downtime involved since the upgrade happens in the same host.
2) 2-System Upgrade Approach
- This approach enables us to install EMC on a different host
- This approach does not upgrade the Management Repository in the existing database
- but upgrades the one in the backed-up database, thus enabling two Enterprise Manager
systems to exist.
- As we will have both (old/new) Enterprise Managers coexist, so there is no downtime or
near zero downtime involved.
3) 1-System Upgrade Approach on a different host
- This approach enables you to install Enterprise Manager Cloud Control on a host
different from where the existing Enterprise Manager is running.
- This approach is similar to the 2-System upgrade approach, but unlike the 2-System upgrade
approach, this approach upgrades the Management Repository in the existing database
itself. Since only one Enterprise Manager system exists at any point, there is a reasonable
downtime involved.
Note:
- Regardless of the approach you choose, the upgrade operation is always an out-of-place
upgrade where you see new Oracle homes of Oracle Management Service (OMS) and Oracle
Management
- Agent (Management Agent). As a best practice, back up your old and new homes regularly.
- You can upgrade any Management Agent on any platform as long as the Oracle
Management Agent 12c software for that platform is available.
Comparison between different approach types:
Now the question is which type of upgrade one should opt? So, let us have a comparation between 3
approaches.
1-System Upgrade Approach 2-System Upgrade Approach 1-System Upgrade Approach
on Different Host
Involves predeployment and
switch over of Management
Agents prior to upgrading the
OMS and the Management
Repository, unlike the
traditional approach that
focussed on upgrading only
the OMS and the Management
Repository.
Resembles fresh installation. Has the same impact as 1-
system upgrade approach, but
with a different host for
Enterprise Manager Cloud
Control 12c Release 5
(12.1.0.5).
Requires a reasonable
downtime.
Essentially, the downtime lasts
from the time you start
Requires minimum or zero
downtime
Requires a reasonable
downtime.
Essentially, the downtime lasts
from the time you start

3. OMS Upgrade from 11.1 to 12.1
By Guduru
3 | P a g e
switching over the
Management Agents till the
time you upgrade the OMS.
switching over the
Management Agents till the
time you install the OMS.
Upgrades to Enterprise
Manager Cloud Control on the
same host where your earlier
release of Enterprise Manager
is running.
Installs Enterprise Manager
Cloud Control on a host that is
different from the host where
your existing Enterprise
Manager system is running.
Installs Enterprise Manager
Cloud Control on a host
different from where the
existing Enterprise Manager is
running but upgrades the
Management Repository in the
existing database itself.
Does not require an additional
hardware resource because it
upgrades on the same host.
Requires an additional
hardware resource because it
installs on a different host.
Requires an additional
hardware resource because it
installs on a different host.
Existing Enterprise Manager
system must be shut down so
that the configuration
information can be copied and
carried over to the upgraded
Enterprise Manager system.
Existing Enterprise Manager
system can continue to run
until you switch over all your
earlier releases of
Management Agents to the
newly upgraded environment.
Existing Enterprise Manager
system must be shut down so
that the configuration
information can be copied and
carried over to the new system
Management Agents must be
deployed and configured
before upgrading the OMS and
the Management Repository.
Management Agents can be
deployed and configured
before or after upgrading the
OMS and the Management
Repository.
Management Agents must be
deployed and configured
before upgrading the OMS and
the Management Repository.
Management Agents can be
deployed and configured in an
incremental or phased
manner, that is, in groups.
Management Agents can be
deployed and configured in an
incremental or phased
manner, that is, in groups.
Management Agents can be
deployed in an incremental or
phased manner, that is, in
groups.
Management Agents must be
switched over before ----
upgrading the OMS and the
Management Repository.
Management Agents must be
switched over after upgrading
the OMS and the Management
Repository.
Management Agents must be
switched over before
upgrading the OMS and the
Management Repository.
Upgrades the Management
Repository in the existing,
certified database.
Upgrades the Management
Repository in the backed-up
database. Therefore, as a
prerequisite, you are required
to back up your existing Oracle
Database.
Upgrades the Management
Repository in the existing,
certified database.
Requires no changes to the
ports and firewall settings. The
upgraded Management Agents
and the OMS use the same
ports used earlier.
Requires some changes to the
ports and firewall settings. The
upgraded Management Agents
use the same ports used
earlier. However, the
Management Agent and the
OMS installed on the remote
host might use new ports.
In a multi-OMS environment, if
you have a Server Load
Balancer (SLB), then you can
either open up new ports for
Requires some changes to the
ports and firewall settings. The
upgraded Management Agents
use the same ports used
earlier. However, the
Management Agent and the
OMS installed on the remote
host might use new ports.
In a multi-OMS environment, if
you have a Server Load
Balancer (SLB), then you can
either open up new ports for

4. OMS Upgrade from 11.1 to 12.1
By Guduru
4 | P a g e
the new Management Agent
and the OMS in the same SLB,
or configure a completely new
SLB for them.
the new Management Agent
and the OMS in the same SLB,
or configure a completely new
SLB for them.
All deployment procedures
must be finished before the
upgrade is started. Otherwise,
the scheduled procedures will
be cancelled, and you will have
to re-create them.
All deployment procedures
must be finished before the
upgrade is started. Otherwise,
the scheduled procedures will
be cancelled, and you will have
to re-create them.
All deployment procedures
must be finished before the
upgrade is started. Otherwise,
the scheduled procedures will
be cancelled, and you will have
to re-create them.
Running jobs will be aborted at
the start of the downtime.
Running jobs will continue to
run on the existing Enterprise
Manager system after the start
of the backup. In Enterprise
Manager Cloud Control, these
jobs will appear to be aborted
or failed.
Running jobs will be aborted at
the start of the downtime.
Scheduled jobs will run after
the downtime is over if their
grace period allows them.
Otherwise, they will be
skipped.
Scheduled jobs will run on the
existing Enterprise Manager
system from the time of the
backup until the point where
the Management Agent for
that target is migrated to
Enterprise Manager Cloud
Control. Once the
Management Agent is
migrated, the jobs will run in
Enterprise Manager Cloud
Control.
Scheduled jobs will run after
the downtime is over if their
grace period allows them.
Otherwise, they will be
skipped.
Repeating jobs will run at their
next scheduled time after the
downtime. If repeating jobs
fall within the downtime, they
may be skipped.
Repeating jobs will continue to
run according to their schedule
in the existing Enterprise
Manage system. Once the
Management Agent is
migrated, subsequent runs will
be in Enterprise Manager
Cloud Control.
Repeating jobs will run at their
next scheduled time after the
downtime. If repeating jobs
fall within the downtime, they
may be skipped.
Note:
Jobs run either in the existing Enterprise Manager system or in Enterprise Manager Cloud Control,
and not on both systems. The true status of a job must be viewed only on the system where it
actually ran. For more information. Also, job executions with multiple targets will not run on either
system unless all Management Agents for all targets are migrated at the same time.
Patches:
In oracle documents the pre-upgrade patch mentioned as 10044087 but this is now replaced with
patch 13503844. So, if the download link prompt this patch it is fine. Follow the readme.txt in this
patch bundle to install it.

5. OMS Upgrade from 11.1 to 12.1
By Guduru
5 | P a g e
One of the pre-requisites for this patch is to have PSU1 10065631.
Once PSU patch/s applied then we need to apply pre-upgrade console patch 13503844
13503844]$ /opt/app/oracle/Middleware/oms11g/OPatch/opatch apply
Oracle Interim Patch Installer version 11.1.0.9.4
Copyright (c) 2011, Oracle Corporation. All rights reserved.
Oracle Home : /opt/app/oracle/Middleware/oms11g
Central Inventory : /opt/app/oraInventory
from : /opt/app/oracle/Middleware/oms11g/oraInst.loc
OPatch version : 11.1.0.9.4
OUI version : 11.1.0.8.0
Log file location :
/opt/app/oracle/Middleware/oms11g/cfgtoollogs/opatch/13503844__07_2018_10_56_45/apply20
uly18-07-17 _10-56-44AM_1.log
OPatch detects the Middleware Home as "/opt/app/oracle/Middleware"
OPatch will do the following:
[Oracle Home discovery] : Configure and Validate Oracle Home info.
[Prerequisite for apply] : Invoke prerequisites to see if patch can be applied.
[Patch conflict detection for apply patch] : Check if any conflict with already installed patches in
Oracle Home.
Applying interim patch '13503844' to OH '/opt/app/oracle/Middleware/oms11g'
Verifying environment and performing prerequisite checks...
To continue, OPatch will do the following:
[Back up for restore] : Back up 68 files for Oracle Home restore in case of patching error.
[Back up for rollback] : Back up 39 files for future patch rollback.
[Patch Oracle Home for apply] : Copy 39 file(s) to Oracle Home;
Archive 4 jar file(s) with 254 class file(s).
[Update inventory for apply] : Modify the inventory to record patch [13503844].
Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit http://www.oracle.com/support/policies.html for details.
Email address/User Name:
You have not provided an email address for notification of security issues.
Do you wish to remain uninformed of security issues ([Y]es, [N]o) [N]: y
Backing up files...
Patching component oracle.sysman.oms.core, 11.1.0.1.0...
Verifying the update...

6. OMS Upgrade from 11.1 to 12.1
By Guduru
6 | P a g e
Patch 13503844 successfully applied
Log file location:
/opt/app/oracle/Middleware/oms11g/cfgtoollogs/opatch/13503844_July_07_2018_10_56_45/appl
y2018-07-17 _10-56-44AM_1.log
OPatch succeeded.
13503844]$ $ORACLE_HOME/bin/rcuJDBCEngine sys/gridb@192.168.0.76:1521:gridb JDBC_SCRIPT
$ORACLE_HOME/sysman/preupgc/puc_dblink_pkgdef.sql
Completed SQL script execution normally.
1 scripts were processed
13503844]$ $ORACLE_HOME/bin/rcuJDBCEngine sys/gridb@192.168.0.76:1521:gridb JDBC_SCRIPT
$ORACLE_HOME/sysman/preupgc/puc_dblink_pkgbody.sql
Completed SQL script execution normally.
1 scripts were processed
13503844]$ $ORACLE_HOME/bin/rcuJDBCEngine sysman/gridb321@192.168.0.76:1521:gridb
JDBC_SCRIPT $ORACLE_HOME/sysman/preupgc/pre_upg_console.sql
l_target_guids.COUNT : 4
oracle.sysman.beacon SMPADDON 11.1.0.1.0 Oracle Beacon Plugin
oracle.sysman.emrep SMPADDON 11.1.0.1.0 Oracle Management And Repository Plugin
oracle.sysman.oh SMPADDON 11.1.0.1.0 Oracle OracleHome
oracle.sysman.csa SMPADDON 11.1.0.1.0 Oracle Client System Analyzer
oracle.sysman.db SMPADDON 11.1.0.1.0 Oracle Database Plugin
oracle.sysman.emas SMPADDON 11.1.0.1.0 Oracle Fusion Middleware Plugin
oracle.sysman.empa ADDON 11.1.0.1.0 Oracle Siebel Plugin
oracle.sysman.vt ADDON 11.1.0.1.0 Oracle Virtualization Plugin
oracle.fmw.bhv ADDON 11.1.0.1.0 Oracle Beehive Plugin
Completed SQL script execution normally.
24 scripts were processed
When patch is succeeded, we should be able to see a link under the deployments tab,
under upgrade as highlighted.

7. OMS Upgrade from 11.1 to 12.1
By Guduru
7 | P a g e
This link will navigation into upgrade console window, which has option to choose the type of
upgrade, agent upgrade status and over view of the steps in the upgrade.
Below is the screenshot of the upgrade console page.
Select the upgrade approach and click on the overview link. The overview link on this page provides
information about each upgrade approach. Below is screenshot of 1-system on same host .

8. OMS Upgrade from 11.1 to 12.1
By Guduru
8 | P a g e
Core Plugins:
Download agent core plugins & copy these files into a directory in the host.
Below is the list of downloaded plugins.
-rw-r--r-- 1 oracle oinstall 495016 Feb 9 11:58 12.1.0.1.0_oracle.sysman.oh_2000_0.opar
-rw-r--r-- 1 oracle oinstall 499849 Feb 9 11:58 12.1.0.1.0_oracle.sysman.csa_2000_0.opar
-rw-r--r-- 1 oracle oinstall 297231 Feb 9 11:58 12.1.0.1.0_oracle.sysman.emrep_2000_0.opar
-rw-r--r-- 1 oracle oinstall 3925371 Feb 9 11:58 12.1.0.1.0_oracle.em.soee_2000_0.opar
-rw-r--r-- 1 oracle oinstall 230699506 Feb 9 11:59 12.1.0.1.0_AgentCore_226.zip
-rw-r--r-- 1 oracle oinstall 223979520 Feb 9 11:59 12.1.0.1.0_AgentCore_46.zip
-rw-r--r-- 1 oracle oinstall 621251038 Feb 9 11:59 12.1.0.1.0_oracle.sysman.db_2000_0.opar
-rw-r--r-- 1 oracle oinstall 106452968 Feb 9 12:08 12.1.0.1.0_oracle.sysman.beacon_2000_0.opar
-rw-r--r-- 1 oracle oinstall 440206388 Feb 9 12:17 12.1.0.1.0_oracle.sysman.emas_2000_0.opar
With out above plugins being discovered agents will be shown as unable to upgrade.
Below snippet show the current state of agent upgradeability as no plugin or agent software is
validated.
*provide the location of the plugins were downloaded and click on validate.
When the plugins and agent software is validated all the agents become upgradable. Resolve any
issues, missing plugins and re-validate before continuing. Below is the snippet for more details.

9. OMS Upgrade from 11.1 to 12.1
By Guduru
9 | P a g e
1. Clicking on the upgradable link next to each green pie chart will show the upgradeability of
each agent and each target.
2. Once all agents are upgradeable click on "Agent Upgrade Status" link which is under "Other
Links" in upgrade console page .At this stage all the status should be not started.
3. Click deploy and configure agents button. Multiple agents could be selected to be deployed
and configured but this require host and agent credentials, if these are not set then oracle
and root credentials must be same for all hosts. Agents are deployed and configured one at
a time.
4. Select the host deploy and configure the new agent.
5. Click on the deploy and configure button will take you to a window to specify the new
directory for agent host credentials.
6. Click continue and give root user credentials.
7. When the submit button is clicked, it will start the deploy and configure job.
8. Once the agent deployment is successful run agent readiness check.
9. At the end agent readiness check Health Check Status column, will see "report pending
verification". This requires manually verifying it is ok to proceed. Click on view and verify
health check report button and inspect the report and confirm if it is error free.
10. Agent is ready for the switch.
Downtime Window:
This where the down time starts. When switch agent is started the current 11g agent will be stopped
and disabled. The 12c new agent will be started but cannot report to 11g OMS until it's upgrade.
Therefore, until the OMS is upgraded there will be no monitoring.
When all the agents are switched to 12c agents and monitoring has effectively halted until OMS is
upgraded. Status of the new agent states its up and ready but still unable to communicate with
OMS.
./emctl status agent
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 12.1.0.1.0

10. OMS Upgrade from 11.1 to 12.1
By Guduru
10 | P a g e
OMS Version : (unknown)
Protocol Version : 12.1.0.1.0
Agent Home : /opt/app/oracle/agent/agent12g/agent_inst
Agent Binaries : /opt/app/oracle/agent/agent12g/core/12.1.0.1.0
Agent Process ID : 4072
Parent Process ID : 3935
Agent URL : https://guduru1. .net:3872/emd/main
Repository URL : https://guduru. .net:4900/empbs/upload
Started at : 2018-07-17 16:26:48
Started by user : oracle
Last Reload : (none)
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0
Number of XML files pending upload : 82
Size of XML files pending upload(MB) : 0.54
Available disk space on upload filesystem : 13.59%
Collection Status : Collections enabled
Last attempted heartbeat to OMS : 2018-07-17 16:32:58
Last successful heartbeat to OMS : (none)
---------------------------------------------------------------
Agent is Running and Ready
Let us go ahead with OMS upgrade immediately to minimise the unmonitored time of agents
shutdown the OMS with
emctl stop oms
when OUI opened, please fill the details.
- My Oracle support details  Provide email if you want to receive security updates
- Software updates  skip
- Prerequisites check  Here Oracle verifies if your system meets minimum requirements for
installing and configuring OEM
- Install types  As we planned to upgrade existing system, selected Upgrade an existing
enterprise management system & selected one system Upgrade. Also, select ORACLE HOME
& Middleware location.
- Database connection details  provide connection string, sys password & sysman password
- Select plug-ins  I opted for first 5 options provided as per my need
- Extend WebLogic server domain  admin server host – Guduru.myoraclesultions.net
 Admin server port – 7101
 WebLogic username – weblogic
 WebLogic password - ********
 OMS instance base location -
/opt/app/oracle/middleware12 (browse the path)
- Review  review the information provided and click install to begin the installation process
- System will pop-out a window asking to run the allroot.sh  Open a new window as root
and run the script
# /opt/app/oracle/Middleware12/oms/allroot.sh
-
Starting to execute allroot.sh .........

11. OMS Upgrade from 11.1 to 12.1
By Guduru
11 | P a g e
Starting to execute /opt/app/oracle/Middleware12/oms/root.sh ......
Running Oracle 11g root.sh script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /opt/app/oracle/Middleware12/oms
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)
[n]:
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root.sh script.
Now product-specific root actions will be performed.
/etc exist
/opt/app/oracle/Middleware12/oms
Finished execution of /opt/app/oracle/Middleware12/oms/root.sh ....
- Click on close to finish the process
At the end of the upgrade the 12c agents switched earlier can now communicate with the OMS.
Checking the status of the agents shows
emctl status agent
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
---------------------------------------------------------------
Agent Version : 12.1.0.1.0
OMS Version : 12.1.0.1.0
Protocol Version : 12.1.0.1.0
Agent Home : /opt/app/oracle/grid_agent/agent12g/agent_inst
Agent Binaries : /opt/app/oracle/grid_agent/agent12g/core/12.1.0.1.0
Agent Process ID : 4072
Parent Process ID : 3935
Agent URL : https://guduru1. .net:3872/emd/main
Repository URL : https://guduru. .net:4900/empbs/upload
Started at : 2018-07-17 16:26:48
Started by user : oracle
Last Reload : (none)
Last successful upload : 2018-07-17 12:59:01
Last attempted upload : 2018-07-17 12:59:01
Total Megabytes of XML files uploaded so far : 2.44
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 13.31%
Collection Status : Collections enabled

12. OMS Upgrade from 11.1 to 12.1
By Guduru
12 | P a g e
Last attempted heartbeat to OMS : 2018-07-17 13:02:12
Last successful heartbeat to OMS : 2018-07-17 13:02:12
---------------------------------------------------------------
Agent is Running and Ready
Status from old agent shows it's running but not communicating with OMS anymore
emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent is Running but Not Ready
*Please de-install the older OEM.
Completed !!.