In this paper we will see that the installation of a Patch Set Update using EM12c is as easy as 1,2,3

Installing Patch Set Update using EM12c

Checkout Incidents Rules in EM12c

Installing EMCLI on EM12c

Then after you would have created a new Database or any other Target Type, you would need to perform a discovery using the Agent that was monitoring the specific server.

Starting with Enterprise Manager 12c your Targets can get discovered automatically even if no Agent has been installed yet.

Auto Discovery in EM12c

Here is how to discover the EM 12c Repository Database

Discover EM12c Repository Database after Installation

The Provision Oracle Database Deployment Procedure takes care of all of this, so installing the Grid Infrastructure software and configuration, installing the Oracle Database software and the creation of the Database!

Provision Oracle Database using EM 12c

In the example I describe the creation of a Single Instance Database version 11.2.0.3, using the Grid Infrastructure.

Creating Oracle Database using EM 12c

I have been using the creation of a “Clusterware Clone” for the example, but creation of any other type will be a simular process.

Creating Golden Images in EM 12c Software Library

Configuring Oracle VM Manager in EM 12c

For instance, Administration Group “All Production Databases” would have automatically assigned a Database Target on the moment Target Property “Deployment Type” for this Database is set to “Production”.

In EM 11 (and earlier releases) we could use User Defined Metrics to extend the “out-of-box” monitoring capabilities. One of the drawbacks of User Defined Metrics in pre 12c releases is that they only applied to the Host and Database (Instance and Cluster Database) Target types.

EM 12c introduces Metric Extensions for the same goal, however supports any Target type.

Metric Extension Library

In EM 11 (and earlier releases) there isn’t a central location to store and maintain User Defined Metrics. A User Defined Metric could only be created as a Target related object, meaning you had to pick a certain Target (Host or Database) and create your UDM. Then by including your UDM in a Monitoring Template you would be able to deploy the UDM to other Targets.

By identifying one specific Host and one specific Database we would simulate a Library for our UDM’s. Normally this would be the OMS (Management Service) Server (or 1 of them when using multiple OMS’s) for Host UDM’’s and the OMR (Management Repository) Database Target for Database related UDM’s.

In EM 12c, a Metric Extension Library has been introduced for this purpose!

Events

An event is a single occurrence detected by EM and related to a single entity (well that is what the Administrator Guide tells us). Such a single entity could be: a Target, a Configuration File, a Job etc. Examples of an event include: Database Instance is down, Configuration File has been changed, Job executions ended in failure, Host exceeded a given percentage of CPU, Tablespace Space is exhausted etc.
No doubt this immediately makes the comparison with Metric Alerts in EM 11 (and before).

Incidents

When working in an IT environment that uses the ITIL (Information Technology Infrastructure Library) Best Practice processes and procedures, the term Incident does ring a bell doesn’t it? When searching for a definition of “Incidents” according ITIL in Wikipedia, you will find: “Incidents are the result of failures or errors in the IT infrastructure. The cause of Incidents may be apparent and the cause may be addressed without the need for further investigation, resulting in a repair, a Work-around or a request for change (RFC) to remove the error.”

EM 12c now allows us to make a definition of an Incident as a single or closely correlated set of events that identify a disturbance within our Data Center. So an Incident Definition might be as simple as the relation with a single Event “Available space in Tablespace has gone down a specified limit” or as more complex as an Incident “Server is running out of resources” that would be related to a set of Events relating to the usage of CPU, I/O and Memory Resources.

Integration with 3rd Party Helpdesk systems
Like we were used in EM 11 (and earlier release) EM 12c allows you to integrate with 3rd Party systems to for instance create a Ticket as result of an Incident occurrence.

Incident Rule Sets

As in EM 11 (and earlier) we used Notification Rules to initiate notification as a result of Alert creation for specific Events and specific Targets, EM 12c now provides us with Incident Rules and Incident Rule Sets to do so.

Incident Rules

Incident Rules actually perform the same role as Notification Rules

Incident Rule Sets

An Incident Rule Set allows you to combine multiple Incident Rules to a more extended control on Incident situations. As Incident Rules apply to objects like: databases, hosts, groups, jobs, web applications etc., by combining them in a Incident Rule Set you are able to take specific actions on a combination of objects and criteria.

Rules within a Rule Set can have a specific order in which each of them must be performed.

This example (based on an example in the Administrators Guide) shows the usage of Incident Rule Sets. The Set applies to a Group of Targets (of different types) and initiates multiple actions based on different criteria.

Out-of-Box Rule Sets

After installation of EM 12c the following “out-of-box” Rules Sets are available:

