Mma 10g r2_936

Download Mma 10g r2_936

Post on 07-Feb-2017




1 download

Embed Size (px)


  • This presentation is for informational purposes only and may not be incorporated into a contract or agreement.

  • This document is for informational purposes. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development,

    release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. This document in any form, software or printed matter, contains proprietary information

    that is the exclusive property of Oracle. This document and information contained herein may not be disclosed, copied,

    reproduced or distributed to anyone outside Oracle without priorwritten consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement

    with Oracle or its subsidiaries or affiliates.

  • Lawrence To & Joe MeeksOracle

    Jeffrey McCormickThe Hartford

  • What They Didn't Print in the Doc

    HA Best Practices by Gurus from Oracles Maximum Availability Architecture Team

  • Agenda

    Maximum Availability Architecture (MAA) The Hartford and MAA HA Best Practices, Tips and Results

    Turbocharged Data Guard Oracle Snapshots and Clones More Uptime for Planned Downtime Transparent Client Failover for Disaster Recovery

  • Maximum Availability Architecture - MAA

    ! Oracle recommended architecture and best practices for High Availability

    ! Database, Application Server, Enterprise Manager, Collaboration Suite and Oracle Applications

    Improved and validated with new Oracle versions, features and product suites

    Focused on reducing unplanned and planned downtime Focused on making customers successful

  • Our Approach

    Develop HA solutions and features Work closely with different development teams

    Provide feedback early in the development cycles Integrate features and test before and after release

    Deploy MAA on internal production systems Design and influence future solutions and features Partner with strategic infrastructure providers Document in best practice books and white papers

    35 Person Years of Effort & Growing

  • Strategic MAA Partners


    Dell, HP


    F5, Qlogic, Foundry Networks, Emulex


    Apple, Engenio, NetApp, HP, EMC

  • Our success measured by the response from customers like you . . .

  • Jeff McCormick Senior Data ArchitectThe Hartford $22.7 billion in revenue Leading provider of investment products, life

    insurance, employee benefits, auto, homeowner & business insurance

    Largest seller of individual annuities in U.S. 11,000 agencies, 100,000 broker/dealers 30,000 employees

  • Architecture Review

    Focus on Business Continuity Assess information technology architectures Minimize/avoid planned & unplanned downtime Rapid recovery/failover to remote location Provide excellent service at lowest cost Retain flexibility to incorporate new technology

  • The Hartford Future State

    Primary Primary

    Primary Site Secondary Site Tertiary Site




    Tape Drive Tape Drive




    Data Guard


    Database REDO

    Database REDO


    Data Guard


    Data Guard


    Data Guard


    Real Application Cluster

  • The Value of MAA to The Hartford

    Simple . . .

    Implement a High Availability solution that offers considerable savings in cost, resources, and time.

  • MAA Best Practices

    Lawrence ToOracle

  • Turbocharged Data GuardDisaster Recovery Solution for

    Oracle Databases

  • Data Guard Best Practices

    Test results show significant out of the box improvements with Data Guard Release 10.2

    Reduction of failover times, potential data loss and primary database impact

    More efficient redo transport Data Guard SYNC implementation is less impact

    than remote mirroring implementation

  • New Data Guard Feature: Fast-Start Failover

    Automatic and fast Logical standby achieved < 20 seconds Physical standby achieved < 20 seconds Old primary is reinstated automatically once

    connectivity is reestablished between observer and primary database

    Attend Session 937, Best Practices for Automatic Failover Using Oracle Data Guard 10g Release 2

  • Data Guard Best Practices:Switchover for Planned Maintenance

    For fastest switchover (< 1 minute) Prior to switchover

    a physical standby transitioning from read only back to Redo Apply should be restarted

    disconnect all sessions and stop job processing shutdown abort for all secondary RAC instances enable real-time apply on the standby database and ensure

    the standby is synchronized or caught up with the primary database

    For manual switchovers open the new primary directly from the mount state

    Or, simulate a Fast-Start Failover - complete transactions and shutdown abort all primary instances

  • Data Guard Best Practices:Faster Redo Transport

    Set SDU=32K Tune network parameters that affect network

    buffer sizes and queue lengths Ensure sufficient network bandwidth for

    maximum database redo rate + other activities

    Note: Please refer to MAA paper, Oracle9i Data Guard: Primary Site and Network Configuration Best Practices

    Oracle 10g Release 2 paper coming soon

  • Data Guard Best Practices:Tune Network Parameters

    Send and receive buffer size = 3 x bandwidth delay product (BDP)

    BDP = 1,000 Mbps * 25ms (.025 secs)= 1,000,000,000 * .025= 25,000,000 Megabits / 8 = 3,125,000 bytes

    Tune network device queues to eliminate packet losses and waits. Set device queues to a minimum of 10,000 (default 100)

    * BDP = the product of the estimated minimum bandwidth and the round trip time between the primary and standby server

  • Impact of Network Tuning

    Impact of Network Tuning



    0 200 400 600 800 1000



    Mbits/secNetwork Throughput

    Oracle MAA Test Result

  • Data Guard Release 10.2 Redo Transport Improvements

    Increased network write sizes to 10 MB to better utilize network capacity for both ARCH and LNS

    Full decoupling of LGWR and LNS processes No more waits during log switches No more waits when LNS buffer is full

    Intra-file parallelism support for ARCH Up to 29 parallel remote archive processes Dedicated local ARCH

  • Faster ASYNC Transport

    52 63 5477 74












    e to





    0ms 10ms 50ms 100ms

    Network latency

    1GB redo transfer



  • ARCH Performance Gains













    e tr







    1 2 3 4 5

    Parallel ARCH Processes

    ARCH Intrafile Parallelism

  • Data Guard Best Practices:Gap Resolution and Data Loss

    For fastest gap resolution Leverage intra-file archive parallelism Follow tips for tuning redo transport to improve network


    To minimize data loss, Use SYNC transport with a low latency and with a high

    bandwidth network For ASYNC transport, follow tips for tuning redo transport

    Example: Less than 7 seconds of data loss exposure for high redo rates of 2-12 MB/sec with

  • Data Guard Best Practices:Reduce Overhead on PrimaryNew Data Guard 10g Release 2 ASYNC Transport Less primary overhead across different latencies and throughput NEW: LNS reads directly from the Online Redo Logs

    Best Practice Allocate additional I/O bandwidth for Online Redo Log Files

    Performance Gains For Redo rates less than 2 MB/sec, there is less than 5% impact on

    the primary database across different latencies For very high redo rates of 20 MB/sec, less than 10% impact on

    primary database even with latencies of 50 and 100 ms Overall, Oracle 10g Release 2 database throughput (redo rate) was

    2-3 times faster than 10gR1 at high redo rates and latencies

  • Data Guard Best Practices:Reduce Overhead on PrimaryOffload Backups to Standby Database Eliminate backup overhead on primary database RMAN enables hot backups of the standby database

    Best Practices Use Redo Apply (Physical Standby) For simplicity, use identical directory structures on the primary and

    standby databases Directory structures can be different see best practice paper for details

    Use RMAN Recovery Catalog so that backups taken on one database server can be restored on another

    Use a catalog server physically separate from primary and standby sites Reference MAA RMAN/Data Guard best practices paper

  • Data Guard Sync Transport Less Overhead than Remote Mirroring

    No DataNo Data

    39% DB Impact39% DB Impact

    26% DB Impact26% DB Impact

    3 % DB Impact3 % DB Impact

    10% DB Impact10% DB Impact20 ms20 ms

    No DataNo Data15 ms15 ms

    4 % DB Impact4 % DB Impact10 ms10 ms

    4 % DB Impact4 % D