Let’s have a quick introduction of Upgrade in Oracle. As we go in depth of this article we have mentioned about the steps of an upgrade OEM from 12cR5 to 13cR2.

Thanks to my fellow DBA Kellyn Pot’Vin-Gorman who gave me idea to write on OEM 13c.

Day by day technologies get change and advanced technology come. Change plays an important role in human life. In our school time, we have learned about the  Darwinian theory which explains the importance of change in the world.

In the same manner in the world of technology, we have also seen that Oracle database’s journey started from the First release: June 1992 (7.0) and still going on. Here we have a technical definition on upgradation . The upgrade is the process of replacing our existing software with a newer version of the same product. For example, replacing Oracle 9i release to Oracle 10g release. Upgrading our applications usually do not require special tools. Our existing reports should look and behave the same in both products. However, sometimes minor changes may be seen in a product. Upgradation is done at the Software level.

There are some reasons why do we need to upgrade our database which is mention below:-

  • Updated hardware and operating systems.
  • Security patches.
  • Marketplace relevance
  • Easier future upgrades.
  • Data protection.
  • Database consolidation
  • Cloud migration
  • Application vendor suppor

 

Oracle OEM 13c has been introduced with enhanced GUI and with a lot of new features.

OEM(Oracle Enterprise Manager) is pictorial representation of system, its status, downtime impact with lot of features to enhance the usability of Database. OEM 13c maximize support integration for Oracle Engineered Machine Exadata. OEM makes daily jobs easier and faster.
If we have Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5), 12c Release 4 (12.1.0.4) or 12c Release 3 (12.1.0.3) then Oracle recommends that you upgrade it to 13c Release 1 to benefit from all the new features.

Supported environment for upgrading to OEM 13c Cloud control:

  1. OEM 12c Release 5 (12.1.0.5)
  2. OEM 12c Release 4 (12.1.0.4)
  3. OEM 12c Release 3 (12.1.0.3) without BI Publisher. If BI publisher is configured then we need to upgrade to 12c Release 4 or 5

Supported OMR database version

  1. Oracle 12.1.0.2.0

Supported Managed Targets

  1. Oracle 12.1.0.2.0
  2. Oracle 12.1.0.1.0
  3. Oracle 11.2.0.4.0
  4. Oracle 11.2.0.3.0
  5. Oracle 11.2.0.2.0
  6. Oracle 11.2.0.1.0
  7. Oracle 11.1.0.7.0
  8. Oracle 10.2.0.5.0
  9. Oracle 10.2.0.4.0
  10. Oracle 10.2.0.5.0
  11. Oracle 10.2.0.4.0
  12. Oracle 10.1.0.5.0

Supported Agent version

  1. Agent 13.1.0.0.0
  2. Agent 12.1.0.5.0
  3. Agent 12.1.0.4.0
  4. Agent 12.1.0.3.0

Restriction

  1. Pre-installed JDK or Oracle Weblogic is not supported from 13c Release 1 onward.
  2. Dedicated Oracle Weblogic Server 12c Release 1 is required.
  3. The central agent (in other words, the Management Agent installed with the OMS) is not upgraded by default. You must upgrade it using the Agent Upgrade Console available in the Enterprise Manager Cloud Control Console after upgrading the OMS.
  4. After upgrading the OMS, you must upgrade the Management Agent separately using the Agent Upgrade Console. Agent Upgrade Console is a GUI console that you see in the Enterprise Manager Cloud Control Console after you upgrade the OMS.
  5. To access the Agent Upgrade Console, from the Setup menu, click Manage Cloud Control, then select Upgrade Agents.

Below are the steps for upgrading OEM 12c (12.1.0.5) to OEM 13c (13.2.0.1)

Current OEM version – 12.1.0.5

Repository DB version – 12.1.0.2

Upgrade OEM version – 13.2.0.0

PREREQUISITES:

  1. OMS 13c repository database needs to be on 12.1.0.2 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.
  3. Apply the latest PSU patch to the rdbms home of repository database.
  4. Make sure that database compatibility parameter equal to the database version
  5. Run utlrp.sql to make sure no invalid objects.

6. Set optimizer_adaptive_features to FALSE;

7. Verify that all the OMS have the same version of Plugins deployed. (Run from SYSMAN)

8. Check for stuck jobs:

9. Remove obsolete plugins:

Below are the obsolete in 13c : ( if any is installed , please remove them )

  • 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)

Note: Below are the steps for removing obsolete plugins:

Go to SETUP -> EXTENSIBILITY -> PLUGINS

SELECT THE PLUGIN , that needs to be removed and Undeploy.

UNDEPLOY FROM -> MANAGEMENT SERVERS

 

10. Grant below privileges on repository database:

11. Stop the OMS and the agent on OMS server:

12. Ensure that you do not have any login or logoff triggers set in the Oracle Database that houses the Oracle Management Repository

Now we can start the Upgrade process for OEM 12cR5 to 13cR2

Download the Oracle OEM 13c software to your server.

Click Here to Download

Note: Don’t unzip them

Execute the .bin file from,( to invoke GUI)

Enter A NEW OMS HOME LOCATION:

In the end root.sh script will pop up. Please run the same as the root user.

With this OMS upgrade has been completed. Let’s open the URL.

 

UPGRADE AGENTS:

Once OMS upgrade is done, we can upgrade the agents to 13.1 version.  However, you still continue using the same old 12c plug-ins.

SETUP -> MANAGE CLOUD CONTROL -> UPGRADE AGENT

Now click on NOT UPGRADABLE AGENTS, to check which agents cant be upgraded directly.

Once the update is done, Follow the same process of upgrading agents.

Thank you for giving your valuable time to read the above information.

Source

For More Detail , You can join us follow:

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

About The Author

Leave a Reply