Enterprise Manager Cloud Control 12c Release

12.1.0.1 Bundle Patch 1

Contents

EM 12.1.0.1 Bundle Patch1 Overview ....................................................................................................... 2

Use cases and Recommendations ............................................................................................................ 2

Bundle Patch1 Compatibility Matrix ......................................................................................................... 5

Mandatory Pre-Requisites for installing Bundle Patch1 ........................................................................... 5

1. Configure Oracle Software Library: ............................................................................................... 6

2. Back up EM components .............................................................................................................. 7

3. Make sure that you are using correct OPatch version ................................................................. 7

Bundle Patch (BP1) Install Instructions ..................................................................................................... 8

A. Apply Bundle Patch1 on Oracle Management Service ................................................................. 9

B. Setting up the Infrastructure for Agent Patching before doing Plug-in Upgrade ....................... 17

C. Upgrade all Deployed Plug-ins to the 12.1.0.2 Releases on OMS .............................................. 31

D. Apply Bundle Patch 1 on Management Agents .......................................................................... 50

E. Upgrade all downloaded Plug-ins to the 12.1.0.2 Releases on Management Agent ................. 55

F. Upgrade the BI Publisher Reports that shipped with the plug-ins ............................................. 61

G. Upgrade ADP and JVMD(Optional) ............................................................................................. 62

Update Existing Agent Image to Agent Image with BP1 included ...................................................... 68

Troubleshooting .................................................................................................................................. 76

EM 12.1.0.1 Bundle Patch1 Overview

This document provides step by step instructions for applying Bundle Patch1 (BP1) in to your existing

Enterprise Manager Cloud Control 12.1.0.1 installation. This Note that this Bundle Patch1 is not an EM

Patchpatch set release, and therefore does not change the EM version to 12.1.0.2.

Follow the steps below in strict order. Skipping steps could result in potential issues.

Use cases and Recommendations

No Use case Recommendation

1 If you are new to Enterprise Manager Get the new EM12c binaries from OTN and do a

fresh install. The installation will include BP1 and the

latest plug-in releases.

2 If you are using the Enterprise Manager

Cloud Control 12.1.0.1 release in a non-

production test or "sandbox"

environment

Analyze how much configuration setup you have

done in EM and the number of Management Agents

you have deployed. Based on that, if feasible, de-

install the existing Cloud Control and do a fresh

installation. . This also means that you have to re-

install all of your existing Management Agents. This

is the simplest way to get to the benefits and

features of the latest patched Cloud Control release,

which includes BP1 and the latest plug-in releases.

Follow the EM Deinstallation instructions available

here

Get the updated EM binaries with BP1 from OTN

3 If you have already downloaded and

installed 12.1.0.1 release in a Production

environment

Follow the below instruction in strict order. Skipping

steps could result in potential issues.

a) Backup your Oracle Inventory, Repository

Database, Middleware Home, Instance Home,

Software Library, Management Agent

b) Apply BP1 on your Oracle Management Service

(OMS) host

c) Upgrade your plug-ins to the latest 12.1.0.2

releases

d) Apply BP1 on your Management Agents

We recommend that you open a pro-active SR

Note: If you have Additional OMS instances or a

disaster recovery configuration, then follow the

Batch Patch 1 application instructions from the

“Apply Bundle Patch1 on Oracle Management

Service” section below.

4 If you are upgrading from an EM Grid Control 10.2.0.5 or 11.1.0.1 releases to EM12c

a) If you’re planning for EM upgrade to

EM12c

You can upgrade directly from Grid Control 10.2.0.5

or 11.1.0.1 releases to EM12c with BP1 included.

a) Download the latest pre-upgrade console

patch from OTN

b) Download the Management Agent and

12.1.0.2 plug-in binaries from OTN

c) Download the EM12c binaries with BP1

included from OTN

d) Follow the Upgrade Guide for instructions

b) If you have just applied the pre-

upgrade console patch and haven't

gone ahead with Management

Agent or OMS upgrade

Follow the steps below:

a) Get the new pre-upgrade console patch

from OTN (you can rollback the old patch or

deploy the new patch on top of the existing

one)

b) Get the new Management Agent zip files

from OTN

c) Get the new 12.1.0.2 plug-in binaries from

OTN

d) Get the new EM12c binaries with BP1

included from OTN

Note: The new version of the pre-upgrade console

patch will only work with EM12c binaries (with BP1

included) and Management Agent 12.1.0.1binaries.

To ensurethat you get the latest patch from OTN,

refer to the last updated date on the OTN download

page.

c) If you have applied the pre-upgrade

console patch and have gone ahead

with Management Agent or OMS

upgrade

Finish your upgrade to EM12c and then follow the

instructions in strict order :

a. Backup your Oracle Inventory, Repository

Database, Middleware Home, Instance

Home, Software Library, Management Agent

b. Apply BP1 on your OMS

c. Upgrade your plug-ins to the 12.1.0.2

releases

d. Apply BP1 on your Management Agents

Oracle recommends that you open a proactive

Service Request (SR) with Oracle Support.

5 If you are planning to perform an additional OMS install

a) If your first OMS is deployed with

new EM binaries with BP1

included or if you have applied

the BP1 manually

You can proceed with the additional OMS

installations. The deployment procedure will clone

the first OMS, so there will be no need to apply BP1

on the second OMS once the install is done.

As a part of the additional OMS installation you will

be required to deploy the Management Agent on the

host where you plan to have the additional OMS.

Get the latest Management Agent binaries from the

Self Update feature, which have BP1 included for

Management Agent deployment.

b) If your first OMS has not been

updated with the new EM, or if

you have not applied the BP1

manually to the OMS

Select one of the following options:

Option 1:

i. Follow the BP1 application process on the

first OMS and Agents

ii. Then do the additional OMS install

Option 2:

i. Do the additional OMS install

ii. Follow the BP1 application process on the

first OMS and additional OMS together

Bundle Patch1 Compatibility Matrix

Refer to following compatibility table to understand the valid patches and version combinations of OMS,

