Author Archives: sharmadeepak345

Host Monitoring using Oracle Enterprise Manager 13c [Webinar]

In this blog I have shared the recent webinar which I did for “AIOUG-North India Chapter“. This webinar is related to the “Host Monitoring” using 13c Cloud Control. More details about this session is mentioned below. In-case you have missed it, you can watch the recorded session on YouTube Page of “AIOUG-North India Chapter”.

Session Details:-

Abstract: In this session we will learn how effectively you can monitor servers/hosts in your organization through new “Oracle Enterprise Manager 13c Cloud Control”. Some New features which were missing in previous release 12c Cloud Control.

Profile: Deepak Sharma is working as Sr. Application Administrator I, with experience of 7+ years. He has worked on technologies like Oracle Enterprise Manager 11g Grid Contol, Oracle Enterprise Manager 12c Cloud Control, Oracle Enterprise Manager 13c, Oracle Database, Oracle Configuration Manager and Sql Server. He is currently working with “Oceaneering International Inc.” from last 5 years and before that he has been employee of “Bebo Technologies” for 2 years. He is Co-Founder of AIOUG-North India Chapter and core team member of AIOUG.

Webinar URL: https://www.youtube.com/watch?v=58s_Mf-k7m0

Demo URL: https://www.youtube.com/watch?v=ECNOpfQTCn8

 

AIOUG NI Chapter-Over The WWW

Youtube: https://www.youtube.com/user/aiougnic

Official Website: http://www.aioug.org/NorthIndiaChapter.php

Facebook: https://www.facebook.com/AIOUG.NIC

Twitter: https://twitter.com/nichapter_aioug

Blog: https://aiougnic.wordpress.com/

Google+ : https://plus.google.com/+AIOUGNorthIndiaChapter/

Do subscribe to our pages for regular updates.

Thanks

ADDKS

Step by Step document to Apply PSU to OEM12c

In this document I have mentioned the step by step process which you have to follow in order to apply PSU to OEM12c. The example shown in this document is for OEM12cR4 which is my current environment. I have documented this process as the step involved are slightly different that normal steps for database patching, OMS patching involves some additional steps.

 

Step 1: Check OMS Details as it will be needed in later steps.

Download the latest PSU from Oracle Support and move it to OEM Server.

Step 2: Check OMS Details as it will be needed in later steps.

[oracle@hanoemap1 bin]$ ./emctl status oms -details

Oracle Enterprise Manager Cloud Control 12c Release 4

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

Enter Enterprise Manager Root (SYSMAN) Password :

Console Server Host : hanoemap1.emdeepaksharma.com

HTTP Console Port : 7790

HTTPS Console Port : 7803

HTTP Upload Port : 4890

HTTPS Upload Port : 4904

EM Instance Home : /app/oracle/product/middleware/gc_inst/em/EMGC_OMS1

OMS Log Directory Location : /app/oracle/product/middleware/gc_inst/em/EMGC_OMS1/sysman/log

OMS is not configured with SLB or virtual hostname

Agent Upload is unlocked.

OMS Console is unlocked.

Active CA ID: 1

Console URL: https://hanoemap1.emdeepaksharma.com:7803/em

Upload URL: https://hanoemap1.emdeepaksharma.com:4904/empbs/upload

 

WLS Domain Information

Domain Name : GCDomain

Admin Server Host : hanoemap1.emdeepaksharma.com

Admin Server HTTPS Port: 7103

Admin Server is RUNNING

 

Oracle Management Server Information

Managed Server Instance Name: EMGC_OMS1

Oracle Management Server Instance Host: hanoemap1.emdeepaksharma.com

WebTier is Up

Oracle Management Server is Up

 

BI Publisher Server is Up

BI Publisher Server named ‘BIP’ running at local URL: https://hanoemap1.emdeepaksharma.com:7803/xmlpserver

BI Publisher Server Logs: /app/oracle/product/middleware/gc_inst/user_projects/domains/GCDomain/servers/BIP/logs/

BI Publisher Log : /app/oracle/product/middleware/gc_inst/user_projects/domains/GCDomain/servers/BIP/logs/bipublisher/bipublisher.log

[oracle@hanoemap1 bin]$

 

Step 3: WebLogic encrypted configuration and key files.

Create directory to store property file.

[oracle@hanoemap1 ~]$ cd /app/oracle/product/middleware/oms12cr4/oms/

[oracle@hanoemap1 oms]$ mkdir -p oms_encr

Run the following script to create the WebLogic encrypted configuration and key files.

<OMS_HOME>/OPatch/wlskeys/createkeys.sh –oh <full path of platform OMS Oracle Home> -location <location to put the encrypted files>

[oracle@hanoemap1 bin]$ cd /app/oracle/product/middleware/oms12cr4/oms/OPatch/wlskeys

