ORACLE EM DBA

Problems, Solutions, Test Cases from my professional and personal experience in technologies like Oracle Enterprise Manager 13 c,Oracle Enterprise Manager 12c, Oracle Configuration Manager and some other stuff.

Month: October 2016

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

Moved WordPress blog to my website “emdeepaksharma.com”

Readers,

I have moved my WP blog to my new website “emdeepaksharma.com”, I am publishing all my new posts over there, hope you will like this. Need you support and suggestions are always welcome.

Thanks

Deepak Sharma

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

© 2017 ORACLE EM DBA

Theme by Anders NorenUp ↑