Plug-ins and Management Agents:

Target Agent without

Bundle Patch1 applied

and 12.1.0.1 plug-in

on target

Management Agent

Target Agent with

Bundle Patch1 and

12.1.0.1 plug-in on

target Management

Agent

Target Agent

without Bundle

Patch1 and 12.1.0.2

plug-in on target

Management Agent

Target Agent with

Bundle Patch1

applied and 12.1.0.2

plug-in on target

Management Agent

12.1.0.1 OMS

without Bundle

Patch1 applied

Yes No No No

12.1.0.1 OMS with

Bundle Patch1

applied and

12.1.0.1 plug-in on

OMS (no plug-in

upgrade)

Yes Yes No No

12.1.0.1 OMS with

Bundle Patch1

applied and

12.1.0.2 plug-in on

OMS (plugin

upgrade done)

Yes ** Yes Yes Yes *

*This is a Fresh Install of EM12c binaries with BP1 included

**An example for this use case is that you have:

• Solaris Management Agents without BP1 applied;

• 12.1.0.1 plug-ins pointing to Linux 32-bit OMS with BP1 applied; and

• 12.1.0.2 plug-ins on the OMS.

Mandatory Pre-Requisites for installing Bundle Patch1

1. Configure the Software Library.

2. Back up all Enterprise Manager components.

3. Set up the Agent Patching Infrastructure (differs for online versus offline modes) .

4. Configure My Oracle Support (MOS) connection (For Agent Patching) or download patches from

My Oracle Support and then upload them to Enterprise Manager.

Make sure that you go through all of the pre-requisites below before applying Bundle Patch 1.

1. Configure Oracle Software Library:

Verify whether you already have the Software Library configured. If not follow the

below steps to configure:

From the Enterprise menu, select Provisioning and Patching, then click Software

Library.

If there is nothing configured yet, click Actions -> Administration -> Add then choose

OMS Shared Filesystem location.

Note: This is a location on a shared file system that is 'visible' to all OMS instances. For example,

this could be a NFS mounted location and should have read/write access from all of the OMS

instances.

Upon addition of the location, a job executes to configure the Software Library. Under this

location, all required entities for EMs features like Provisioning, Patching, and Cloud

Management are populated.

Once the job is successful, you will see the components configured in the Software Library.

To view the Software Library, navigate to: Enterprise Manager > Patching and Provisioning >

Software Library

2. Back up EM components: Before you apply Bundle Patch 1, ensure that you back up the

following components:

a) Oracle Inventory

b) Management Repository Database

c) Middleware Home and EM domain

d) Instance Home where OMS is installed

e) Default Management Agent with OMS

f) Software Library

IMPORTANT: You MUST back up all components listed above. In case of a failure during any stage

of the Bundle Patch 1 process, you might have to restore one or more of these components from

the backup.

Refer to "Backing Up Enterprise Manager" chapter from the Admin guide here

http://docs.oracle.com/cd/E24628_01/doc.121/e24473/ha_backup_recover.htm#BGBCCIJC

3. Make sure that you are using correct OPatch version

Verify you have the right OPatch version under the OMS Oracle Home. The OPatch version

required for installing the Bundle Patch 1 is 11.1.0.9.4 or higher.

Note: It has to be 11.1.0.x series of OPatch and NOT OPatch 11.2.x

Set ORACLE_HOME to OMS HOME. Run the command as shown in the figure below to

verify the OPatch version.

Bundle Patch (BP1) Install Instructions

Follow the below sequence of applying the BP1 .

1. Apply Bundle Patch1 on Oracle Management Service

2. Upgrade all deployed Plug-ins to the 12.1.0.2 releases on the OMS

3. Apply Bundle Patch 1 on all Management Agents

4. Upgrade all deployed Plug-ins to the 12.1.0.2 releases on the Agents

Important Note:

1. Ensure that you have first applied the OMS Patch 13242773 on all OMS instances before

applying this Bundle Patch on Management Agents. If the OMS patch is not applied before

applying the Bundle Patch, then the metadata version will not be registered with the OMS, and

the OMS will block the patched Management Agents from uploading data.

2. If you have configured Enterprise Manager for High Availability by deploying one or more

Additional OMS and using a local RAC and/or Data Guard database for the repository database,

the sequence of patching would be to stop each OMS; apply the patch to each OMS Oracle

Home then run the post deploy steps as described in section A , step14 below.

There is no special consideration when using Data Guard since any changes to the repository

that occur as part of the patching exercise are forwarded to the standby database repository as

part of normal Data Guard operations.

3. If you have configured Enterprise Manager for Disaster Recovery by deploying one or more

Standby OMS and a standby database (RAC or single instance) at another site, patching of the

standby site should be performed after all patches and plugin updates have been deployed on

the primary site.

Once the primary site patches and updated plug-ins have been deployed on the primary site,

any changes to the repository that are made due to those updates will be forwarded to the

standby database repository as part of normal Data Guard operations. Therefore, patching of

the standby site consists of applying the patches to the standby OMS homes ( as described

below in section A ) without performing post deploy operations that update the repository and

deploying updated plugins without updating the repository.

A. Apply Bundle Patch1 on Oracle Management Service

Note: In a multi-OMS environment, ensure these prerequisites have been met on each OMS

host.

1. Ensure that you have the latest version of OPatch 11.1. The minimum OPatch version required

for installing Bundle Patch 1, should be greater than or equal to 11.1.0.9.4.

NOTE: You must ensure the OPatch version is 11.1.0.9.x where x is 4 or higher. Do NOT use

OPatch 11.2.x.

You can determine the current version of OPatch by running the command opatch version from

the OMS Home/OPatch

To determine the latest version of OPatch available, log in to My Oracle Support, select the

category Patches, and enter 6880880 in the search field. If you do not have the latest version,

follow the install instructions in the readme for 6880880.

2. Set the ORACLE_HOME environment variable to the OMS Home, which

is <MIDDLEWARE_HOME>/oms

3. Ensure that you set the PATH environment variable to include the location of