[oracle@hanoemap1 wlskeys]$ ./createkeys.sh -oh /app/oracle/product/middleware/oms12cr4/oms -location /app/oracle/product/middleware/oms12cr4/oms/oms_encr

Please enter weblogic admin server username: weblogic

Please enter weblogic admin server password: formula1

Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Creating new key…

Trying to get configuration and key files for the given inputs…

This operation will take some time. Please wait for updates…

User configuration file created: /app/oracle/product/middleware/oms12cr4/oms/oms_encr/config

User key file created: /app/oracle/product/middleware/oms12cr4/oms/oms_encr/key

‘createKeys’ succeeded.

[oracle@hanoemap1 wlskeys]$

Step 4: Create the property file with the following entries:

Enter the details of the WebLogic Administrator Server URL retrieved in STEP 1

WLS Domain Information

Domain Name : GCDomain

Admin Server Host : hanoemap1.emdeepaksharma.com

Admin Server HTTPS Port: 7103

Admin Server is RUNNING

 

The output displayed contains the WebLogic Adminstrator Server details. Here is an example on how to construct the URL with these output details. Property file should contain below mentioned information and should look similar to the following once completed:

AdminServerURL=t3s://<host address from where admin server is running>:<port of the admin server>

AdminConfigFile=<‘config’ file location>

AdminKeyFile=<‘key’ file location>

 

Following is the example of how a property file (constructed by the above mentioned guidelines) should appear:

AdminServerURL= https://hanoemap1.emdeepaksharma.com:7103

AdminConfigFile=/app/oracle/product/middleware/oms12cr4/oms/oms_encr/config

AdminKeyFile=/app/oracle/product/middleware/oms12cr4/oms/oms_encr/key

 

Create directory for property file followed by creation of text file as mentioned below

mkdir –p  /app/oracle/product/middleware/property_file

cd /app/oracle/product/middleware/property_file

vi property_file.txt

 

Add below mentioned entries in “property_file.txt”

AdminServerURL= https://hanoemap1.emdeepaksharma.com:7103

AdminConfigFile=/app/oracle/product/middleware/oms12cr4/oms/oms_encr/config

AdminKeyFile=/app/oracle/product/middleware/oms12cr4/oms/oms_encr/key

 

Step 5: Analyze the PSU

Make sure you have the latest OPatch for your OMS. The analyze process will fail with error if the OPatch is not latest.

Run the following command on OMS instance home to ensure that you do not have any issues with configuration and binary prerequisite checks. Please note: the OMS should be online when you do this step only.

export ORACLE_HOME=$OMS_HOME

export PATH=$ORACLE_HOME/OPatch:$ORACLE_HOME/bin:$PATH:

Navigate to the patch folder and analyze the patch.

[oracle@hanoemap1 middlware]$  cd /app/oracle/product/middleware/oms12cr4/oms/22132672

While Installing the System patch

$ opatchauto apply -analyze  [–property_file <location of property file>]

[oracle@hanoemap1 22132672]$$ opatchauto apply -analyze -property_file “/app/oracle/product/middleware/property_file/property_file.txt”

[oracle@hanoemap1 22132672]$ opatchauto apply -analyze -property_file /app/oracle/product/middleware/property_file/property_file.txt -invPtrLoc /app/oracle/product/middleware/oms12cr4/oms/oraInst.loc  OPatchAuto.OMS_DISABLE_HOST_CHECK=true

 

OPatch Automation Tool

Copyright (c) 2014, Oracle Corporation.  All rights reserved.

OPatchauto version : 11.1.0.12.9

OUI version        : 11.1.0.12.0

Running from       : /app/oracle/product/middleware/oms12cr4/oms

Log file location  : /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/opatch2017-01-20_16-45-34PM_1.log

OPatchauto log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatchauto/22132672/opatch_oms_2017-01-20_16-45-36PM_analyze.log

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) “22132672” and Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”…

Please monitor OPatch log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/22132672_Jan_20_2017_16_45_34/ApplyPrereq2017-01-20_16-46-55PM_2.log

Sub-patch(es) “22132672” are successfully analyzed for Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”

Complete Summary

================

All log file names referenced below can be accessed from the directory “/app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/2017-01-20_16-45-34PM_SystemPatch_22132672_1”

Prerequisites analysis summary:

——————————-

The following sub-patch(es) are applicable:

  Oracle Home Name   Sub-patches                                     Log file

  —————- ——–  ———–                                          ——–

           oms12c3            22132672                                         22132672_ApplyPrereq2017-01-20_16-46-55PM_2.log

Log file location: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatchauto/22132672/opatch_oms_2017-01-20_16-45-36PM_analyze.log

OPatchauto succeeded.

[oracle@hanoemap1 22132672]$

 

Step 6: On Successful analysis, Apply PSU. If not, address the errors, then proceed with next steps.

Stop OMS

