News
Perth, Australia
+ (61) 417713124
prosolutions@gavinsoorma.com

Upgrading EM12c Release 1 (12.1.0.1) to 12c Release 2 (12.1.0.2)

  • Posted by Gavin Soorma
  • On November 21, 2012
  • 0 Comments
  • 12.1.0.1, 12.1.0.2, 12c, 12c Cloud Control, 12c Release 2, upgrade

I recently upgraded EM 12c version 12.1.0.1 to EM 12c Release 2 (12.1.0.2) on a Linux 64 bit platform. Here are few of the things to keep in mind and some notes I made which may be helpful to others planning the similar upgrade.

The 12c Release 2 software is made up of three zip files. Ensure we have between 10-15 GB free in the stage area where we are going to unzip the files.

em12cr2_linux64_disk1.zip
em12cr2_linux64_disk2.zip
em12cr2_linux64_disk3.zip

The 12.1.0.1 to 12.1.0.2 upgrade is an out of place or what is called a 1 system upgrade.

The 1-system upgrade approach upgrades Enterprise Manager 12c Cloud Control on the same host—upgrades Oracle Management Service (OMS) on the same host and Oracle Management Repository (Management Repository) in the existing database. Since the upgrade happens on the same host, there will be downtime involved in the upgrade

Ensure we have at least 10 GB free on the OMS host for the 12c Release 2 Middleware Home. When we upgrade the 12c management agent we also need to ensure that there is a minimum of 1 GB of free disk space in the 12c Release 1 Agent Home.

 

Before the upgrade

 

Ensure that we have take a backup up the 12c Release 1 OMS (the middleware home and the inventory), the Management Repository, and the Software Library.

Ensure that the tables in the Management Repository do not have any snapshots created.

Log in to the Management Repository and run the following SQL query as SYSMAN user:

SQL> select master, log_table from all_mview_logs where log_owner=’SYSMAN’;

no rows selected

If there are snapshots, then drop them by running the following command as SYSMAN user:

SQL> Drop snapshot log on <master> ;

Copy the emkey from the existing OMS to the existing Management Repository

[oracle@kens-oem-prod bin]$ ./emctl config emkey -copy_to_repos
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
Copyright (c) 1996, 2012 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@kens-oem-prod bin]$

[oracle@kens-oem-prod bin]$ ./emctl status emkey
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
Copyright (c) 1996, 2012 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@kens-oem-prod bin]$

Shut down the Management Agent that monitors the Management Services and Repository target

Launch the 12c R2 installer from the location where we have unzipped the 12.1.0.2 software.

 

 

Enter the location of the 12c R2 Middleware and OMS home – so we have to enter a new location since this is a One-System approach

 

At this point we need to stop the OMS.

$ <OMS_HOME>/bin/emctl stop oms

 

Make a note of the current value of the parameter job_queue_processes as the upgrade resets it to 0. After the upgrade check if the value has changed from 0 to the original pre-upgrade value

 

The deployed plug-ins are upgraded if newer versions are available in the Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2.0) software.

If newer versions are not available in the Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2.0) software, then existing deployed plug-ins are carried over without upgrading them.

 

 

Java Development Kit (JDK) 1.6 v24 and Oracle WebLogic Server 11g Release 1 (10.3.5) are installed by the upgrade process if they are not already available in the Middleware home we specify.

A new Oracle WebLogic domain is created using the existing Administration Server configuration details .

It creates a new Oracle Management Service Instance Base directory (gc_inst) for storing all configuration details related to Oracle Management Service 12c R2.

After the Upgrade

 

The installer does NOT upgrade the existing 12.1.0.1 Management Agent that was installed with the OMS. You must upgrade it (and all other Management Agents) using the Upgrade Agents Console.

The ports used by the earlier release of the Management Agents are carried over to the upgraded Management Agents so we do not need to make any changes to our firewall settings as such.

The 12.1.0.1 agent is compatible with the EM 12c Release 2 OMS. So we can still continue using the 12.1.0.1 management agents with the 12.1.0.2 OMS, but a preferred option would be to upgrade the existing 12c Release 1 agents.

After the upgrade we can see that an additional item has been added to the SetUp menu which is Manage Cloud Control.

From the Manage Cloud Control menu option we select Upgrade Agents.

 

We can now see a list of all our existng 12.1.0.1 agents.

Select the agent we would like to upgrade. In this case Privilege Delefation setting has not been setup for this particular host so we need to run the root.sh manually.

Note that after the upgrade a another directory called 12.1.0.2.0 is created under the AGENT_HOME base/core.

To start and stop the 12c R2 agent we need to ensure that we are now using the emctl executable located under for example:

/u01/app/agent12c/core/12.1.0.2.0/bin

 

[root@kens-oem-prod 12.1.0.2.0]# pwd
/u01/app/em12c/Middleware/agent/core/12.1.0.2.0

[root@kens-oem-prod 12.1.0.2.0]# ./root.sh
Finished product-specific root actions.
/etc exist
Finished product-specific root actions.
[root@kens-oem-prod 12.1.0.2.0]#

[root@kens-orasql-001-dev 12.1.0.2.0]# ./replacebins.sh
Replaced sbin executables

[oracle@kens-oem-prod bin]$ ./emctl status agent

Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
—————————————————————
Agent Version : 12.1.0.2.0
OMS Version : 12.1.0.2.0
Protocol Version : 12.1.0.1.0
Agent Home : /u01/app/em12c/Middleware/agent/agent_inst
Agent Binaries : /u01/app/em12c/Middleware/agent/core/12.1.0.2.0
Agent Process ID : 6725
Parent Process ID : 6673
Agent URL : https://kens-oem-prod.corporateict.domain:3872/emd/main/
Repository URL : https://kens-oem-prod.corporateict.domain:4900/empbs/upload
Started at : 2012-11-13 22:33:30
Started by user : oracle
Last Reload : 2012-11-13 22:33:53
Last successful upload : 2012-11-13 22:36:06
Last attempted upload : 2012-11-13 22:36:06
Total Megabytes of XML files uploaded so far : 0.05
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 13.80%
Collection Status : Collections enabled
Heartbeat Status : Ok
Last attempted heartbeat to OMS : 2012-11-13 22:35:54
Last successful heartbeat to OMS : 2012-11-13 22:35:54
Next scheduled heartbeat to OMS : 2012-11-13 22:36:54

—————————————————————
Agent is Running and Ready

 

0 Comments

Leave Reply

Your email address will not be published. Required fields are marked *