the unzip executable, the <ORACLE_HOME>/bin, and that the

<ORACLE_HOME>/OPatch directories are present in the OMS Home.

setenv PATH $ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH

Check if the PATH variable is set by running the command:

echo $PATH

4. Ensure that you verify the Oracle Inventory that is accessed by OPatch to install the patches. To

verify the state of the Oracle Inventory, run the following command. If the command displays

any errors, contact Oracle Support and resolve the issue:

$ opatch lsinventory

5. Ensure that the Oracle Database, which contains the Management Repository, and its listener

are up and running.

6. Ensure that you have the SYSMAN password ready. You will have to enter the password when

prompted.

7. Download the OMS Bundle patch1 13242773 from My Oracle Support.

8. Also download the JDeveloper and Web Services Manager patches 13470978 and 12321965

from My Oracle Support . You will be required to apply these patches after applying the

13242773 BP1 on OMS.(Refer step16)

Note: Download the patch 12321965 for FMW 11.1.0.1.5 version as shown in the below

screenshot

9. Choose a location for storing the contents of the Bundle Patch 1 ZIP file. In the rest of the

document, this location (absolute path) is referred to as <PATCH_TOP_DIR>.

10. Extract the contents of the Bundle Patch 1 ZIP file to the location you created in Step (1). To do

so, run the following command:

$ unzip -d <PATCH_TOP_DIR> p13242773_121010_<platform>.zip

Navigate to the <PATCH_TOP_DIR>/13242773 directory:

$ cd <PATCH_TOP_DIR>/13242773

11. Ensure that you shut down the OMS by running the following command:

$ emctl stop oms -all

To verify that the OMS has completely stopped, run the command emctl status oms,

and verify the status. Ideally, the OMS and its associated services will be down.

Note: In a multi-OMS environment, shut down all OMS instances.

12. Stop the following components if running within your Cloud Control domain before applying

Bundle Patch 1 or updating any plug-in to the latest release:

• Application Dependency and Performance (ADP) Manager

• JVM Diagnostics (JVMD) Manager

• BI Publisher Managed Server named "BIP"

13. Install Bundle Patch 1 by running the following command:

$ opatch apply

In a multi-OMS environment, ensure that you run this command on all OMS instances.

14. Run the following script to automate the Bundle Patch 1 post installation process.

Note: Ensure that you are in the Bundle Patch 1 location <PATCH_TOP_DIR>. Also, keep the

Repository host name, SID, Listener port, and sysman password ready before running

the post_deploy.sh script.

a) In a single-OMS environment, run the following command from the Bundle Patch 1

directory:

$ <PATCH_TOP_DIR>/13242773/post_deploy.sh

Note: The OMS will be started automatically after running this post_deploy.sh

It will ask you for the Patch location please provide the location from where ran the

post_deploy.sh

b) In a multi-OMS environment, do the following:

i. Run the following command only on the OMS that is co-located with the Administration

Server. The Administration Server location details are available in config.xml file that is

located in a path similar to the following:

<%middleware_home%>/instance/user_projects/domains/GCDomain/config.

In the config.xml file you will find the Administration server details. For example:

<listen-address>myadminserver.us.oracle.com</listen-address>

You can also find the Admin server by running the following commands from

OMS_HOME/bin

./emctl status oms

Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0

Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.

WebTier is Up

Oracle Management Server is Up

./emctl status oms –details

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 :

Console Server Host : slc00tae.us.oracle.com

HTTP Console Port : 7789

HTTPS Console Port : 7801

HTTP Upload Port : 4890

HTTPS Upload Port : 4901

OMS is not configured with SLB or virtual hostname

Agent Upload is locked.

OMS Console is locked.

Active CA ID: 1

Console URL: https://slc00tae.us.oracle.com:7801/em

Upload URL: https://slc00tae.us.oracle.com:4901/empbs/upload

WLS Domain Information

Domain Name : GCDomain

Admin Server Host: slc00tae.us.oracle.com

Managed Server Information

Managed Server Instance Name: EMGC_OMS1

Managed Server Instance Host: slc00tae.us.oracle.com

ii. Then execute:

$ ./post_deploy.sh

iii. Run the following command from the Bundle Patch 1 directory on all other OMS

instances except the primary OMS :

$ ./MultiOms_post_deploy.sh

15. It’s mandatory that you apply JDeveloper and Web Services Manager patches 13470978 and

12321965 to the OMS.

If you have EM installed using the EM binaries with BP1 then this JDeveloper patch is

automatically installed with no further work required. If you are apply the BP1 on your existing

EM, then you have to apply the JDeveloper patch as an extra step. There are a variety of fixes in

the patch that customers require some functional issues, as well as ability to run on Chrome

browser and IE9 browser. The JDeveloper patch should be applied AFTER the BP.

For instructions, refer to the ReadMe of the respective patch.

When you search for patch 12321965, you will find two releases of the patch: 11.1.1.5.0 and

11.1.1.4.0. Ensure that you select and apply the 11.1.1.5.0 release of the patch. Ensure that you

apply both the patches in the oracle_common directory that resides in the Middleware Home

(MW_HOME/oracle_common/). Set environment variable ORACLE_HOME to your

"[MW_HOME]/oracle_common" directory before applying the patches 13470978 and 12321965

to the OMS.

16. To verify if Bundle Patch 1 has been installed properly:

a) Run the following command to verify whether the patch is registered in the

inventory:

$ opatch lsinventory

b) To verify that all the patches are installed on the OMS, run the following commands:

• Set the following environment variable on the OMS host:

setenv ORACLE_HOME <MIDDLEWARE_HOME>/oms

• Run the following verification commands:

./<MIDDLEWARE_HOME>/oms/opatch lspatches -id 13242773 -verify

./<MIDDLEWARE_HOME>/oms/opatch lspatches -oh

<MIDDLEWARE_HOME>/oracle_common -id 12321965 -verify

./<MIDDLEWARE_HOME>/oms/opatch lspatches -oh

/<MIDDLEWARE_HOME>/oracle_common -id 13470978 –verify

