oracle cloud file system for sap overview june 2012
TRANSCRIPT
Oracle Cloud File System for SAP Overview
June 2012
Abdel Boukachabine, Principal Sales Consultant
Oracle Database for SAP Technology Center, Walldorf/Germany
What is Automatic Storage Management (ASM)?
• ASM is a volume manager and a file system for Oracle database
files that supports single-instance Oracle Database and Oracle
Real Application Clusters (Oracle RAC) configurations.
• ASM is Oracle's recommended storage management solution
that provides an alternative to conventional volume managers,
file systems, and raw devices.
• Starting with 11gR2 Oracle ASM is the preferred storage
platform for SAP systems running on single-instance Oracle
Database and Oracle Real Application Clusters (Oracle RAC)
• ASM reduces Cost and Complexity Without Compromising
Performance or Availability
Automatic
Storage
Management
The Operational Stack
Disks
Logical Vol
File System
0010 0010 0010 0010 0010
0010 0010 0010 0010 0010
Files
Tablespace
Tables
Disk Group
Logical Vol
File System
File Names
Tablespace
Tables
Before ASM ASM
Networked Storage
(SAN, NAS, DAS)
ASM Disk Groups
Disk Group
• A pool of disks managed as a
logical unit
• Divides total disk space into
uniform sized megabyte units
ASM Disk Groups
Disk Group
• 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
ASM Dynamic Rebalancing
Disk Group
• Automatic online rebalance
whenever storage configuration
changes
ASM Dynamic Rebalancing
• Automatic online rebalance
whenever storage configuration
changes
• Only move data proportional to
storage added
Disk Group
ASM Mirroring
• No hot spare disk required
– Just spare capacity
– Failed disk load spread among survivors
– Maintains balanced I/O load
ASM Redundancy
• EXTERNAL REDUNDANCY indicates that ASM does
not provide any redundancy for the disk group.
• NORMAL REDUNDANCY double mirrors the extents
– tolerates the failure of a single failure group or any
set of disks in a single failure group
• HIGH REDUNDANCY triple mirrors the extents
– tolerates the failure of two failure groups or any set
of disks in two failure groups
• Automatic I/O load balancing
• Stripes and balance loads across
all disks in a Disk Group
• Optimizes I/O throughput and
reduce I/O latency
• Automatic mirroring
• Efficient, online add/remove of
disks
• Consolidate data into a
common shared storage
environment
Automatic Storage Management
DB-A DB-B DB-C
Automatic Storage Management (ASM)
Disk Group
ASM Preferred Mirror Read
Site B Site A
P S Failure
Group A Failure
Group B
Without Preferred
Read
Site B Site A
Failure Group B
Failure Group A
ASM_PREFERRED_READ_FAILURE_GROUPS =
DG_A.FG_A DG_A.FG_B
With Preferred
Read
P S
Without ASM Fast Mirror Resync
ASM redundancy used 1 Disk access failure 2
Disk added back: Extents rebalanced
4 Disk automatically dropped: All dropped extents re-created
3
Oracle Database 10g and 11g
With ASM Fast Mirror Resync
ASM redundancy used 1 Disk access failure 2
Oracle Database 11g
Failure time < DISK_REPAIR_TIME Access other extents
3 Disk again accessible: Auto resync modified extents
4
Allocation Units
• ASM disks are divided into allocation units (AU):
• AU size is configurable at disk group creation
• Default AU size is 1MB:
• Small enough to be cached by database and large enough for
efficient sequential access
• Allowable AU sizes:
• 1, 2, 4, 8, 16, 32, or 64 MB
• Larger AU sizes typically provide performance
advantages for data warehouse applications that use
large sequential reads.
• Oracle recommends that the allocation unit (AU) size for
a disk group be set to 4 megabytes (MB).
ASM Files
• ASM files:
• Are a collection of AUs
• Analogous to extents in a filesystem
• Appear as normal files to the database kernel
• Have file names that start with '+'
• For example, +DATA/P11/datafile/psapsr3.260.738399155
• May be associated with an optional alias file name
• For example, +DATA/P11/datafile/system01.dbf
• Are evenly distributed across disks in a disk group
• Are mirrored according to the policies defined in the disk group
ASM Components
Disk Group
Disk B
2
6
Disk A1
5
Disk C3
7
Disk D4
8File
File
Allocation
Unit
Disk
Group
Disk
Extent size equals AU size for the first 20000 extent sets (0 - 19999).
Extent size equals 4*AU size for the next 20000 extent sets (20000 - 39999).
Extent size equals 16*AU size for the next 20000 and higher extent sets (40000+).
ASM Files
Database File
ASM File automatically spread inside Disk Group +DATA
SQL>create tablespace PSAPCUSTOM datafile '+DATA' size 500M autoextend on;
1
2
3
4
1 2 3 4
Automatic ASM file Creation
RMAN
What is an ASM instance?
• Oracle instance to manage the metadata for disk groups
• All metadata modifications are done by an ASM instance to isolate failures
• Database instances connect to ASM instance to create, delete, resize, open, or close files
• Database instances read/write directly to disk
• one ASM instance per node in a cluster
• ASM instance failure kills attached database instances
Ideal for Data Consolidation
Clustered Pool of Storage
• Shared storage across
several databases
– RAC and Single Instance
• Benefits:
– Simplified and Centralized
management
– Higher storage utilization
– Higher performance
Local Area Network
SAP NW BW Database
SAP ERP Database
SAP CRM Database
11g RAC
ASM 11g
ASM 11g
ASM CRM BW ERP
ASM Management Tools
• SQL
• Native management interface
• Familiar for DBAs
• Enterprise Manager
• Graphical user interface
• Simple to use
• ASM Command Tool (ASMCMD)
• UNIX-like command interface
• Easy for systems administrators to learn
• ASMCA
• Easy to use tool for configuration and deployment
• ACFS is multi-platform, scalable file system, and storage
management technology
• ACFS extends Oracle Automatic Storage Management (Oracle
ASM) functionality to support customer files maintained outside of
Oracle Database
• ACFS supports many database and application files, including
executables, database trace files, database alert logs, application
reports
• Oracle ASM is the preferred storage manager for all database
files. It is optimized for best performance for Database files
• Oracle ACFS is the preferred file manager for non-database files.
It is optimized for general purpose files.
What is ASM Cluster File System (ACFS)
3rd Party FS Application
Automatic Storage Management (ASM)
ASM Cluster & Single Node File System
(ACFS)
Database
ACFS Snapshot
ASM Disk
Group
DB Datafiles, OCR and Voting Files ACFS FSs 3rd Party File Systems
Dynamic Volume Manager
• ASM supports ALL data - database files, file systems, Clusterware files (OCR, Voting Disk)
• Built-in mirroring protects from disk failures
• Enables auto-repair from corrupt blocks using a valid mirror copy
Automatic Storage Management (ASM) Stores & Manages All Data
ASM Instance Managing Oracle DB
Files
ASM Cluster File System
Oracle Management of File System Data
• Manage both database homes and file system data
• Clustered or local file system • Data stored in ASM
• Inherits all ASM manageability benefits
• Online disk add/drop/rebalance
• Integrated mirroring
• Cross-platform
• Read-Only Snapshots • up to 63 point-in-time space efficient
copies of file system
• Available on all platforms except HP-UX
Shared File System
How to get to ASM?
• http://www.oracle.com/pls/db112/portal.all_books
– Grid Infrastructure Installation Guide for all certified OS
• Software Requirements List for your platform
• Creating Groups, Users and Paths for Oracle Grid
Infrastructure
• Checking Server Hardware and Memory Configuration
• Checking the Network Requirements
• Automatic SSH Configuration During Installation (RAC)
• Identifying Storage Requirements for Oracle Automatic
Storage Management
• Creating DAS or SAN Disk Partitions for Oracle Automatic
Storage Management
How to get to ASM?
• Oracle Grid Infrastructure (<OHGRID>)
– Download ORACLE 11.2 (e.g 64-BIT)
• service.sap/com/swdc Search for Installations and
Upgrades type „ORACLE 11.2 64-BIT“
• Unpack the grid dvd to a local directory and start as user
“oracle” /oracle/stage/grid/runInstaller
for single
instance
for Real
Application
Clusters
• Please check Installation and Configuration Requirements for ASM with SAP (scn) for the complete documentation
How to get to ASM? „Cont“
• Create ASM Disk Group
• Disk Group Name: OCR
• select the five (high)/three (normal) disks you prepared
Install the Oracle RDBMS software
• Logon as user “oracle”
• Switch to /oracle/<SID>/112/SAP
• $ ./RUNINSTALLER
• Apply the latest SAP Bundle Patch
Migrate ONLINE the Database to ASM
homogeneous
• Both platforms must use the same endian format. See
view 'V$TRANSPORTABLE_PLATFORM'.
• Only the following platform combinations are
supported
• Solaris-x64 <-> Linux-x64
• HP-PA <-> HP-IA
• Linux <-> Windows (requires minimum 11.1 compatible
setting)
• Solaris SPARC (64-bit) <-> AIX (64-bit) (source database
must be non-RAC and non-TDE)
• Instantiating an Entire Database on the Same
Platform Using: "RMAN duplicate from active
database"
Migrate the Database to ASM
heterogeneous
• Online using Triple-O based on GoldenGate
• Offline:
• Export/import
• Oracle Transportable Tablespaces (TTS)
• Easier and faster than export/import
• For information about the migration process:
– Installation and Configuration Requirements for ASM with
SAP
– Best Practices for Migration of an SAP Database to ASM
– SAP with Oracle Real Application Clusters 11g Release 2 and
Oracle ASM (streteched cluster)
http://scn.sap.com/docs/DOC-7971
Changes came with ASM
• Oracle version 11.2.0.2 or higher
• BR*Tools version 7.20 patch level 18 or higher
includes full support for Oracle ASM
• Oracle software installation under OS user ‘oracle’
• ‘oracle’ OS user replaces ‘ora<sid>’ user
• ‘ora<sid>’ OS user is not used anymore
• One OS user for multiple databases
• Valid only for Oracle 11g ASM and RAC – not for the
standard installations
BR*Tools Configuration with ASM (I)
• Note 1598594 - BR*Tools configuration for Oracle inst.
under "oracle" user
– brarchive, brbackup brtools etc. are owned by “oracle:oinstall”
– /oracle/<SID>/saparch,sapbackup, …,sapprof owned by oracle
– sapprof includes init<SID>.sap, init<SID>.ora
– /$OH/dbs/
• init<SID>.ora: spfile='+DATA/<DBNAME>/spfile<SID>.ora‘
• remove init<SID>.sap to sapprof
– Create ops$oracle, grant sapdba role and drop ops$ora<SID>
BR*Tools Configuration with ASM (II)
• New parameters within init<SID>.sap
– asm_ora_sid = +ASM (default)
– asm_ora_home = /oracle/GRID/11202 (no default)
– asm_root_dir = ASM (default)
• For example a 4 RAC nodes config: asm_ora_sid = (RAC001:+ASM1, RAC002:+ASM2, RAC003:+ASM3,
RAC004:+ASM4)
asm_ora_home =
(RAC001:/oracle/GRID/11203,RAC002:/oracle/GRID/11203,
RAC003:/oracle/GRID/11203, RAC004:/oracle/GRID/11203)
White papers on oracle.com
http://www.oracle.com/us/solutions/sap/wp-o11g-rac-config-unx-303802.pdf
http://www.oracle.com/us/solutions/sap/asm-configguidelines-304656.pdf
http://www.oracle.com/us/solutions/sap/asm-bestpractices-304655.pdf
http://www.oracle.com/us/products/database/sap-exadata-wp-409603.pdf
http://www.oracle.com/us/solutions/sap/sapctl-303790.pdf
For more information:
• http://www.oracle.com/sap
• http://scn.sap.com/community/oracle