Incident Management Rule Sets for All Targets

• Incident creation Rule for target down.
• Incident creation Rule for target unreachable (for Agents and hosts).
• Incident creation Rule for metric alerts (for critical severity only).
• Out-of-box Incident creation rule for Service Level Agreement Alerts.
• Incident creation rule for compliance score violation
• Incident creation rule for high-availability events.
• Auto-clear Rule for metric alerts older than 7 days.
• Auto clear Rule for job status change terminal status events older than 7 days.
• Clear Application Dependency and Performance (ADP) alerts after without incidents after 7 days.

The Rules that are part of an Incident Rules Set are made out of two parts:

• Criteria
  The events/incidents/problems on which the Rule applies
• Action
  The Actions that should be performed in case the Criteria are met

The Administrators Guide gives some example Rule Set possibilities:
Rule Set:

• Applies to Target: Group Target G
• Rules in the Rule Set:
1. Rule(s) to create Incidents for specified Events
2. Rule(s) that send Notifications on the Incidents
3. Rule(s) that escalate Incidents based on some condition (e.g. length of time the Incident is open)

Rule Set (Details)
• Rule Set for Production Group G
• Target: Production Group G
• Rule 1: Create Incident for all Target down Events
• Rule 2: Create Incident for specific DB, Host or WLS Metric alert events of critical or warning severity
• Rule 3: Create Incident for any problem Job events
• Rule 4: For all critical Incidents, send page, for all warning Incidents send e-mail
• Rule 5: If Fatal Incident is op for more than 12 hours set escalation level to 1 and e-mail Manager

Event prioritizing

We all know that when using EM in a large IT landscape, having hundreds to thousands of targets, a heavy load of Incidents might be the result.

In such a case we would want to be able to prioritize. To allow such prioritizing EM 12c introduces: Target Life-cycle Status and Incident/Event Type.

Target Life-cycle

• Mission Critical (Highest priority)
• Production
• Stage
• Test
• Development (Lowest priority)

Incident/Event Type

• Availability (Highest priority)
• All Events/Incidents (Fatal severity)
• All Events/Incidents (Warning and Critical severity’s)
• All Events/Incidents (Informational) (Lowest priority)

• One ORACLE_HOME in which installed the most recent release of Oracle DB, for instance 11.2.0.2
• Several Database Instances running on the Oracle Software installed

If we want to apply a Patch to an environment like this we need to follow a scenario like this:

1. Download the Patch manually from MOS
2. Study the documentation
3. Check if the proper version of OPatch is available and upgrade if necessary
4. Clone the current ORACLE_HOME (you might be using a Golden Image in the EM Software Library for this)
5. Install the Patch on the cloned ORACLE_HOME
6. Stop database per database and copy necessary files (<oracle_home>/dbs/…)
7. Modify /etc/oratab to modify the path to the cloned ORACLE_HOME
8. Startup the database in the clone ORACLE_HOME
9. Execute necessary sql scripts

10. Check and document

Indeed an intensive and error prone scenario.

EM 10.2.0.5 and 11.1 provided us with a Patching procedure that was unable to cover this scenario.

EM 12c however now provide us with a procedure that takes care of this “Out-of-place” Patching procedure.

Starting with the support of Single Instances and RAC on Exadata, the support for RAC on clustered Servers is soon to follow (obviously as this is a more or less same procedure as the support for Exadata).

By this IT departments are able to perform a robust, complete patching procedure in which databases will be patched one by one with a minimum of down time.

Cheers

Yes these are my notes in Stagato Style, sorry guys.

For planning the consolidation of multiple server to one server

Plans based on collected resource history data for a certain time interval

Cloud Consolidation Planning Workflow

• Collect data from source servers
• Select resources to be analyzed
• Define constraints
• Specify Target Servers
• Review Consolidation Plan Results

User creates consolidation project and defines:

Type of consolidation P2P P2V

Source servers

After source data collection you can analyze the gathered data and resource usage trends.

Consolidation Analysis

• Consolidation scenario specifies which metrics will be analyzed for the purpose of the consolidation exercise
• Resource requirements fir each source server calculated
• Each resource aggregated to 24-hour patterns based on specified formula
  • Conservative
  • Medium
  • Aggressive

Consolidation constraints

Use constraints to specify which server workloads can be placed together and which workloads must be kept apart for business or technical reasons

Consolidation planner uses SPECint data related to specific processor types

Policies for existing servers – Fewest Servers, Even distribution

Specify Maximum Resource Utilization % on Target Servers

Exadata Target Planning, to use Exadata as a Target platform

Server Mapping (the actual running of the consolidation)