17. Apply BP1 patches to each standby OMS (if standby OMSs have been deployed)

a) Shutdown all standby OMS servers

b) Using Opatch apply, apply the patch binaries. Follow the instructions from step7 onwards and

don’t run post_deploy.sh (step 14)

c) Run the following for each standby OMS instance:

You will get the below scripts under : <13242773_PATCH_TOP_DIR>/custom/scripts/

$ORACLE_HOME/perl/bin/perl <13242773_PATCH_TOP_DIR>/apply12959056.pl

$ $ ORACLE_HOME/perl/bin/perl <13242773_PATCH_TOP_DIR>/ apply13479448.pl

$ sh $ORACLE_HOME/bin/exec_13651296_patch

B. Setting up the Infrastructure for Agent Patching before doing Plug-in

Upgrade

For patching Management Agents, the patches can be automatically downloaded during the patching

flow if Enterprise Manager is configured to connect to My Oracle Support. Otherwise, if a connection to

My Oracle Support is not possible, you can upload the patches manually to Enterprise Manager. Based

on your connectivity policy, follow the sub sections below to set up the necessary infrastructure in

either online or offline mode.

Setting up the Infrastructure if you are using Agent Patching in Online Mode

a) Set up the connection to My Oracle Support (Online mode)

Check to see if the connection to My Oracle Support is set to “Online”. Navigate to

Setup > Provisioning and Patching > Offline Patching.

a) The connection setting has to be “Online”. If not set, set it to Online and click Apply.

b) Select the adjacent tab My Oracle Support and Proxy Connection

c) Configure your Proxy Connection to connect to My Oracle Support, if needed. If you choose

Manual Proxy Configuration, provide the required Proxy Server, Port and Realm details, then

click Apply.

d) Once the configuration is done, click Test to check if the connectivity works correctly. Upon

successful TEST , save the configuration by clicking APPLY.

If you cannot configure connection to My Oracle Support, choose to switch to Offline Mode.

Note: The Error is informational. From the message on screen, you can follow the link to

setup MOS Credentials. The same is explained in the next step too.

1) Set up My Oracle Support Credentials:

Follow the below steps to set up the My Oracle Support credentials. If you have already set up your MOS

credentials then you can skip this step

i. From the Setup menu, select My Oracle Support, then select Set Credentials.

ii. Supply your My Oracle Support credentials, then click Apply.

Clicking APPLY will save the My Oracle Support Credentials. It also triggers jobs for Updating the Opatch

and Refresh From My Oracle Support. Check if the jobs complete successfully before proceeding. The

jobs won’t be triggered if it had run successfully in the last 24 hrs, you could then proceed.

2) Setting up the Infrastructure if you are using Agent Patching in Offline Mode

If you cannot use Online mode and configure connectivity to My Oracle Support , then you

must use the offline patching method. Follow the steps below to set up the infrastructure to

patch your Management Agents with the Bundle Patch.

a) Verify that the connection to My Oracle Support is set to “Offline”:

Navigate to Setup > Provisioning and Patching > Offline Patching.

On the Patching Setup page, choose “Online and Offline Settings” tab, select Offline

and click Apply

b) Update the Metadata Files of Enterprise Manager :

i. Download Metadata Files from My Oracle Support (https://support.oracle.com):

You can download all of the required XMLs through a ‘wget’ script. Execute the script as

instructed in Support Note 1436338.1

You can also select and download the files manually by following the below step in this

section.

List of metadata files to download:

Metadata

XML File Location To Download From

aru_products.

xml

https://updates.oracle.com/Orion/Services/metadata?table=aru_products

aru_releases.

xml

https://updates.oracle.com/Orion/Services/metadata?table=aru_releases

aru_platforms

.xml

https://updates.oracle.com/Orion/Services/metadata?table=aru_platforms

aru_language

s.xml

https://updates.oracle.com/Orion/Services/metadata?table=aru_languages

aru_product_

groups.xml

https://updates.oracle.com/Orion/Services/metadata?table=aru_product_groups

aru_product_

releases.xml

https://updates.oracle.com/Orion/Services/metadata?table=aru_product_releases

aru_compone

nt_releases.x

ml

https://updates.oracle.com/Orion/Services/metadata?table=aru_component_releases

aru_targets.x

ml

https://updates.oracle.com/Orion/Services/metadata?table=aru_targets

certifications.

xml

https://updates.oracle.com/Orion/Services/components?ctype=product,release,platfor

m,platform_version,wildcard-release,config-group,release-component,certification

patch_recom

mendations.x

ml

https://updates.oracle.com/Orion/Services/search?language_id=0&classification_group

=recommended&patch_type=all&group_by=target_type&group_by=release&group_by=

platform

Download the URLs and store them in the local system.

Tip: Copy paste the contents of every URL into a separate file (word doc/notepad) and save

it with the proper name, with the .xml extension(For example, save the file as

“aru_products.xml”)

Open the URL in the browser, copy paste the contents to a Note Pad and save the file as an

XML.

ii. Upload the metadata files to Enterprise Manager:

Navigate to Patching Setup Page, Setup > Provisioning and Patching > Offline Patching.

From Metadata Cache section, upload the metadata files to Enterprise Manager from the

local desktop.

Choose or Browse File to pick the file from the Local System. Click Upload once you have

selected all the metafiles.

Upon successful Upload, the status column for all the XML files would turn Green.

iii. Run the “Refresh From My Oracle Support” Job:

From the Enterprise menu, select Job, then select Activity.

On the Job Activity page, from the Create Job list, select Refresh From My Oracle

Support and click Go.

Specify a Name for the Job and Submit It

Upon submit a Job is created and submitted

Click on the link to track the status of the job. Ensure the job succeeds. You might have to

refresh the page or set up the refresh to be every 30 seconds.

Note: If the job fails, refer to the trouble shooting section at the end of the document

or call Oracle Support.

c) Download the required Management Agent patches and OPatch patches

i. Download the Management Agent patches from Oracle’s support site - My