[oracle@hanoemap1 22132672]$ emctl stop oms

Oracle Enterprise Manager Cloud Control 12c Release 4

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

Stopping WebTier…

WebTier Successfully Stopped

Stopping Oracle Management Server…

Oracle Management Server Successfully Stopped

Oracle Management Server is Down

 

Apply Patch

[oracle@hanoemap1 22132672]$ opatchauto apply -property_file /app/oracle/product/middleware/property_file/property_file.txt

 

OPatch Automation Tool

Copyright (c) 2014, Oracle Corporation. All rights reserved.

OPatchauto version : 11.1.0.12.9

OUI version : 11.1.0.12.0

Running from : /app/oracle/product/middleware/oms12cr4/oms

Log file location : /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/opatch2017-01-20_17-04-10PM_1.log

OPatchauto log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatchauto/22132672/opatch_oms_2017-01-20_17-04-11PM_deploy.log

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) “22132672” and Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”…

Please monitor OPatch log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/22132672_Jan_20_2017_17_04_10/ApplyPrereq2017-01-20_17-05-37PM_2.log

Sub-patch(es) “22132672” are successfully analyzed for Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”

To continue, OPatchauto will do the following:

[Patch and deploy artifacts] : Apply sub-patch(es) [ 22132672 ] to Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”;

Apply RCU artifact with patch “/app/oracle/product/middleware/oms12cr4/oms/.patch_storage/22132672_Dec_16_2015_23_31_36/original_patch”;

Register MRS artifact “omsPropertyDef”;

Register MRS artifact “procedures”

Do you want to proceed? [y|n]

y

User Responded with: Y

Applying sub-patch “22132672” to Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”…

Please monitor OPatch log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/22132672_Jan_20_2017_17_04_10/apply2017-01-20_17-07-53PM_4.log

Updating repository with RCU reference file “/app/oracle/product/middleware/oms12cr4/oms/.patch_storage/22132672_Dec_16_2015_23_31_36/original_patch”

Registering service “omsPropertyDef” with register file “/app/oracle/product/middleware/oms12cr4/oms/sysman/metadata/omsProperties/definition/BIPHAPropDefinition.xml”…

Registering service “procedures” with register file “/app/oracle/product/middleware/oms12cr4/oms/sysman/metadata/procedures/linuxpatch/PatchLinux.xml”…

Registering service “procedures” with register file “/app/oracle/product/middleware/oms12cr4/oms/sysman/metadata/procedures/linuxpatch/ULNPatchLinux.xml”…

 

Complete Summary

================

All log file names referenced below can be accessed from the directory “/app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/2017-01-20_17-04-10PM_SystemPatch_22132672_1”

Patching summary:

—————–

Binaries of the following sub-patch(es) have been applied successfully:

Oracle Home Name Sub-patches Log file

—————- ———– ——–

oms12c3 22132672 22132672_apply2017-01-20_17-07-53PM_4.log

Deployment summary:

——————-

The following artifact(s) have been successfully deployed:

Artifacts Log file

——— ——–

SQL rcu_applypatch_original_patch_2017-01-20_17-08-57PM.log

MRS-omsPropertyDef emctl_register_omsPropertyDef_2017-01-20_17-10-38PM.log

MRS-procedures emctl_register_procedures_2017-01-20_17-10-43PM.log

MRS-procedures emctl_register_procedures_2017-01-20_17-10-48PM.log

Log file location: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatchauto/22132672/opatch_oms_2017-01-20_17-04-11PM_deploy.log

OPatchauto succeeded.

 

Start OMS

[oracle@hanoemap1 22132672]$ emctl start oms

Oracle Enterprise Manager Cloud Control 12c Release 4

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

Starting Oracle Management Server…

Starting WebTier…

WebTier Successfully Started

Oracle Management Server Successfully Started

Oracle Management Server is Up

Starting BI Publisher Server …

BI Publisher Server Already Started

BI Publisher Server is Up

[oracle@hanoemap1 22132672]$

 

Step 7: Verify Applied Patches

 

[oracle@hanoemap1 22132672]$ opatch lsinventory

Oracle Interim Patch Installer version 11.1.0.12.9

Copyright (c) 2017, Oracle Corporation. All rights reserved.

Oracle Home : /app/oracle/product/middleware/oms12cr4/oms

Central Inventory : /app/oracle/oraInventory

from : /app/oracle/product/middleware/oms12cr4/oms/oraInst.loc

OPatch version : 11.1.0.12.9

OUI version : 11.1.0.12.0

Log file location : /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/opatch2017-01-20_18-29-52PM_1.log

OPatch detects the Middleware Home as “/app/oracle/product/middleware/oms12cr4”

Lsinventory Output file location : /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/lsinv/lsinventory2017-01-20_18-29-52PM.txt

——————————————————————————–

Installed Top-level Products (1):

