EM12cR2 upgrade to EM12cR5

I followed the steps below:

# backup the rule sets
 To make a copy, from the Setup menu, select Incidents, then select Incident Rules.
 On the Incident Rules - All Enterprise Rules page, in the table, select the out-of-box rule set you want to copy.
 Then, from the Actions menu, select Create Like Rule Set. In the Create Like Rule Set page, provide the required details and click Save.
# Back up the OMS (the middleware home and the inventory)
 [oracle@oem bin]$ /u01/app/oracle/product/11.2/OPatch/opatch lsinventory
 Invoking OPatch
Oracle Interim Patch Installer version
 Copyright (c) 2009, Oracle Corporation. All rights reserved.
Oracle Home : /u01/app/oracle/product/11.2
 Central Inventory : /u01/app/oracle/oraInventory
 from : /etc/oraInst.loc
 OPatch version :
 OUI version :
 OUI location : /u01/app/oracle/product/11.2/oui
 Log file location : /u01/app/oracle/product/11.2/cfgtoollogs/opatch/opatch2015-11-18_10-09-47AM.log
Patch history file: /u01/app/oracle/product/11.2/cfgtoollogs/opatch/opatch_history.txt
Lsinventory Output file location : /u01/app/oracle/product/11.2/cfgtoollogs/opatch/lsinv/lsinventory2015-11-18_10-09-47AM.txt
 Installed Top-level Products (1):
Oracle Database 11g
 There are 1 products installed in this Oracle Home.
There are no Interim patches installed in this Oracle Home.
OPatch succeeded.
[oracle@oem u01]$ locate oraInst.loc | grep oms
 [oracle@oem u01]$ cat /u01/app/oracle/product/12.1.0/middleware/oms/oraInst.loc
[oracle@oem u01]$ locate oraInst.loc | grep agent
 [oracle@oem u01]$ cat /u01/app/oracle/product/12.1.0/agent/core/
[oracle@oem OMS_BACKUP]$ tar -cvzf GRID_Inventory.tar.gz /u01/app/oracle/oraInventory

# Middle-ware Home and EM domain – take a snapshot of your OMS(Oracle Management Service) use the syntax bellow:

 /bin/emctl exportconfig oms [-sysman_pwd ]
 [-dir ] Specify directory to store backup file
 [-keep_host] Specify this parameter if the OMS was installed
 using a virtual hostname (using ORACLE_HOSTNAME=)
cd /u01/app/oracle/product/12.1.0/middleware/oms/bin/
 [oracle@oem bin]$ ./emctl exportconfig oms -sysman_pwd -dir /backup/OMS_BACKUP/
 Oracle Enterprise Manager Cloud Control 12c Release 2
 Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
 ExportConfig started...
 Machine is Admin Server host. Performing Admin Server backup...
 Exporting emoms properties...
 Exporting secure properties...
Export has determined that the OMS is not fronted
 by an SLB. The local hostname was NOT exported.
 The exported data can be imported on any host but
 resecure of all agents will be required. Please
 see the EM Advanced Configuration Guide for more
Exporting configuration for pluggable modules...
 Preparing archive file...
 Backup has been written to file: /backup/OMS_BACKUP/opf_ADMIN_20151118_102429.bka
The export file contains sensitive data.
 Please ensure that it is kept secure.
ExportConfig completed successfully!

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

[oracle@oem bin]$ ./emctl config emkey -copy_to_repos -sysman_pwd Oracle Enterprise Manager Cloud Control 12c Release 2
 Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
 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@oem bin]$
[oracle@oemv bin]$ ./emctl status emkey
 Oracle Enterprise Manager Cloud Control 12c Release 2
 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@oem bin]$

# Preserv changes to the memory

[oracle@oem bin]$ ./emctl get property -name 'JAVA_EM_MEM_ARGS'
 Oracle Enterprise Manager Cloud Control 12c Release 2
 Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
 SYSMAN password:
 Value for property JAVA_EM_MEM_ARGS for oms All Management Servers is null
 [oracle@oemv bin]$
$/bin/emctl set property -name 'JAVA_EM_MEM_ARGS' -value '-Xms256m -Xmx1740m'

# stop the EM12c demons:

./$/bin/emctl extended oms jvmd stop -all
 $/bin/emctl extended oms adp stop –all
 ./emctl stop oms -all -force
 ./emctl stop agent

# backup the repository using RMAN

shutdown immediate
 startup mount
RMAN> run{
 allocate channel c1 device type disk format '/backup/OMS_BACKUP/%U';
 backup as compressed backupset database PLUS ARCHIVELOG;
 backup current controlfile;
shutdown immediate
 lsnrctl stop

# Because the DB version is we need to deploy the necessary patches:

unzip p9748749_112020_Linux-x86-64.zip
 unzip p11061801_112020_Generic.zip
cd 9748749
 $ORACLE_HOME/OPatch/opatch apply
 cd 11061801
 $ORACLE_HOME/OPatch/opatch apply
sqlplus / as sysdba

#- Upgrade the OMS

cd EM12cr5

Deselect the checkbox and click Next:



Click “Yes” and move forward

Select “Skip” and click on Next



I ignored the warning in my case since I have both packages installed already. Choose “Ignore” and click Next.


As we do an upgrade choose as in the image above and click Next.


Fill in the Middleware Home Location. Be aware that it has to be a new location and with ~15GB free.


Fill in the necessary password and confirm that you have backed up the repository and click Next.


Click OK and move on.

For the following 2 screens click OK and Yes respectively.


Below you can see all the components that will be upgraded:


Click Next.

Below you can select additional plugins to be deployed:


Click Next when you’re done.

This time I’m doing the installation of the new home on an NFS volume:



In the message below is warning me and it’s giving me an advice about how to proceed after the installation has completed:


Click OK and move on.


Click Next to proceed with the deployment:


The last thing for the OMS upgrade:


Now running the allroot.sh script


And that was it:



Leave Comment

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