Oracle Support(https://support.oracle.com)

From the “Patches & Updates” page, in the Patch Search region, specify all the

four patch numbers as comma-separated entries: 13242776, 13491785,

13550565, 13550561. Ensure you select the right platform, for example:

Click Search

Download the patch zip files and also the Patch Metadata files for the patches. Ensure you download

both.

To download the Patch Zip file, click on the Patch File . To download the Patch Metadata file, click

“Download Patch Metadata” link and then click “Download”.

ii. Download the required OPatch patches from My Oracle Support

(https://support.oracle.com)

Search for patch “6880880” for the appropriate Management Agent target’s platform (say your target is

Linux x86-64, pick platform Linux x86-

64)

Download the patch for the version 11.1.0.0.0 series ONLY (the latest version is listed there)

Download both the Patch zip file and the Patch Metadata for the Patch. Ensure you download both. To

download the Patch Metadata file, click “Download Patch Metadata” link and then click “Download” in

the pop up window.

d) Upload the patches to the Software Library as follows:

1) Upload Management Agent patches to the Software Library.

i. Go to Enterprise -> Provisioning and Patching -> Saved Patches. From the

Saved Patches page, click the Upload button to open “Upload Patches to

Software Library” page.

ii. Out of the four patches for Management Agents, two are for “Base platform”

(13242776 and 13491785) and the other two are for “Oracle Home plug-in”

(13550561 and 13550565).

iii. Set the Basic Information in the page as shown in the image below:

For patches: 13242776 and 13491785, pick the Patch Metadata file and Patch zip file

from the local directory on the system and click Upload.

iv. Upload patches 13550561 and 13550565 by selecting their patch metadata and

the patch zip file.

v. Reset the basic information attributes in the page as shown below.

vi. Select the patch zip file and the metadata file and click Upload.

2) Upload OPatch 6880880 to the Software Library.

Specify the “Basic Information” attributes as shown in the screen below. Select the

Patch Metadata and Patch Zip file for the Opatch patch 6880880 and upload it.Ensure

you choose the release version as “11.1.0.0.0”.

Upon successful upload, all the patches will be visible in the Saved Patches page.

C. Upgrade all Deployed Plug-ins to the 12.1.0.2 Releases on OMS

Pre-Requisites for deploying Plug-ins

Make sure that you upgrade all of your version 12.1.0.1 plug-ins to the latest 12.1.0.2 releases,

where available. Update all plug-ins on an OMS instance at the same time. Plug-ins can only be

updated one at a time, but you should upgrade one after the other until all have been upgraded.

1. Login into your repository database as sysman and recompile invalid objects

EXEC EMD_MAINT_UTIL.recompile_invalid_objects

Make sure that you don’t have any invalid objects in your repository. To check any invalid object,

log into the repository as sys user and run the following sql:

SELECT object_name, object_type FROM ALL_OBJECTS WHERE owner='SYSMAN' and status <>

'VALID' ;

2. Make sure that DBMS jobs are running. If they are not running them run the following package as

sysman user :

EXEC EMD_MAINTENANCE.submit_em_dbms_jobs

To check if jobs are running or not: From EM console -> Setup -> Management Server and

Repository -> Repository

3. Restart the Database and OMS before your start the plug-in upgrade.

4. Make sure that Target Management Agent where you will be upgrading your plug-in

is up and running.

5. If you are updating to the 12.1.0.2 release of the Oracle Fusion Middleware Plug-in, and you

already have Application Dependency and Performance (ADP) and/or JVM Diagnostics (JVMD)

installed, you must follow the instructions in "Optional: Upgrade ADP and JVMD" section at the

end of this document.

6. Stop the following components if running within your Cloud Control domain before updating any

plug-in to the latest release:

• Application Dependency and Performance (ADP) Manager

• JVM Diagnostics (JVMD) Manager

7. Make sure that you upgrade all of your 12.1.0.1 version plug-ins to 12.1.0.2 releases one after the

other until all have been upgraded. This means downloading one 12.1.0.2.0 plug-in, deploying

that plugin, then downloading another 12.1.0.2.0 plug-in and deploying that one and so on.

Deploying Plug-in in Online mode on OMS

1. From the Setup menu, choose Extensibility and then choose Self Update. Click Self Update to get

the complete list of available updates

2. Select the desired entity type (Plugin) and click on the “Check Update “button to see the updates

available. Once this is done you will be able to see the number of updates available for Plug-in

A job gets triggered and updates the “Available Update” column

3. Choose Open from the Action menu. The entity type page appears

4. Select an update from the list of available updates, then click Download. The Schedule

Download dialog appears. In this example, the Oracle Audit Vault plug-in is selected.

5. Select when to download the update. Note that multiple downloads can be scheduled

simultaneously.

Click Select. An Enterprise Manager job is created to download the update to the Software Library.

Enterprise Manager starts downloading the archive from the Oracle Enterprise Manager store. Wait

for the download to complete.

Note: The page is not refreshed automatically. Click the refresh icon to view the updated download

status.

Once an entity has been downloaded to the Software Library, it is ready to be applied to your

installation. Select an update from the list whose status is Downloaded, then click Apply.

You will be redirected to the plug-in deployment page.

.

Note: Follow the below steps to deploy each updated Plugin on each Standby OMS:

a) Extract the Plugin archives from the Primary site

b) Go to the Self Update Home, click on Plugins, select the required plugin and select

export from the Action table menu. Note the EMCLI command from the popup that

gets displayed.

emcli export_update -id=<update id> -deep -host=<standby OMS host> -dir=<directory

to export archives> <host credential options>

Note that an additional option “-deep” is required. This command would create 4 files

on the destination directory specified. The filename

<version>_OMS_<platform>_<revision>.zip is the one to be used in next step.

c) Start the Standby Administration Server, if it is down.

OMS_HOME/bin$ emctl start oms -admin_only

d) Install the OMS archive to First Standby OMS Oracle Home

OMS_HOME/bin$ pluginia –archives <path to plugin archive>

e) Configure the Plug-in on First Standby OMS Oracle Home