EM Platform (OMS) 12.1.0.4.0

There are 1 products installed in this Oracle Home.

Interim patches (1) :

Patch 22132672 : applied on Fri Jan 20 17:08:47 EST 2017

Unique Patch ID: 19559467

Patch description: “EMBP Patch Set Update 12.1.0.4.160119”

Created on 16 Dec 2015, 23:31:36 hrs PST8PDT

Bugs fixed:

20010360, 20346629, 18599481, 19459173, 20646440, 18830050, 18244680

19614772, 20492788, 18932882, 20646540, 19355307, 20263906, 20556489

20106145, 14301574, 18721562, 17714229, 19328391, 19535114, 19861538

19794113, 19604817, 20596437, 19892848, 19218456, 19978077, 18505219

17843191, 20345612, 20748748, 20024779, 18256983, 19329809, 19300103

17987955, 18351725, 18903783, 19430853, 19845101, 20870437, 20421152

20223681, 21437683, 20019184, 20263188, 19069940, 21545754, 19861412

19136663, 18446798, 19474685, 18765545, 18038059, 17783148, 19509780

20838602, 18041873, 19030447, 20861693, 20933667, 19574756, 19258481

18938561, 17812648, 20377474, 20251039, 19572261, 18945007, 20307428

18388324, 19500609, 20751948, 22324488, 17991694, 19137411, 20369347

19474929, 19592446, 18710124, 20536095, 21358443, 19352118, 19557054

18726708, 19595813, 19170861, 19685443, 18353162, 19289270, 19367214

18906451, 19458672, 20284029, 18490444, 19766881, 20021966, 18509136

20739088, 21450977, 18695961, 19511544, 19812966, 20093530, 20576148

20806405, 20623258, 19055251, 19586898, 20260177, 19323634, 21462217

19941819, 18725891, 19824587, 20672821, 19780847, 18359621, 21067380

19393211, 19211048, 20505155, 18476364, 18490468, 18247849, 19071602

19068674, 18490455, 19524568, 20616490, 19061168, 19077861, 20031287

18756725, 19281252, 21061986, 18977955, 18485889, 20695395, 18521731

18411036, 19775544, 18900197, 17834366, 20460507, 19545505, 21330117

19823996, 20645335, 20633770, 17407918, 18706824, 20568225, 18805935

19376082, 19146514, 21429472, 20985421, 18490432, 18230284, 19694744

18726208, 20044313, 18516298, 18391707, 20642633, 18999400, 20692416

19362386, 20392036, 21495795, 19452280, 20623344, 21093418, 22132672

18356966, 19055979, 20617058, 19830994, 20030493, 19823761, 18834216

19196979, 19785223, 18389542

——————————————————————————–

OPatch succeeded.

[oracle@hanoemap1 22132672]$

 

Hope this document will help you apply patches in your OEM12c environment.

 

Thanks

ADDKS

Automatically create Service Request on MOS from OEM13c

This is step by step document to create Service Request on My Oracle Support for any open problem in Oracle Enterprise Manager. The Service Request will be created from within OEM itself and all required details and log files etc. will automatically be uploaded.

Note: I assume that you already have “Oracle Configuration Manager” configured for OEM environment.

Step 1: Navigate to Incident Manager

Login to the OEM13c console and Navigate to Incident Manager. Under Incident Manager as shown in the screenshot in the left panel Click on “All Open Problems”. Select the problem for which you want to open the “Service Request”. In the detail window on the bottom half of the screen under “Actions” click on “Support Workbench Package Diagnostic

image0

clip_image002

Step 2: Login to Support Workbench

Next step is to provide the credentials of “Weblogic Host” {OMS Host} and “Weblogic Server”. As shown in the screenshot please use your PRV account named credentials to login to weblogic host. “Weblogic Server” credentials are already saved, please use the same credentials. “WLS_EMGC_GCD

image0_1clip_image004

Step 3: Select Packaging Mode.

In this step please select the type package {Quick or Custom} you want to upload on My Oracle Support. It is preferred to use “Quick Packaging”, it will upload all the required files together as one package.

image0_2clip_image006

Step 4: Create Package

Enter the required details as mentioned in the screenshot for the package. This includes “Package Name, description, MOS option, Create new SR, CSI, and SR Summary”. Once all the details are filled click on “Next”.

image1clip_image008Once you click on Next it will compile up all the logs and other information in the single package to upload on My Oracle Support.

image2

Step 5: View Contents of Package

This step simply lists the Incidents which are included in this package. Click on “Next” to proceed.

image3clip_image012

Step 6: View Contents of Manifest file.

It lists all the details of the manifest file to be uploaded on the My Oracle Support. If you want you can review the contents and then click on “Next” to proceed.

image4clip_image014

 

Step 7: Schedule the package.