Automatic Mapping of Source Servers onto Target Servers

Manual Mapping can be used on existing servers

Reporting

Consolidation scenario report available after running scenario

KEY BENEFITS

• Identify under-utilized and over-utilized servers
• Help admins determines candidates for consolidation
• Work physical and virtual

METERING AND CHARGEBACK

• Metering and Chargeback enable cloud consumers to take control of their costs
• Cloud empowers end-users to provision resources onto shared infrastructure using self-service
• Without chargeback there can be a perception that cloud resources are ‘ free’
• Without metering charges will be flat regardless of usage

Chargeback – Key Concepts

• Charge Item
  • Targets that are chargeable
  • Charge Plan
    • Defines the charge items and associated rates that will be used for charge calculations
    • Cost Center
      • Organization unit that will be charged for the costs
      • Reporting Cycle

Chargeback Workflow

Select targets for metering

Define charge plans

Define cost center hierarchy

Assign charge items to charge plan

Target metering dedicated and shared mode

Dedicated mode consumers using the target are from the same cost center

Shared mode: consumers using the target are from different cost centers

Setup charge Plan

• Simplest way to leverage chargeback
• Contains 3 universal charge items
  • CPU
  • Memory
  • Storage
  • Can be assigned to any type of supported chargeback target
  • Extended charge plan
    • Target specific charges
      • VM machine size
      • Database Option
      • Host OS
      • WebLogic User Requests
• Supports fixed, configuration and usage based rates
• Can leverage the universal plan with universal rate adjustment
• Extended Plan conditions
  • Under specific conditions

Define Cost Centers

• Used in aggregation in Charge reports
• Import from LDAP option
  • OID
  • AD
  • Open LDAP
  • Novel EDirectory
  • SUN IPlanet
  • Default cost center sued for unassigned targets

Charge Plan and Cost Center Assignment

Chargeback admin uses target and plan assignment

Reports

• Daily job calculates all charges for current reporting cycle
• Ad-hoc reports available from chargeback reports tab
• Chargeback tab in self-service portal provide summary
• Trending shows charge and utilization trend over specific period
• BI Publisher – Generate Reports in variety of formats
• Email reports to recipients

Chargeback – MRB integration

Integrate with oracle billing and revenue management

Again I will do my post in the form of a summary of features. Simply need some more time to revise these posts, so stay tuned. For now this is what I wanted to share with you guys.

Yes these are my notes in Stagato Style, sorry guys.

Patching Challenges

Database patch management process

• Complex
  • Many steps to perform
  • RAC – Grid – ASM
  • Manual
  • Error Prone
  • Time consuming
  • Labor intensive
  • Affects application uptime/business continuity

Current Patching Tools

• Opatch
• Custom scripts
• Enterprise Manager

EM 12c Patching Features

• Patch advise
  • Based on Configuration
  • Community information
  • MOS
    • Complete integration between EM and MOS
    • Support for Off-line Mode if Online connection is unavailable
    • Patch planning
      • Plans & Templates
        • Bundle multiple Patches
• Detects conflicts and fie merge requests
  • Automatic Patch Conflict Resolution
  • Files Patch request incase of conflict
• Pre-flight dependencies and impact analysis
• Patchability Reports
  • Identify what can be patched before starting the process
• Real-time target sanity checks:
  • Is there enough disk space
  • Opatch checks on version
  • Cluster verification
  • Inventory sanity like locks, access…
  • Patch rollout
    • Out of Place patching/upgrade for single instance
    • Rolling patching for RAC
    • One-offs, Patch sets, CPU, PSU and GI bundles
    • Support AC, Clusterware, ASM, Database, Exadata
    • Patch verification & Reporting
      • Patch Compliance Tracking
      • Associate targets to Compliance standards
      • Track compliancy

User profiles tailored for Datacenters

• Site Administrator
• Patch Designer
  • Create patch plan
  • Apply on Test
  • Save as Patch Template
  • Publish Template so that the Patch Operator can use it for Production
  • Patch Operator

Upgrade Planning

• Identify the path to upgrade
• Download required software
• Perform upgrade

Out-of-Place Patching

• Multiple Database running form same home
• Clone Oracle Home
• Patch Cloned Oracle Home
• Switch instances to newly cloned Oracle Home
• Apply SQLs (as needed) to the instances

Rolling Real Application Cluster Patching

Rolling upgrade instance by instance

Patching Database Clusters on Exadata

Also supports out-of-place patching

Automated Upgrade Deployment

For instance 10.2.0.4 à 11.2.0.3

Patching in off-line mode

Also supported

Manually download the patches and upload to Software Library