pluginca -action deploy -isFirstOMS true -plugins <plugin-list> -oracleHome <oms

oracle home> -middlewareHome <wls middleware home>

where, <plugin-list> is the plugin name in the format <plugin-id>=<plugin-version>

f) Repeat steps 3 and 4 for each Standby additional OMS

OMS_HOME/bin$ pluginia –archives <path to plugin archive>

pluginca -action deploy -isFirstOMS false -plugins <plugin-list> -oracleHome <oms

oracle home> -middlewareHome <wls middleware home>

g) This completes the plugin deployment on Standby site. Validate the plugins by going to

self update, click on the plugin and view the information, all oms servers should be

listed.

6. Select the plugin and deploy it on OMS first and then to the agent. Right click the plugin ->Deploy

on->Management server

7. Provide the repository sys password and click continue

8. Plugin upgrade pre-requisites will be executed.

9. Once the prerequisites are successful click deploy

Note: OMS will be bounced now

10. Once the OMS is up, navigate to Setup->Extensibility->Plug-in . The Plugin version on OMS is now

12.1.0.2.

11. Deploying each updated Plugin on each Standby OMS:

a) Extract the Plugin archives from the Primary site

Go to the Self Update Home, click on Plugins, select the required plugin and select 'export'

from the Action table menu. Note the -id value from the example commands displayed in

the pop-up.

Run the following EM CLI command on one of the primary site OMS servers:

emcli export_update -id=<ID_FROM_POP-UP> -deep -omslocal -dir=<dirname>

Note: The "-deep" option is required. In a multiple OMS setup, the request can be processed

by any OMS, so the directory should be a valid path, ideally shared, for each OMS that could

process the request.

The EM CLI command generates a zip file in the specified directory. That zip file should be

copied to a location on the standby OMS and extracted. The extracted file with a name of

the form <version>_OMS_<platform>_<revision>.zip is the one to be used in the following

steps.

b) Start the Standby Administration Server, if it is down.

emctl start oms -admin_only

c) Install the OMS archive to First Standby OMS Oracle Home

pluginia –archives <path to plugin archive>

d) Configure the Plug-in on First Standby OMS Oracle Home

pluginca -action deploy -isFirstOMS true -plugins <plugin-list> -oracleHome <oms oracle home> -

middlewareHome <wls middleware home>

where <plugin-list> is the plugin name in the format <plugin-id>=<plugin-version>

e.) Copy the plugin archive file to each Standby additional OMS

f) Run the following commands from each Standby additional OMS Oracle Home:

pluginia –archives <path to plugin archive>

pluginca -action deploy -isFirstOMS false -plugins <plugin-list> -oracleHome <oms oracle home>

-middlewareHome <wls middleware home>

g) This completes the plugin deployment on Standby site. Validate the plugins by going to self

update, click on the plugin and view the information, all oms servers should be listed.

Deploying Plug-in in Offline mode on OMS

1. Navigate to Self Update page

2. You will view the Self Update home page

3. Click on “Check Update”

4. You will get the following pop-up

You have to download the catalog of all updates published at Oracle from the url shown in the

popup -

https://updates.oracle.com/Orion/Download/download_patch/p9348486_112000_Generic.zip

Note: Don’t unzip the file

Make sure that you have this zip file on the OMS host. In this example i have created a directory

“plugupdate “ on OMS host to have this catalog zip file

5. Go to the 12.1 OMS home/bin and login into the emcli by running the command as install user:

./emcli login -username=sysman

6. Perform emcli synchronize (Mandatory)

7. Import the catalog file by executing the below command:

./emcli import_update_catalog -omslocal -file=<absolute location of the zip file>

Example:

./emcli import_update_catalog -omslocal -

file=/scratch/pluginupdate/p9348486_112000_Generic.zip

Tip: If you have a multi-OMS setup, run emcli help import_update_catalog for additional

considerations

8. Go back to the Self update homepage and perform the refresh of the page. You will see the

count of new updates under Available Updates column.

9. Click on Plug-in folder and you will the list of the available new plug-in

10. Select the required plug-in and click Download. In this example I have selected the MOS plugin

11. You will get a pop-up

12. Follow the instructions on the popup. Download the update file for the selected plugin and

make sure it’s on the OMS host.

Note: You have to download the update file for all the plugins separately one after the other. In

this example I have downloaded the update file for MOS plugin.

13. Go to the 12.1 OMS home/bin and import the update file which you download in the above

step, by executing the below command:

./emcli import_update -omslocal -file=<absolute location of the zip file>

Example:

./emcli import_update -omslocal -file=/scratch/pluginupdate/p13789099_112000_Generic.zip

Tip: if you session has expired, you might be prompted to login again. Do so by running emcli

login –username=sysman

This command will make the update show up in “Downloaded” state in the Self Update Home

page and can be “Applied” from the UI. Follow the steps from above section “Deploying Plug-in

in Online mode” to deploy the plug-in on OMS

14. Go to the Self Update page-> Plugin. You will see the status change for MOS plugin from

Available to Download

Note: you have to download the update files for the reaming plugins one after the other and

then run the emcli command to change the status from available to download.

15. Select the plug-in and click on Apply. Follow the steps from above section “Deploying Plug-in in

Online mode” to deploy the plug-in on OMS

D. Apply Bundle Patch 1 on Management Agents

Steps to apply Patches on Agent

1. Ensure the OMS patches are applied before starting with patching of the Management Agents.

2. Ensure that all plug-ins have been upgraded to 12.1.0.2 releases.

Note: For generic flow of patching agents using Patch plans, you can see the video in My Oracle Support

note 1359221.1 [Video]

3. From the Enterprise Menu, select Provisioning and Patching , then select Patches and Updates.

4. On the Patches and Updates page, in the Patch Search Region, enter the Patch numbers 13242776,

13491785, 13550565, 13550561, then click Search. If EM is in Offline patching mode, you will need

to search for patches individually, one at a time (13242776, 13491785, 13550565, 13550561).

