Upgrade OEM 12c to OEM 13c Cloud control

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. 12c Release 5 (12.1.0.5)
2. 12c Release 4 (12.1.0.4)
3. 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.

Upgrading OMR note

Ensure that you stop the OMS instances of the earlier release that are connected to the database

emctl stop oms -all

Ensure that you do not have any login or logoff triggers set in the Oracle Database that houses the Oracle Management Repository
SELECT COUNT (trigger_name) FROM sys.dba_triggers WHERE TRIGGERING_EVENT LIKE 'LOGIN%' AND status='ENABLED';
SELECT COUNT (trigger_name) FROM sys.dba_triggers WHERE TRIGGERING_EVENT LIKE 'LOGOFF%' AND status='ENABLED';

Disable if logon or logoff triggers exists

alter trigger disable;
alter trigger enable;

Upgrade the database to 12.1.0.2

Disable the optimizer adaptive feature by setting the optimizer_adaptive_features to false and set compatible to 12.1.0.2.0

alter system set optimizer_adaptive_features=false scope=both;

















ALTER SYSTEM SET COMPATIBLE='12.1.0.2.0' SCOPE=SPFILE;

Restart the OMR database.

Copy emkey

$/bin/emctl config emkey -copy_to_repos [-sysman_pwd ]

Verify with the following command

$/bin/emctl status emkey

If the emkey is copied, then you will see the following message:

The EMKey  is configured properly, but is not secure.
Secure the EMKey by running "emctl config emkey -remove_from_repos".

Restart OMS service.

$/bin/emctl stop oms -all
$/bin/emctl start oms

Create new Middleware home and BI Config and cluster directory should be outside of the Middleware home.

mkdir -p /ssd/oracle/Middleware_1
mkdir -p /ssd/oracle/bi_config
mkdir -p /ssd/oracle/bi_cluster
chown -R oracle:oinstall /ssd/oracle/Middleware_1
chown -R oracle:oinstall /ssd/oracle/bi_config
chown -R oracle:oinstall /ssd/oracle/bi_cluster

To run em pre-requisite check before performing upgrade. Execute following command

./em13100_linux64.bin EMPREREQ_KIT=true EMPREREQKIT_PROPERTY_FILE=


Sample property file
installerMode=emprereqkit
connectString=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=core.localdomain)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=testoem)))
dbPassword=dill1o@
dbRole=sysdba
dbUser=SYS
executionType=install
logLoc=/u01/software/em13c/prerequisiteResults/log
prereqResultLoc=/u01/software/em13c/prerequisiteResults
reposUser=SYSMAN
runPrerequisites=true

Stop the JVMD and ADP engines explicitly:

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

Shutdown OMS

$/bin/emctl stop oms -all

Management Agent Shutdown requirement

$/gc_inst/bin/emctl stop agent

For error emkey has not been copied

/bin/emctl config emkey -copy_to_repos_from_file -repos_host -repos_port -repos_sid -repos_user SYSMAN [-repos_pwd ] [-admin_pwd ] -emkey_file /sysman/config/emkey.ora

TMP directory required at least 10G space, if we do not have sufficient space we can create new temp directory for installation.

mkdir -p /data/tmp/
chown -R oracle:oinstall /data/tmp/

If you are using redhat-6.8 or centos 6.8 modify the parameter to 6.7 because 6.8 is not certified yet.

You may encounter the error below:
Expected result: One of enterprise-6.7,enterprise-6.6,enterprise-6.5,enterprise-6.4,enterprise-6.3,enterprise-6.2,enterprise-6.1,enterprise-6.0,oracle-7.1,oracle-7,redhat-7.1,redhat-7,oracle-8,redhat-6.7,redhat-6.6,redhat-6.5,redhat-6.4,redhat-6.3,redhat-6.2,redhat-6.1,redhat-6.0,SuSE-11,SuSE-12
Actual Result: redhat-6.8

Make source file executable

chown 755 em13100_linux64.bin

Execute em13100_linux64.bin with the command below. Note in my case I have used new temp directory due to un sufficient space on /tmp

./em13100_linux64.bin -J-Djava.io.tmpdir=/data/tmp

Once you execute the em13100_linux64.bin binary this is the landing page.

Uncheck "I wish to receive security updates via My Oracle Support". Click on Next to continue.

Warning message will be displayed. Click on Yes to continue.

Select Skip and Click on Next to continue.

All Prerequisite checks should be succeeded before beginning the installation. Click on Next to continue.

Select Upgrade and existing Enterprise Manager system Click on Next to continue.

Select new Middleware home Click on Next to continue.

Provide the Repository database details. Select Confirm that you have backed up Management Repository and Disable DDMP jobs Click on Next to continue.

Repository database related prerequisite checks in progress.

Patch related information will be displayed. Click on OK once you applied minimal patches required for repository database.

If Management agent is not closed then this message will pop up. Stop the agent and click on OK to continue.

Some fixable configuration requirements error will be displayed. Click on Yes to fix it automatically.

Few warning message regarding the requirements. Click on OK to fix it and continue.

Plugin details will be displayed. Click on Next to continue.

We can choose additional plugins in the case we required. Click on Next to continue.

Type extended weblog server domain Click on Next to continue.

Type BI Publisher Config Volume and Cluster Volume. Click on Next to continue.

BI Publisher port details will be displayed Click on Next to continue.

Summary will be displayed Click on Upgrade to begin upgrade.

Upgrade on progress ##########.

Upgrade on progress ####################.

Upgrade on progress ##############################.

Upgrade on progress ########################################.

Execute listed allroot.sh script file as user root. Once execution completes Click on OK to continue.

Information regarding OEM upgrade complete will be displayed. Click on Close to complete upgrade.

Now we can login OEM 13c with the same details as of OEM 12c. Same URL and same user credentials.

Click I accept on the License Agreement. 

OEM 13c is ready to use.