In this step, you can select the schedule for generating an upload file and send it to “My Oracle Support”. You can either do it “Immediately” or schedule it for later time. Click on “Submit” to finish the process.

image5

image6clip_image016

Step 8: Confirmation

This screen shows that SR has been successfully created on MOS, but please note that this is a “DRAFT” service request. You have to login on MOS with your account and submit this SR manually.

image7clip_image018

image8clip_image020

 

Stay connected for more stuff on OEM13c…

 

Thanks

ADDKS

OEM13c Release 2 Step by Step Upgrade

This is the step by step document to upgrade OEM12cR4 to OEM13cR2. Mentioned below are some important prerequisites, make sure to you do not skip anyone of them before starting your upgrade.

Prerequisites

· Check the certification matrix to make sure your existing environment is certified for this upgrade. I have already gather the required details.

· EM13cR2 OMS requires Oracle 12.1.0.2 as repository database.

· EM13cR2 agents don’t support Enterprise Linux earlier than version 6.

· Back up your repository database and OMS.

· Another important point to take is the timezone of Repository Database and OMS machine. Since in our case we have both OMS and Database on the same machine so it does not matter. However if the timezone is not same then, Upgrade will fail at ‘Plug-ins Perquisites check’ step.

 

Certification Matrix

certification_matrix13cr2

Since our Existing environment is on RHEL Linux 6 so the certification matrix is based on that.

certification_matrix13cr2_1

There are few plugin’s which have been obsoleted in new release 13c. Check if there are any obsolete plug-ins in your current system. Un-deploy obsolete plugins if exists both from OMS and Agent before proceeding with upgrade to EM13.2:

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

 

Upgrade Process.

Step 1: Copy EMKey to the Management Repository.

Note: EMKey is used during upgrade, EM13c will need to access EMKey. { secret key to encrypt password}

$OMS_HOME/bin/emctl config emkey -copy_to_repos

Step 2: Make sure you have “optimizer_adaptive_features” disabled in your repository database, if not run the below mentioned SQL command.

SQL> alter system set optimizer_adaptive_features=false scope=spfile;

 

Step 3: If you have upgraded your database recently, make sure that database compatibility parameter equal to the database version.

SQL> alter system set compatible=”12.1.0.2.0″ scope=spfile

To make the new changes take effect, please restart your database.

Step 4: Download the OEM13cR2 Setup from Oracle Website. Use the below mentioned URL to download 6 files included in setup.

http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-linux64-3237624.html

Step 5: Copy Software on the installation server.

Make you copy all 5 files in one single folder. NOTE: Please do not unzip any file, EM13c installation doesn’t need you to unzip the files. In EM13c we have “em13200_linux64.bin” as executable we have to run this file as “oracle” user.

image1

Step 6: Run the Setup and enter MOS Details.

image2

 

The first screen that pops-up will request your credentials for MOS. This is optional not mandatory if you want to receive updates from Oracle you can put your credentials or you can leave it blank as well. “CLICK NEXT” to proceed.

Step 7: Software Update (Optional)

Next step is the software update window, here you will be prompted if you want to check for any new updates available for your new release on which you ware upgrading. Since 13c is released recently so it already contains all latest updates, still if you want to check you can do that by simply providing your MOS credentials as shown below in the screenshot.

image3

image4

Step 8: Pre-requisite Checks

At this step setup performs a check to make sure all the pre-requisites are passed successfully. Make sure you do not have Warning or Failed status for any one of the pre-requisites. Some warnings can be ignored but make you fix the “Failed” pre-requisites before proceeding to the next step as it can FAIL you upgrade later.

image5

 

Step 9: Installation Types

In this step you will be prompted to select the “Installation Type”, since we are doing the upgrade we will select “Upgrade as existing Enterprise Manager System”. For upgrade there is only one option available “One-System Upgrade”.

Select the radio button as shown in the screenshot below and click on “NEXT”.

image6

 

Step 10: Installation Details.

In this step you will be prompted to enter the middleware home location for new Oracle Enterprise Manager 13c. Make sure you provide the correct location as this is the directory where all binaries for OEM13c going to be stored.

image7

 

Step 11: Database Connection Details.

Here you have to provide the connection details for your OMR database. Since we are doing the upgrade of our existing environment, “Connect Descriptor” field is already filled. You have to provide “SYS and SYSMAN” passwords.

image8

EM13c gives as option to disable DDMP during the upgrade.

If you are planning to stop your EM for POST upgrade maintenance then it is recommended to DISABLE DDMP jobs. Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the historical data of your old Enterprise Manager. Depending on how much data stored, it may take same time.

Also, before proceeding to next step make you have you have already backed-up your OMR. Select the check-box and click on “NEXT”.

Before you proceed, make sure you have applied latest PSU on your database to avoid failure during your repository upgrade.