5. The patch based on the connectivity setting to My oracle Support will be either searched directly

from My Oracle Support or from the pre-staged Software library list. Select all the patches, then

click Add to a Plan, then select Add to New.

6. Specify a name for the plan. Set the target type to “Agent” and specify the Management

AgentManagement Agent target names you want to search for. You can also search for Groups, if

you have any created.

Select the Management Agents you want to patch and click Create Plan

7. Click View on the top , to view the newly created Patch plan.

8. Click Next or click on Deployment Options in the left –hand panel.

9. From the Deployment Options, specify the credentials of the target Management Agents. If not

already set, choose to override and pick a named credential for the target Management Agent

Oracle Home.

Note: if you have do not have direct access to ‘ORACLE’ credentials and have to setup Privilege

credentials as ‘root’, configure EM to use SUDO or PBRUN. Follow the instructions under chapter -

Setting up Credentials in the Lifecycle Management Guide:

URL: http://docs.oracle.com/cd/E24628_01/em.121/e27046/infrastructure_setup.htm#BABGGJB

10. Click Next or validation on the left-hand panel:

11. On the Validation page, click Analyze. The analysis process runs pre-requisite checks and also

checks for patch conflicts. The Analysis process takes close to 10mins to complete.

12. Upon completion of Analysis, click Next and from the Review page, click Deploy.

The process takes sometime based on the number of agents you are patching, It can be tracked from

Show Detailed Progress

link.

E. Upgrade all downloaded Plug-ins to the 12.1.0.2 Releases on Management

Agent

Deploying Plug-in in Online mode on Management Agent

1. From the Setup menu, choose Extensibility and then choose Self Update. Click Self Update to get

the complete list of available updates

2. Choose Open from the Action menu. The entity type page appears

3. You will be redirected to the plug-in deployment page.

.

4. Select the plugin and deploy it on Agent. Right click the plugin ->Deploy on->Management Agent

5. Click on Add to add the management agent where plugin will be deployed

6. Select the required agent and click on “Select” . You can select multiple agents in a single window.

7. Once you have selected the agents, click continue

8. Run the plugin upgrade pre-requisites and click next

9. Click Deploy, to deploy the plug-in on the agents

10. You can monitor the plugin deployment by click on the “show status”

11. Make sure that plug-in are deployed successfully before moving forward.

Deploying Plug-in in Offline mode on Agents

1. Navigate to Self Update page

2. You will view the Self Update home page

3. Since you have downloaded the pluig-ins by following the steps in the above section “Deploying

Plug-in in Offline mode on OMS“ you will the plug-in are in status downloaded

4. Select the Plugin and apply it on Management Agent

Follow the steps from the above section “Deploying Plug-in in Online mode on

Management Agent “

F. Upgrade the BI Publisher Reports that shipped with the plug-ins

Note:

• This step is required If BI Publisher was previously installed and configured to work with EM 12c.

• If BI Publisher is not installed and configured, this step will occur automatically when BI Publisher is

configured at a later time.

1. Start the BI Publisher Managed Server named "BIP".

2. Run the following commands at the command-line of the account that owns the Middleware Home:

emcli login -username=sysman

Enter the sysman password at the prompt, the prompt will not echo.

emcli sync

emcli deploy_bipublisher_reports -force

[It is very important that you use the "-force" option, otherwise the reports will not be updated]

You should receive confirmation of success.

The message will be (in English):

The Enterprise Manager Oracle-provided Reports have been deployed to the Enterprise Manager

Shared folder "Enterprise Manager Cloud Control" on the previously registered BI Publisher

"http[s]://{biphost}:{bipport}/xmlpserver".

G. Upgrade ADP and JVMD(Optional)

NOTE: The instructions below supersede any other instructions on ADP or JVMD patching contained

in the OMS Patch (13242773) ReadMe document.

The instructions below are valid for the following conditions only:

• You already have Application Dependency and Performance (ADP) and/or JVM Diagnostics

(JVMD) installed

• You have updated both Oracle Management Service and Management Agent on target servers

to the 12.1.0.2 release of the Oracle Fusion Middleware Plug-in

If the conditions above apply to your installation, follow the instructions below to upgrade ADP and

JVMD.

Upgrade Application Dependency and Performance

Follow the instructions below to upgrade Application Dependency and Performance.

1. Unzip the ocamm.zip archive, which is in the following location:

$MIDDLEWARE_HOME/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0/archives/ocam

m/

This will create a folder called ADPManager.ear within the same directory.

2. Log in to the Oracle WebLogic Server Administration Console of the EMGC Domain. On the

Home Page, click Servers.

3. Locate all deployed ADP Managers. These will be managed servers that contain

“EMGC_ADPMANAGER” in the server name. For example: “EMGC_ADPMANAGER1”

Perform the steps below for each ADP Manager. For illustration purposes, the server name

“EMGC_ADPMANAGER1” will be used

4. Shut down EMGC_ADPMANAGER1 using Oracle WebLogic Server Administration Console.

5. Use the mv command to rename the existing ADPManager.ear folder in the

EMGC_ADPMANAGER1 directory to ADPManager.ear_12cc01978:

mv

$MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/

ADPManager.ear

$MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/

ADPManager.ear_12cc01978

6. Use the mv command to move the ADPManager.ear folder you created to

EMGC_ADPMANAGER1:

mv

$MIDDLEWARE_HOME/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0/archives/ocam

m/ADPManager.ear

$MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/

7. Change directory to the ADPManager.ear_12cc01978 folder:

cd

$MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/

ADPManager.ear_12cc01978

8. Copy the Ascera.properties file as shown:

cp -f configuration.xml Acsera.properties key

$MIDDLEWARE_HOME/gc_inst/user_projects/domains/GCDomain/EMGC_ADPMANAGER1/

ADPManager.ear/ADPManager.war/config/

9. Add the following properties at the end of the Acsera.properties files you just copied:

JMXContainer.DisableComputeClassPaths = true

DeployerClient.CoreJAgentJars=lib/bcel.jar;