Customer Story: Enterprise Holdings

World largest Car Rental Company

400+ databases

100+ Oracle Database software

Three datacenters

AIX and Linux

Average 4 databases per Oracle Home

Out of place Patching

• Less down time
• Less risk
• Consistent gold code across enterprise
• Easily Rollback
• No common downtime across all applications with shared environments

Currently takes a lot of time to complete with multiple DBA’s (30 days)

Engineering time spent automating changes and testing

Still manually pre/post step necessary

DBA privileges required to execute commands

OEM 12c Solution

Search patches and check patch conflicts directly with MOS

Predefined procedures with pre-requisite checks

Building a gold code – Clone from an existing install and patch it

Ability to move databases with a shared ORACLE_HOME one at the time

Run post SQL scripts

Access and Manageability

Separation of Roles (Designer and Operator)

Manage as Groups

Create Named credentials for security and store them as Preferred Credentials for reuse

Ability to create Templates with patches, enforcing standards

Restrict Operators to specific Databases and allowed actions

Expected Savings

Reduce effort form 30 days to a few days

Process streamlined by using Designer?operator instead of multiple teams/roles

Significantly reduce documentation overhead

DBA are now able to focus efforts on business related applications

Room fully packed, looks like many people are interested in this new release.

Again I will do my post in the form of a summary of features. Simply need some more time to revise these posts, so stay tuned. For now this is what I wanted to share with you guys.

Yes these are my notes in Stagato Style, sorry guys.

Unique management requirements

• Personalization
• Extensibility
• Performance stability and scalability
• Security
• Manageability
• Fault diagnostics

Personalization

• Tailor EM experience based on job role
  By this not everybody will get the same homepage, but can choose the page layout the like and suit best to their jobs
• Custom Homepages
• Customize Target Homepages
• Favorites
• History
  Very easy for context switching, so being able to get back to where you were 2 clicks ago.

OK, because of technical issues no DEMO was given.

Extensibility

• New architecture for extensibility
  • EM platform – cannot be updated between releases
  • EM plugins – can be updated between releases
  • All out of the box target types modeled as plug-ins
  • Enables target support and other vertical capabilities
  • Target plugins
    • Management for new versions of targets like: databases, fusion middleware, Siebel, Exedata etc
    • Monitoring of 4rd party targets through metadata based plugins
    • Solution plugin
      • Provide enhancements in vertical functionality
      • Chargeback end trending
      • Self service cloud management

Plugin deployment

• Single console to manage lifecycle
• Pre-requisite checks and logging
• Seamless deployment of plugins across middle tier and agent tier

Enhanced custom plug-ins

• Target to target associations
• Automatic discovery
• Custom target credentials
• Configuration Management
• Compliance standards

Self-Update

Automatically update of:

• Agent Core images
• Plug-ins
• Compliance standards and rules
• Diagnostics checks
• VM templates
• Management Connectors
• Administrators notified that update is available
• Update is downloaded from Oracle store to customer site
• Update is applied by administrator

Performance, stability and scalability

• Fault tolerant Agent
• Robust
  • Less port specific issues
  • Suspension of misbehaving taks
  • Self-tuning
    • Memory allocated based on environment
    • Lightweight
      • Scales to thousands of targets per agent
      • Unified
        • Integration of acquired technology
        • New “ Lifecycle Status” target property
          • Being able to set Production, Staging, Test, Development
          • Missions critical and production servers treated with higher priority than data from development and test systems
          • Helps ensure tat adding more targets does not impact performance
          • Improved Loader
            • Faster uploads
              • Synchronous uploads from Agent
              • No filesystem staging area, simply upload directly to the Management Service
• Isolation of Loader problems
  • Resources partitioned by type of data and lifecycle status
• Flow control
  • Agents backed off by Lifecycle status
  • Stops loader becoming saturated

Security

• Integrate with enterprise security
• Improve authentication to EM
  • Integration with (OAM SSO)
  • Direct LDAP authentication support (AD and OID)
  • Strong host and database target authentication
  • Improved credential management
  • Fine grained authorization
  • Out-of-the-box roles

Manageability

• Deployed across thousands of distributed systems
• Agent software download with self-update
• Deploy to multiple servers and platforms in a single step
  • SSH ensures confidentiality and integrity of agent deployment
  • Remote prerequisite checks
  • Automatically registers agent with OMS
  • All control operations from UI and EMCLI
    • Start
    • Restart
    • Shutdown
    • Secure
    • Update Agent Properties
    • Support for batch control operations and property changes
    • Agent monitoring
      • Performance, resource usage
      • Configuration information
      • Deployed metric extension and plug-in summary
      • System/Service modeling of EM Application
        • Database components
        • Weblogic comp
        • Hosts
        • EM services
        • Auto discovery
        • New target types
          • OMS/OMS console/OMS platform
          • Rich relationships
            • Composite application contains
            • Provided by
            • Topology viewer and EM services dashboard
            • Central location to assess EM health
            • Dependency analysis for EM system
            • Shows relationships between system components
            • Customizable views and component grouping