Note: If you haven’t stopped the OMS and agent running on your OMS and OMR server (if OMS and database are on separate machines) , please stop them now. Once OMS and Agent are down then click on NEXT.

Run the below mentioned commands to stop OMS and Agent respectively.

$OMS_HOME/bin/emctl stop oms -all
$AGENT_HOME/agent_inst/bin/emctl stop agent

Although you stop the agents, you may still get a warning about them. Ignore it and continue to upgrade.

 

Step 12: Database Configuration Check.

When you click on “NEXT” in “Database Connection Details” window in the last step, it performs come checks for the existing database.

image9

image10

 

You may or may not receive warning depending on your database configuration.

image11

Some of the warnings can be fixed automatically by the installer when you click “YES”, some of them you have to fix manually. In-order to avoid your upgrade to FAIL in middle make sure you fix all the warnings and then click “NEXT”.

image12

 

Step 13: Plug-in Upgrade, select additional Plug-in’s if you want to install any of them during this installation..

This displays all your existing plug-ins which will be upgraded during this process. Please read thoroughly and click on “NEXT”. Also if you want to install and additional plugin’s in this install, select from the list.

image13

 

Step 15: Enter Weblogic Details

Please enter the details of Weblogic server for your OEM13c installation. Make sure you choose new location for your OMS instance outside your Middleware home. Also enter your weblogic password.

image14

 

Step 16: Shared Location Details for BI Publisher

If you already had BI Publisher installed and configured in your existing environment then BI Publisher automatically gets upgraded during upgrade to OEM13c. The checkbox shown in the below screenshot will be checked and grayed out by default only if BI Publisher is already configured.

image15

 

Step 17: Ports Configuration

Do not make any changes until the mentioned ports are already being used. Accept the default ports and click on NEXT.

image16

 

Step 18: Review Details

Review the information you entered, and then click the upgrade button to start upgrade process. The time for this upgrade will depend on hardware of your system.

image17

image18

image19

image20

image21

Step 19: Run root.sh script as ROOT user to complete the installation. [root.sh script is located in the middleware home]

image22

 

Step 20: Final & Final Details

image23

 

Step 21: POST Upgrade Steps.

Login to your 13c console using the sysman user and perform the POST-upgrade tasks. Navigate to the “upgrade agents” page under the “setup menu” to upgrade your agents.

13c_console

license

home_pagehome_page

 

Regards

ADDKS

Oracle Enterprise Manager Cloud Control 13c Release 2 (13.2.0.0) available now

I am not now sure how many of you are aware that Oracle Enterprise Manager 13c Release 2 is available now for those who are not I have mentioned few of the Important URL’s for OEM13cR2 which might help you if you are planning to install or upgrade to this new release.

Certification Matrix of OEM13cR2 for RHEL 6

Download Link for OEM13cR2

OEM Cloud Control Upgrade Guide

Prerequisites for Upgrading to Enterprise Manager Cloud Control 13c Release 2

 

Soon I’ll be publishing new post Step by Step Upgrade guide to Cloud Control 13c Release 2.

 

Thanks

ADDKS

Offline Database Patching in OEM12c

 

This is the step by step document of how you do database patching from OEM. Before we start I’ll just give small introduction about Patching in OEM.

There are two different methods by which we can do patching in OEM:

● Out-Of-Box Patching

● In-Place Patching

Out-Of-Box patching is the recommended method by Oracle, the advantage of using this method is that it reduces your downtime. On the contrary you need to have some extra (almost double to you ORACLE_HOME) space on your disk as this method CLONE your ORACLE_HOME so that in case of failure revert back is easily possible.

In-Place patching is also known as Offline patching, in this method downtime is more as compare to Out-Of-Box patching. So if you have planned maintenance window you can easily adopt this method.

In this blog we will be performing In-Place patching. So let’s see what are some prerequisites required before patching your database.

 

Required Roles and Permission:

● EM_PATCH_DESIGNER

● EM_PATCH_OPERATOR

● EM_PATCH_ADMINISTRATOR

 

Step 1: Create Normal and Privilege Credentials for Host

Before we start with the patching process make sure we have “Normal and Privilege” credentials set. Login to OEM console and create Normal and Privilege credentials if already not created.

Navigate to “Setup -> Security -> Named Credentials ”

clip_image002[5]

Click on Create and put the required Details.

 

clip_image004[5]

Make sure you TEST credentials before you SAVE them. So that the credentials are validated.

 

clip_image006[5]

 

Step 2: Download Patches and Upload them to Software Library.

Download the patches to be applied from MOS and upload them to Software Library. Navigate to “Enterprise -> Provisioning and Patching -> Saved Patches” and follow the below mentioned steps.

 

clip_image008[9]

 

clip_image010[6]

 

clip_image012[4]

 

Step 3: Check Recommended Patches and their details.

