Larry Ellison announcing the Oracle Public Cloud

Applications and Platform: Based on Industry Standards.

Run any Oracle Database in the cloud. You can take back whenever you want, move it to Amazon, whatever you want. Everything is portable.

Java Service: Standards-based. Run any Java Application in the Cloud.

“Beware of False Clouds”
Standards-based Cloud vs. Vendor Proprietary Cloud

Data Service: Standards-based

Service Oriented Architecture: Easy Integration

Instantly Productlibity

  • Monthly subscription
  • Self-service sign-up
  • Instance provisioning
  • Elastic: Capacity-on-Demand
  • Develop/extend applications using Java

Fusion Suite: Runs in the Cloud and On-Premise

Secutiry Built into Middleware, DB, OS – Not Applications


Enterprise Manager Consolidation Planner

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.

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


Consolidation scenario report available after running scenario


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


  • 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


  • 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

Next Generation Database Patching – Maximum Ease – Minimum Downtime

Hari Srinivasan
John Young
Tim Misner

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 à

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