Diagnostics framework

• Reduce time to resolution of EM problems
• Simplifying customer interaction with Oracle Support
• Problem prevention

Incident Manager

• Manage complete lifecycle of all incidents and problems
• Assigns ownership, add comments, prioritize, escalate and track incidents
• Guided resolution
• Integration with Support Workbench

Typical case of “Old wine in new bottles” ?

Madhup Gulati

After a short introduction to the Cloud Concept by Madhup Gulati from Oracle, Kai Yu started his presentation.

When looking at Cloud management and Oracle Enterprise Manager Cloud Control it all comes the integration with OracleVM 3.0

In his presentation Kai showed us the integration of Oracle VM Manager and EM. Instead of the “Half baked” solution we found in EM 11.1, the integration of Oracle VM Manager 3.0 in EM 12c is a “plugin” based solution where you are actually using Oracle VM Manager when in EM 12c.

By means of synchronization configuration changes made while in Oracle VM Manager can be synchronized with EM. This new way of integration allows you to fully configure the Oracle VM environment while connected to the EM console.

One of the Cloud Key features, the Self Service portal relies fully on the definition of Roles. Assigning Quotas, Zones and Network Profiles to the Role allows you to authorize your users to access and work with the Portal.

Both presenters Adeesh Fulay and Matthew McKerley did a very good job explaining things.

Self Service

• Pre-packaged
• One click provisioning
• On demand scaling
• Metering – Chargeback
• Comparable with Amazon Cloud Services

Metering / Chargeback

• Charge reports for Cost Centers
• Rollup based on LDAP hierarchy

Creating a Cloud

• Automated discovery and resource base-lining
• Consolidation Planning
  • Eliminates inefficient use of resources
  • Cloud models on Virtualized and Physical platforms

Something on Hiearchy

• Cloud – Top-level entity
  • Database zones – Defines a logical unit based on configuration, version etc.
    • Database software – Oracle Home
      • RAC Cluster – Collection of Servers with Clusterware installed

Cloud Administrator

• Provision
• Manage Cloud Resources
• Create Users and Roles
• Manage Security and Policies
• Provision Database Software

Self Service Administrator

• Define deployment procedures for database provisioning
• Define services in Service Catalog for deployment by Self Service users
• Assign quotas to Users and Roles
• Define access boundaries (map Roles to Zones)

Database Provisioning Procedures

• Usage of Provisioning Profiles
• Ability to lock down certain Configuration Parameters
• Catalog of Service Templates – saved Deployment Procedures

Creation of database zones

• Policy constraints per Host
  • Max CPU utilization
  • Max MEM
  • Max number of database instances

Does solve several issues I see at various customers, like ability to limit resource usage per server.

A Self Service Administrator is able to create it’s own Service Catalog (Predefined Deployment Procedures).

Metering an Charge Back based on a Charge Plan. Based on this you are able to create Charge Back reports based on for instance a Cost Center.
Charge Back reports can also be created as a drill down based on a LDAP hierarchy.

Also we need to get used to the concept of Database Zones, which are a logically group of Databases based on configuration, version etc.

In the Novellus Theater, Richard Sarwal (Senior Vice President Oracle) gave us a 1 hour presentation of some of the EM 12c highlights.

Some figures he mentioned:

• 200 new features
• 500 enhancement requests included
• 3 years of development
• A complete rebuild

As the ‘c’ in the new release obviously tells us, the new release of Enterprise Manager has got a lot to do with the monitoring and management of the cloud. Including a Self Service feature to allow end users to fully profit from the grid and the desired by many, charge back feature.

Here are some other features that draw my attention:

• Cloud services
• Support physical and virtual clouds
• Console feature will run on iPad and other mobile devices
• ADDM like feature for middleware
• Out of place patching
• Integrated hardware & software for EXADATA
• Increased support MOS integration
• ASR automated creation of SR
• New web 2.0 UI
• Many partner plugins
• Business transaction monitoring related to business services SLA
• Real-time ADDM analysis

During the night I have been downloading the software from OTN and will try to start installation one of these days

Today I will be attending some presentations focusing on this new release, so stay tuned.

Read about it on OEM GC 12c – Total Cloud Control