lib/com.oracle.diagnostics.instrumentor_1.8.0.0-try-03.jar; lib/jManagement Agent1.5.jar

DeployerClient.WLDFJar=com.oracle.diagnostics.instrumentor_1.8.0.0-try-03.jar

10. Start ADP Manager using the Oracle Weblogic Administration Console.

11. Redeploy all ADP Agents on the previously configured target servers. Note that you will

essentially redeploy the Agents on top of the original Agents. For instructions, see:

http://docs.oracle.com/cd/E24628_01/install.121/e22624/adp_installation.htm#CJHFFADD

12. Restart the target servers.

Upgrade JVM Diagnostics

Follow the instructions below to upgrade JVM Diagnostics.

1. Unzip the jvmd.zip archive, which is in the following location:

$MIDDLEWARE_HOME/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0/archives/jvmd/

This will create a set of files in the same directory including jammanager.ear.

2. Log in to the Oracle WebLogic Server Administration Console of the EMGC Domain. On the

Home Page, click Servers.

3. Locate all deployed JVMD Managers. These will be managed servers that contain

“EMGC_JVMDMANAGER” in the server name, such as “EMGC_JVMDMANAGER1”.

For each JVMD Manager, perform the steps below. For illustration purposes, the server

name “EMGC_JVMDMANAGER1” will be used.

4. Start EMGC_JVMDMANAGER1, if it is not already running.

5. In Oracle Weblogic Administration Console, click Lock and Edit.

6. Select Deployments, then click the checkbox for Enterprise Application for a JVMD Manager. For

example: jammanagerEMGC_JVMDMANAGER1

7. Click Update.

8. Note the source path to the existing jammanager.ear. For example:

$EMGC_DOMAIN_HOME/servers/EMGC_ADMINSERVER/upload/jammanagerEMGC_JVMD

MANAGER1/app/jammanager.ear

9. On the filesystem, navigate to the Source Path you noted in the previous step and replace the

existing jammanager.ear with the jammanager.ear from

$MIDDLEWARE_HOME/plugins/oracle.sysman.emas.oms.plugin_12.1.0.2.0/archives/jvmd/.

10. Click Next to complete the update.

11. If you have Middleware Diagnostics Advisor (MDA) enabled, disable it for every Oracle WebLogic

Domain and Oracle WebLogic Server target it has been enabled for.

o In Cloud Control, navigate to the target home page for a WebLogic Server domain.

o From the WebLogic Domain menu, select Diagnostics, then select Setup Middleware

Diagnostics Advisor.

o Select each target that MDA has been enabled for, then click Disable.

12. Undeploy existing JVMD Agents from the target server. Agents will usually have names such as:

javadiagnosticManagement Agent_<ServerName>

13. Remove the corresponding Java Virtual Machine targets using Enterprise Manager Cloud

Control:

I. In Cloud Control, from Targets menu, click Middleware.

II. Locate the Java Virtual Machine targets that correspond to the JVMD Agents you un-

deployed in the previous step.

III. Select each Java Virtual Machine target in the table, then click Remove.

14. Redeploy all JVMD Agents. For instructions, see:

http://docs.oracle.com/cd/E24628_01/install.121/e22624/jvmd_installation.htm#CHDCFFG

C

15. After all JVMD Agents have been redeployed, return to the Middleware Diagnostics Advisor

Configuration page and re-enable MDA for each target it was previously enabled for.

Update Existing Agent Image to Agent Image with BP1 included

Follow the below steps to update your existing downloaded agent image in your environment to agent

image with BP1 included. Once you update your agent image following the below steps you will not be

required to apply any BP1 patches to the agents that will be installed using this updated image.

Note: At present we have updated agent image with BP1 included available for Linux32 and Linux 64 bit

platform only. As and when we release agent binaries with BP1 included for other platforms repeat the

following steps to update them for other platforms.

The version of agent binaries with BP1 included is same as earlier 12.1.0.1.

A. OMS and Target Management Agent Hosts are of the same platform

1. Download the agent zip file from OTN: http://www.oracle.com/technetwork/oem/grid-

control/downloads/oem-upgrade-console-502238.html

2. Copy this zip into OMS_HOME/sysman/agent directory.

Note: For multi OMS case, copy into all OMSes Oracle home

B. OMS and Target Management Agent Hosts are on different platforms

1. Log into the 12.1 console

2. Navigate to Self update page

3. You will view the Self Update home page

4. Select the Agent Software entity and click on open

5. You view the Agent Software update page. It list down various agent platform binaries

status.

6. Select the platform for which you want update the binaries. In this example let’s select Linux

x86 binaries, as we have Linux x86 agent binaries out with Bundle Patch 1 included and now

you want to update the existing Linux x86 agent binaries with the new ones.

Select the Linux X86 binaries and click on Action -> Remove

7. You will get a pop-up for the confirmation. Select Remove

8. A job get trigger to remove the agent binaries from the library

9. Once the job is done the page is refreshed and you see that select agent binaries status is

changed to Downloaded In this example you Linux x86 binaries status is “Downloaded “

10. Select the row with status Downloaded and Click Action -> Delete

11. Confirmation pop-up appears , select Delete

12. Once the above step is done and page is refreshed you will no longer see the selected agent

binaries in the library. In this example you will not see the Linux x86 binaries

13. If you want to delete the agent binaries which are in Available status then select the row

and click on Action -> Delete. In this example let’s take Linux x86-64 agent binaries

14. Confirmation pop-up appears , select Delete

15. Once the above steps is successful, you will no longer see the agent binaries for the selected

platform in the library. In this example , you will not see Linux x86-64 binaries

16. Go to the Self Update page and select the agent software entity and click on check update

to get the latest agent binaries.

17. A job will get triggered and once it’s done you will see “Available updates “column updated.

Troubleshooting

Refer to My Oracle support Note to know about troubleshooting Tip and list of know issues while

applying the Bundle Patch1.

Enterprise Manager Cloud Control 12.1.0.1 Bundle Patch 1 Known Issues (Doc ID 1395640.1)