Scribd Logo
Importer

Bienvenue sur Scribd !

  • 03 B SC Enablement Exadata ASM

    Transféré par

    IMRAN SHABBAR
    16 vues28 pages
    The file creation process provides a fine illustration of the interactions that take place between database instances and ASM. The file creation process occurs as follows: 1. The database requests file creation. 2. An ASM foreground process creates a Continuing Operation Directory (COD) entry and allocates space for the new file across the disk group. 3. The ASMB database process receives an extent map for the new file. 4. The file is now open and the database process initializes the file directly. 5. After initialization, the database process requests that the file creation is committed. This causes the ASM foreground process to clear the COD entry and mark the file as created. 6. Acknowledgement of the file commit implicitly closes the file. The database instance will need to reopen the file for future I/O. This example reinforces two important points about the architecture of ASM: The Database Instance and ASM Instance work together in a coordinated fashion. A Database instance must interact with ASM to map database files to ASM extents. A Database instance also receives a constant stream of messages relating to ASM operations (such as disk group rebalancing) that may lock or move ASM extents. Database I/O is not channeled through the ASM instance. In fact, the database conducts I/O operations directly against ASM files, as illustrated in step 4 in the slide.

    Copyright

    © © All Rights Reserved

    Formats disponibles

    PPT, PDF, TXT ou lisez en ligne sur Scribd

    Avez-vous trouvé ce document utile ?

    Ce contenu est-il inapproprié ?

    Signaler ce document
    The file creation process provides a fine illustration of the interactions that take place between database instances and ASM. The file creation process occurs as follows: 1. The database requests file creation. 2. An ASM foreground process creates a Continuing Operation Directory (COD) entry and allocates space for the new file across the disk group. 3. The ASMB database process receives an extent map for the new file. 4. The file is now open and the database process initializes the file directly. 5. After initialization, the database process requests that the file creation is committed. This causes the ASM foreground process to clear the COD entry and mark the file as created. 6. Acknowledgement of the file commit implicitly closes the file. The database instance will need to reopen the file for future I/O. This example reinforces two important points about the architecture of ASM: The Database Instance and ASM Instance work together in a coordinated fashion. A Database instance must interact with ASM to map database files to ASM extents. A Database instance also receives a constant stream of messages relating to ASM operations (such as disk group rebalancing) that may lock or move ASM extents. Database I/O is not channeled through the ASM instance. In fact, the database conducts I/O operations directly against ASM files, as illustrated in step 4 in the slide.

    Droits d'auteur :

    © All Rights Reserved
    Téléchargez comme PPT, PDF, TXT ou lisez en ligne sur Scribd
    Signaler comme contenu inapproprié
    16 vues28 pages

    03 B SC Enablement Exadata ASM

    Transféré par

    IMRAN SHABBAR
    The file creation process provides a fine illustration of the interactions that take place between database instances and ASM. The file creation process occurs as follows: 1. The database requests file creation. 2. An ASM foreground process creates a Continuing Operation Directory (COD) entry and allocates space for the new file across the disk group. 3. The ASMB database process receives an extent map for the new file. 4. The file is now open and the database process initializes the file directly. 5. After initialization, the database process requests that the file creation is committed. This causes the ASM foreground process to clear the COD entry and mark the file as created. 6. Acknowledgement of the file commit implicitly closes the file. The database instance will need to reopen the file for future I/O. This example reinforces two important points about the architecture of ASM: The Database Instance and ASM Instance work together in a coordinated fashion. A Database instance must interact with ASM to map database files to ASM extents. A Database instance also receives a constant stream of messages relating to ASM operations (such as disk group rebalancing) that may lock or move ASM extents. Database I/O is not channeled through the ASM instance. In fact, the database conducts I/O operations directly against ASM files, as illustrated in step 4 in the slide.

    Droits d'auteur :

    © All Rights Reserved
    Téléchargez comme PPT, PDF, TXT ou lisez en ligne sur Scribd
    Signaler comme contenu inapproprié
    sur 28

    <Insert Picture Here>

    Automatic Storage Management


    Technical Overview

    The DBA Storage Challenges


    Databases are rapidly growing in size

    DBAs have to manage thousands of data files


    Decreasing windows of scheduled downtime
    Storage resources involve many organizations

    Database Admin
    Systems Admin
    Storage Admin
    Network Admin
    Management of database storage is increasing in complexity and
    cost

    Storage Management Gap


    Avg. Managed Capacity per Administrator

    In Database Sites with >100 GB Capacity


    60
    50
    Disk
    Capacity

    40
    30

    Capacity
    /DB Adm

    20
    10

    Mgmt Gap

    19
    97
    19
    98
    19
    99
    20
    00
    20
    01
    20
    02
    20
    03
    20
    04
    20
    05

    Capacity in
    Terabytes

    Strategic Research Corporation

    Automatic Storage Management


    A Database File System which provides cluster file system and
    volume manager capabilities that are integrated into the Oracle
    database 10g kernel at no additional cost

    Reduce Cost and Complexity Without Compromising


    Performance or Availability
    Simplifies and Automates Database storage Management

    Increases Storage Utilization and Agility


    Predictably Delivers on Performance and Availability SLAs

    Database Storage
    Provisioning and Management
    Servers
    Application &DB mgmt

    This is where ASM


    fits into the stack

    File System Mgmt


    Volume Mgmt

    ASM also simplifies


    this process for
    clustered storage

    Storage
    Arrays

    Zoning

    Networked
    Networked
    storage
    Storage

    LUN Masking

    Assign Volume Ports


    Configure LUNs

    The Operational Stack


    ASM

    Before ASM
    Tables

    Tables

    Tablespace
    Files

    Tablespace
    0010 0010 0010 0010 0010
    0010 0010 0010 0010 0010

    File Names

    File System

    File System

    Logical Vol

    Logical Vol

    Disks

    Disk Group

    Networked Storage
    (SAN, NAS, DAS)

    Automatic
    Storage
    Management

    Screen reader hint: This slide


    contains a diagram that is
    explained in the speaker notes.

    Interaction Between Database


    Instances and ASM
    ASM Instance
    System Global Area

    Database Instance
    System Global Area

    1
    Shared
    Pool

    Large
    Pool

    Buffer
    Cache

    Processes

    a
    nt M
    Exte

    5
    CKPT

    DBWR

    LGWR

    Snnn

    ASM
    Cache

    Processes
    RBAL
    MARK

    Clos

    Large
    Pool

    mit
    Com

    SMON

    PMON

    Shared
    Pool

    File
    e
    t
    a
    e
    r

    GMON
    PZ9n
    ARBn
    Onnn

    Other
    Other
    Other

    Other
    Other
    Other

    Allocation

    Initialize

    ASM Storage

    Screen reader hint: This slide


    contains a diagram that is
    explained in the speaker notes.

    Disk Group Overview

    Disk 1

    Disk 2

    Disk 3

    Disk 4

    Disk 5

    Disk 6

    File 3

    File 4

    File 1

    File 2

    ASM Disk Groups


    A pool of disks managed as a
    logical unit

    Disk Group

    ASM Disk Groups


    A pool of disks managed as a
    logical unit
    Divides total disk space into
    uniform sized megabyte units

    Disk Group

    ASM Disk Groups


    A pool of disks managed as a
    logical unit
    Divides total disk space into
    uniform sized megabyte units
    ASM spreads each Oracle file
    evenly across all disks in a disk
    group

    Disk Group

    Traditional vs ASM Add Disk

    1. Add Disk to OS
    2. Create volume(s) with
    Volume Manager
    3. Create File System over
    volume
    4. Figure out data to move to
    new disk
    5. Move data to new files
    6. Rename files in database
    7. Re-tune I/O

    1. Add Disk to OS
    2. Issue the Add Disk
    command

    Adding a Disk with ASM


    DBA issues the request to
    add a disk to the existing
    disk group

    Disk Group

    ASM Dynamic Rebalancing


    Automatic online rebalance
    whenever storage configuration
    changes

    Disk Group

    ASM Dynamic Rebalancing


    Automatic online rebalance
    whenever storage configuration
    changes
    Only move data proportional to
    storage added

    Disk Group

    Traditional vs ASM Remove Disk


    1. List all data that is on disk
    2. Choose existing filesystem
    to hold data from dropped
    disk
    3. Move data to new files
    4. Rename files in database
    5. Remove disk from OS
    6. Re-tune I/O

    1. Issue drop disk command


    2. Remove the disk from OS
    when Oracle says it is done

    Traditional vs ASM Tune I/O


    1. Daily monitor I/O
    performance
    2. Discover hot spots
    3. Figure out how to remove
    hot spots
    4. Move data to new files
    5. Rename files in database
    6. Verify that hot spot is gone

    This space intentionally left


    blank

    Data Distribution

    Unstriped Disks

    Striped Disks

    Automatic Storage Management Extends SAME


    Allows dynamic online Storage reconfiguration
    Efficient relocation of data during rebalance
    Eliminate manual I/O tuning in all storage configurations

    Data Mirroring with ASM


    Choices for disk group
    redundancy
    External: defers to hardware
    mirroring
    Normal: 2-way mirroring
    High: 3-way mirroring

    Integration with database


    removes need for dirty
    region logging

    ASM Mirroring
    Mirror at extent level
    Mix primary & mirror extents on each disk

    ASM Mirroring
    Mirror at extent level
    Mix primary & mirror extents on each disk

    ASM Mirroring
    No hot spare disk required

    Just spare capacity


    Failed disk load spread among survivors
    Maintains balanced I/O load

    ASM Failure Groups


    Disk Groups assigned by DBAs
    A Failure Group is a set of
    disks sharing a common
    resource whose failure needs
    to be tolerated

    Controller 1

    Controller 2

    Redundant copies of an extent


    are stored in separate Failure
    Groups

    Failure Groups assigned by


    DBAs or automatically by ASM

    Failure Group 1 Failure Group 2

    Disk Group

    ASM Architecture
    ASM
    Instance

    NonRAC

    Oracle
    DB Instance

    Database

    Server

    Pool of Storage
    Disk Group

    ASM Enables Consolidated Clustered


    Storage
    ASM
    Instance

    RAC or
    NonRAC
    Databases
    Clustered

    Oracle
    DB Instance

    ASM
    Instance
    Oracle
    DB Instance

    Database

    ASM
    Instance
    Oracle
    DB Instance

    ASM
    Instance
    Oracle
    DB Instance

    Database

    Servers
    Clustered

    Pool of Storage
    Disk Group

    Disk Group

    ASM
    Instance
    Oracle
    DB Instance

    Screen reader hint: This slide


    contains a diagram that is
    explained in the speaker notes.

    ASM Dynamic Performance Views


    Diagram
    V$ASM_FILE

    V$ASM_ALIAS

    V$ASM_ATTRIBUTE

    V$ASM_OPERATION

    V$ASM_DISKGROUP

    V$ASM_DISK

    V$ASM_TEMPLATE

    V$ASM_CLIENT

    V$ASM_DISK
    _IOSTAT

    Lower Cost and Complexity


    Without Compromising
    Performance or Availability
    Simplify and Automate
    Database Storage
    management

    Fraction of the time is needed to


    manage database files

    Increase Storage Utilization


    and Agility

    Eliminate over provisioning and


    maximize storage resource
    utilization with new flexibility

    Predictably Deliver on
    Service Level Agreements

    Never get out of tune delivering


    higher performance than raw and
    file system sustained over time
    Uncompromised availability
    empowering low cost storage
    deployment reliably

    Copyright 2009, Oracle Corporation and/or its affiliates

    28

    Vous aimerez peut-être aussi