In order to check the recommended patches and details about them. Login to OEM using your credentials and Navigate to “Patching” Home Page as shown in the screenshot below. (Enterprise -> Provisioning and Patching -> Patches & Updates)

 

clip_image014[4]

 

Patch Recommendations Details are shown on this homepage in the bottom left corner. (Classification View)

 

clip_image016[4]

 

You can either see the details by selecting Classification View as shown in the above screenshot or by Target View as shown below. Else we also have “All Recommendations” link as well which will show all details together.

(Target View)

clip_image018[4]

 

Click on “Database Instance” to check recommended patches. Patches are displayed in the form of table with details like Patch Name, Description, Release, Platform etc.

If you further want to check information for specific patch, select the particular patch row and further details like SPU’s include, Bugs resolved will be displayed below. You will also get the option to download the patch or add to Patch Plan.

 

clip_image020[4]

 

If you click on “All Recommendation” link on the “Patches & Updates” Home page you will get something like this . All patches for different targets clubbed together in single table.

 

clip_image022[4]

 

Particular Patch Details

Click on single row to check the details about that patch.

 

clip_image024[4]

 

Step 4: Create a Patch Plan and add patches

After we have confirm the patches to be applied and their details. Next step is to add particular patch to a Patch Plan. Select a particular row and Click on “Add to Plan” followed by “ Add to New ” as shown in the below screenshot.

 

clip_image026

 

Create New Plan pop-up window will open, please enter a meaningful name and click on “Create Plan” button.

 

clip_image028

 

Now Click on “View Plan” to check the Plan details.

 

clip_image030[4]

 

Step 5: Deploy Patch

Patch deployment is a 5-step process,

1. Plan Information

2. Patches

3. Deployment Options

4. Validations

5. Review & Deploy

Once you have created a Patch Plan, follow the above mentioned process and step by step and at last deploy the patch.

 

Plan Information

This step involved Plan description and the permissions, Enter the plan information details followed by granting permissions to existing users.

 

clip_image032[4]

 

Patches

In this step you can add multiple patches to existing Patch Plan.

clip_image034[4]

You can search the patches in three different ways, using Patch Number, using Advanced Method or by Recommended Patch Advisor.

clip_image036[4]

Deployment Options

This is further multi-step process. Screenshot for each step is show below.

How to Patch {In Place or Out-Of-Box method}

What to Patch {Database Instance Targets details}

Where to Stage {Location of staging directory}

Credentials Information {Host Credentials with sudo permissions}

Customization

Notification {Email notifications phase}

Rollback {Rollback option in-case of failure}

Conflict Check {If any existing patch is conflicting}

clip_image038[4]

 

Select the tested Named Credentials and Privilege Credentials for the host on which you are deploying the Patch. Do not forget to Validate them.

Make sure “Named Credentials and Privilege Credentials” are different if your OEM is 12.1.0.4.0 as there is BUG reported in OEM12cR4.

 

clip_image040

Verify effected Database Instance Targets and Staging Directory by default it goes to “%emd_emstagedir%” directory.

 

clip_image042

 

Verify Customization, Notification, Rollback and Conflict Options before proceeding further.

clip_image044

 

Validation

Click on the “Analyze” button to start the Validation process, this process can take time depending on the Patches and Targets involved.

clip_image046

clip_image048

Check if any Issue remains even after Validation, Review them and then resolve them before proceeding further.

clip_image050

In-case there is some failures like I got the one shown below during the Review Process, make sure you fix them and then proceed with the “Deployment” process.

clip_image052

 

Review & Deploy

This is the last option, this page will display all information make sure you review the information thoroughly and if everything looks good click on “Deploy” button to start the deployment process.

 

Regards

ADDKS

Back to OEM Basics – Agent12c Blocked by OMS [Agent Resynchronization]

This blog is a part of my “Back to OEM Basics” series. In this I have explained in details how easily you can solve your “Agent blocked by OMS” issue. With the help of logs and screenshots I have made it more simple to understand.

Lets got step by step and see how you can fix your problem and can Unblock an blocked agent.


Oracle Agent usually gets blocked when it is Out-Of-Sync with the OMR repository database.

 

Step 1: How to check if agents are blocked, this can be simply done by login-in to OEM.

 

Please login to OEM and navigate to “Setup-> Manage Cloud Control –> Agents” as shown in the screenshot.

 

agent_blocked0

 

The “Manage Cloud Control” AGENTS home page will give you list all of the installed agents, you can sort the list using the “STATUS” column as shown in the below screenshot.

 

image1

 

Step 2: Login to Agent server and check the logs to verify the cause.

 

I checked agent logs on the server where agent was BLOCKED and this is what I found.

 

Agent Logs:-

2016-09-20 10:13:04,906 [9825:547A0FF8:GC.SysExecutor.1036 (Ping OMS)] INFO - attempting initial heartbeat

2016-09-20 10:13:04,919 [9825:547A0FF8] INFO - The agent has been blocked by the OMS.

2016-09-20 10:13:04,919 [9825:547A0FF8] INFO - Reason the OMS blocked the agent: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console.

2016-09-20 10:13:41,530 [9743:2F24D3F3] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@21a09189

2016-09-20 10:13:41,531 [9743:2F24D3F3] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@653b1740

2016-09-20 10:14:41,530 [9822:669C9195] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@354632cf

2016-09-20 10:14:41,531 [9822:669C9195] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@6cde3ddf

2016-09-20 10:15:41,532 [9836:6A4F37D3] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@39af50a4

2016-09-20 10:15:41,532 [9836:6A4F37D3] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@9bce0a

2016-09-20 10:16:04,938 [9759:755A5435:GC.SysExecutor.1028 (Ping OMS)] INFO - attempting initial heartbeat

2016-09-20 10:16:04,948 [9759:755A5435] INFO - The agent has been blocked by the OMS.

2016-09-20 10:16:04,948 [9759:755A5435] INFO - Reason the OMS blocked the agent: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console.

 

Step 3: Check status of agent by running “emctl status agent” command.

 

D:oracleproductagent12cr3agent_instbin> 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       : (unknown)

Protocol Version  : 12.1.0.1.0

Agent Home        : D:/oracle/product/agent12cr3/agent_inst

Agent Binaries    : D:oracleproductagent12cr3core12.1.0.2.0

Agent Process ID  : 3416

Parent Process ID : 2524

Agent URL         : https://HANHRRP3.oiiad.com:3872/emd/main/

Repository URL    : https://hanoemap1.oii.oceaneering.com:4904/empbs/upload

Started at        : 2016-09-16 22:43:30

Started by user   : HANHRRP3$

Last Reload       : (none)

Last successful upload                       : (none)

Last attempted upload                        : (none)

Total Megabytes of XML files uploaded so far : 0

Number of XML files pending upload           : 690

Size of XML files pending upload(MB)         : 1.13

Available disk space on upload filesystem    : 47.09%

Collection Status                            : Collections enabled

Heartbeat Status                             : Agent is blocked

Last attempted heartbeat to OMS              : 2016-09-20 10:43:05

Last successful heartbeat to OMS             : (none)

Next scheduled heartbeat to OMS              : 2016-09-20 10:46:05

—————————————————————

Agent is Running and Ready

 

Step 4: Navigate to Agent home page in Oracle Enterprise Manager Console to verify and rectify issue.

 

agent_blocked1

 

The error message in console as well clearly shows that agent is Blocked and need to “unblock” it manually.

 

Step 5: Navigate to “Resynchronization” under “Agent” on the home page as show in the screenshot below.

 

agent_blocked2

 

Step 6: Select unblock agent Under “Agent Resynchronization” make the checkbox is checked and click on “Continue”.

 

agent_blocked3

 

 

Step 7: This confirms that “Agent Resynchronization” job has been executued successfully.

 

You can monitor the progress of the job by clicking the Job Name {eg. RESYNC_20160920104720}

 

agent_blocked4

 

Step 8: Check RESYNC Job Details and verify  if it is completed.

 

agent_blocked5

 

Step 9: Navigate back to agent home page and verify Agent status.

It should be “UP & RUNNING” after the RESYNC job has completed successfully.

 

agent_blocked6

 

This way you can easily un-block all of your Blocked agents and make them again fit for monitoring your targets.

Stay tuned for more “BACK TO OEM BASICS” Topics.

 

Thanks

ADDKS

EM12c login FAILED for all users after database upgrade from 11.2.0.2 to 12.1.0.2

Two days back I ran into an issue where I was not able to login to my OEM12c test environment using any of the account. This happened after OEM database upgrade. Recently I did upgrade of my OEM database from 11.2.0.2 to 12.1.0.1 followed by upgrade to 12.1.0.2.

After upgrade was done successfully I tried to login to OEM using my account “dksharma” it gave me error, then I tried using the “sysman” but login failed again. All other users also  reported the same issue.

I have document all  my findings and solution to that in the attached document. If you also face the same Issue you use to document to fix your problem.

em12c-login-failed

Regards

ADDKS

 

Prerequisite for OEM12cR4 to OEM13cR1 upgrade

If you have Oracle Enterprise Manager 12cR3/12cR4/12cR5 running on either RHEL or OEL and you are planning to upgrade your OEM to new release of 13c you must make sure that you meet below mentioned requirements.

I have shortlisted few mandatory and minimum requirements which you should keep in mind  while planning to upgrade to Oracle Enterprise Manager 13c or fresh installation of OEM13cR1.

oem13c_upgrade_checklist

In my next blog I’ll put the complete step by step document for OEM13cR1 upgrade.

Share your feedback and stay connected for next blog.

Regards

ADDKS