lesson 01 5day

8/4/2019 Lesson 01 5day

http://slidepdf.com/reader/full/lesson-01-5day 1/59

Copyright © 2010, Oracle and/or its affiliates. All rights reserved.

Oracle Grid Infrastructure Architecture

8/4/2019 Lesson 01 5day


Copyright © 2010, Oracle and/or its affiliates. All rights reserved.1 - 2

Objectives

After completing this lesson, you should be able to:• Explain the principles and purposes of clusters

• Describe Cluster hardware best practices

• Describe the Oracle Clusterware architecture

• Describe how Grid Plug and Play affects Clusterware• Describe the Automatic Storage Management (ASM)

architecture

• Describe the components of ASM

8/4/2019 Lesson 01 5day



Oracle Grid Infrastructure• ASM and Oracle Clusterware are installed into a single

home directory called Oracle Grid Infrastructure 11g

Release 2.• This directory is referred to as the Grid Infrastructure

home.

8/4/2019 Lesson 01 5day



Module 1: Oracle Clusterware Concepts

8/4/2019 Lesson 01 5day



What Is a Cluster?

• A group of independent, but interconnected, computersthat act as a single system

• Usually deployed toincrease availability andperformance orto balance a dynamicallychanging workload

Storage Network

Interconnect

Users

Network

8/4/2019 Lesson 01 5day



What Is Clusterware?

Software that provides various interfaces and services for acluster. Typically, this includes capabilities that:

• Allow the cluster to be managed as a whole

• Protect the integrity of the cluster

• Maintain a registry of resources across the cluster• Deal with changes to the cluster

• Provide a common view of resources

8/4/2019 Lesson 01 5day

http://slidepdf.com/reader/full/lesson-01-5day 7/59Copyright © 2010, Oracle and/or its affiliates. All rights reserved.1 - 7

Oracle Clusterware

Oracle Clusterware is:• A key part of Oracle Grid Infrastructure

• Integrated with OracleAutomatic Storage

Management (ASM)• The basis for ASM Cluster

File System (ACFS)

• A foundation for OracleReal Application Clusters

(RAC)

• A generalized clusterinfrastructure for all kindsof applications

8/4/2019 Lesson 01 5day


Oracle Clusterware Architecture and Services

• Shared disk cluster architecture supporting applicationload balancing and failover

• Services include:

– Cluster management

– Node monitoring – Event services

– Time synchronization

– Network management

– High availability

8/4/2019 Lesson 01 5day


Goals for Oracle Clusterware

• Easier installation• Easier management

• Continuing tight integration with Oracle RAC

• ASM enhancements with

benefits for all applications• No additional clusterware

required

8/4/2019 Lesson 01 5day


Oracle Clusterware Networking

• Each node must have at least two network adapters.

• Each public network adapter must support TCP/IP.• The interconnect adapter must support:

– User Datagram Protocol (UDP) or Reliable Data Socket (RDS)for UNIX and Linux for database communication

– TCP for Windows platforms for database communication• All platforms use Grid Interprocess Communication (GIPc)

Interconnect: Private network

Public network

8/4/2019 Lesson 01 5day


Interconnect Link Aggregation: Single Switch

• Link aggregation can be used to increase redundancy forhigher availability with an Active/Standby configuration.

• Link aggregation can be used to increase bandwidth forperformance with an Active/Active configuration.

bond0

Active Standby Active Active

Interconnect Interconnect

Each

node

Each

node

eth2

bond0

eth2

8/4/2019 Lesson 01 5day


Interconnect Link Aggregation: Multiswitch

• Redundant switches connected with an Inter-Switch Trunkmay be used for an enhanced highly available design.

• This is the best practice configuration for the interconnect.

Active Standby

Eachnode

Inter Switch Trunk

Interconnect

eth1

eth2

bond0 eth1

eth2

bond0

8/4/2019 Lesson 01 5day


Interconnect NIC Guidelines

Optimal interconnect NIC settings can vary depending on thedriver used. Consider the following guidelines:

• Configure the interconnect NIC on the fastest PCI bus.

• Ensure that NIC names and slots are identical on allnodes.

• Define flow control: receive=on, transmit=off.

• Define full bit rate supported by NIC.

• Define full duplex autonegotiate.

• Ensure compatible switch settings:

– If 802.3ad is used on NIC, it must be used and supported onthe switch.

– The Maximum Transmission Unit (MTU) should be the samebetween NIC and the switch.

• Driver settings can change between software releases.

8/4/2019 Lesson 01 5day


Additional Interconnect Guidelines

UDP socket buffer (rx)

• Default settings are adequate for the majority ofcustomers.

• It may be necessary to increase the allocated buffer sizewhen the:

– MTU size has been increased

– netstat command reports errors

– ifconfig command reports dropped packets or overflow

Jumbo frames:

• Are not an Institute of Electrical and Electronics Engineers

(IEEE) standard• Are useful for Network-Attached Storage (NAS)/iSCSI

storage

• Have network device interoperability concerns

• Need to be configured with care and tested rigorously

8/4/2019 Lesson 01 5day


8/4/2019 Lesson 01 5day


• Oracle Clusterware is started by the OS init daemon.

• Oracle Clusterware installation modifies the

/etc/inittab file to restart ohasd in the event of acrash.

Oracle Clusterware Startup

/etc/init.d/init.ohasd

ohasd.bin oclskd.bin

octssd.bin crsd.bin

oraagent.bin gipcd.bin

diskmon.bin mdnsd.bin

ocssd.bin gpnpd.bin

evmd.bin scriptagent.bin

cssdagent oraagent.bin

orarootagent.bin

init

Clusterwarestartup script

Oracle Clusterware processesOperating systeminit daemon

# cat /etc/inittab..h1:35:respawn:/etc/init.d/init.ohasd run >/dev/null 2>&1 </dev/null

8/4/2019 Lesson 01 5day


Oracle Clusterware Process Architecture

Clusterware processes are organized into several component groups.

They include:Component Processes Owner

Cluster Ready Service (CRS) crsd root

Cluster Synchronization Service (CSS) ocssd ,cssdmonitor, grid owner,cssdagent root, root

Event Manager (EVM) evmd , evmlogger grid owner

Cluster Time Synchronization Service(CTSS)

octssd root

Oracle Notification Service (ONS) ons, eons grid owner

Oracle Agent oraagent grid ownerOracle Root Agent orarootagent root

Grid Naming Service (GNS) gnsd root

Grid Plug and Play (GPnP) gpnpd grid owner

Multicast domain name service (mDNS) mdnsd grid owner

8/4/2019 Lesson 01 5day


Grid Plug and Play

• In previous releases, adding or removing servers in a

cluster required extensive manual preparation.• In Oracle Database 11g Release 2, GPnP allows each

node to perform the following tasks dynamically:

– Negotiating appropriate network identities for itself

– Acquiring additional information from a configuration profile

– Configuring or reconfiguring itself using profile data, makinghost names and addresses resolvable on the network

• To add a node, simply connect the server to the clusterand allow the cluster to configure the node.

8/4/2019 Lesson 01 5day


GPnP Domain

• The GPnP domain is a collection of nodes belonging to asingle cluster served by the GPnP service:

– Cluster name: cluster01

– Network domain: example.com

– GPnP domain: cluster01.example.com

• Each node participating in a GPnP domain has thefollowing characteristics:

– Must have at least one routable interface with connectivityoutside of the GPnP domain for the public interface

– A unique identifier that is unique within the GPnP domain – A personality affected by the GPnP profile, physical

characteristics, and software image of the node

8/4/2019 Lesson 01 5day


GPnP Components

Software image• A software image is a read-only collection of software to be

run on nodes of the same type.

• At a minimum, the image must contain:

– An operating system – The GPnP software

– A security certificate from the provisioning authority

– Other software required to configure the node when it startsup

8/4/2019 Lesson 01 5day


GPnP Profile

The profile.xml file:

$ cat GRID_HOME /gpnp/profiles/peer/profile.xml

<?xml version="1.0" encoding="UTF-8"?><gpnp:GPnP-Profile Version="1.0"xmlns="http://www.grid-pnp.org/2005/11/gpnp-profile" ...xsi:schemaLocation="http://www.grid-pnp.org/2005/11/gpnp-profile gpnp-profile.xsd"ProfileSequence="4" ClusterUId="2deb88730e0b5f1bffc9682556bd548e" ClusterName="cluster01"PALocation=""><gpnp:Network-Profile><gpnp:HostNetwork id="gen" HostName="*"><gpnp:Networkid="net1" IP="192.0.2.0" Adapter="eth0" Use="public"/><gpnp:Network id="net2"IP="192.168.1.0" Adapter="eth1"

Use="cluster_interconnect"/></gpnp:HostNetwork></gpnp:Network-Profile><orcl:CSS-Profileid="css" DiscoveryString="+asm" LeaseDuration="400"/><orcl:ASM-Profile id="asm"DiscoveryString="/dev/sd*" SPFile="+data/spfile.ora"/><ds:Signature <ds:SignedInfo>

<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/> <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> <ds:Reference URI="">

<ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/>

<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"> <InclusiveNamespaces xmlns="http://www.w3.org/2001/10/xml-exc-c14n#"

PrefixList="gpnp orcl xsi"/> ...

<ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/> <ds:DigestValue>gIBakmtUNi9EVW/XQoE1mym3Bnw=</ds:DigestValue>

... <ds:SignatureValue>cgw3yhP/2oEm5DJzdachtfDMbEr2RSfFFUlZujLemnOgsM...=</ds:SignatureValue>

8/4/2019 Lesson 01 5day


Grid Naming Service

• GNS is an integral component of Grid Plug and Play.

• The only static IP address required for the cluster is the GNSvirtual IP address.

• The cluster subdomain is defined as a delegated domain.

• A request to resolve cluster01-scan.cluster01.example.comwould be forwarded to the GNS on 192.0.2.155.

• Each node in the cluster runs a multicast DNS (mDNS)process.

[root@my-dns-server ~]# cat /etc/named.conf

// Default initial "Caching Only" name server configuration...# Delegate to gns on cluster01

cluster01.example.com # cluster sub-domain # NS cluster01-gns.example.com # Let the world know to go to the GNS vip

cluster01-gns.example.com 192.0.2.155 # cluster GNS Address

8/4/2019 Lesson 01 5day


Single Client Access Name

• The single client access name (SCAN) is the address used

by clients connecting to the cluster.• The SCAN is a fully qualified host name located in the GNS

subdomain registered to three IP addresses.

• The SCAN provides a stable, highly available name forclients to use, independent of the nodes that make up thecluster.

# dig @192.0.2.155 cluster01-scan.cluster01.example.com ...

;; QUESTION SECTION:;cluster01-scan.cluster01.example.com. IN A ;; ANSWER SECTION:cluster01-scan.cluster01.example.com. 120 IN A 192.0.2.244cluster01-scan.cluster01.example.com. 120 IN A 192.0.2.246cluster01-scan.cluster01.example.com. 120 IN A 192.0.2.245;; AUTHORITY SECTION:

cluster01.example.com. 10800 IN A 192.0.2.155;; SERVER: 192.0.2.155#53(192.0.2.155)

8/4/2019 Lesson 01 5day



GPnP Architecture Overview

LL LL LL LL LL

SL SL SL

mDNS mDNS mDNS mDNS mDNS

remote_listener

local_listenerClient

DNS GNS

DHCP

Scan+port+service Node1

L o a d b a l a c i n g

Register node VIP & SCAN VIP

One name thatresolves to three VIPs

G e t s t h e t h r e e S C A N V I P S

D y n a m i c V I P a d

d r e s s e s

o b t a i n e d b y o r a r

o o t a g e n t Least

loadednodefor

service p r o

f i l e . x m

l

U s e 1 S C A N V I P

GNS Static VIP

GPnP GPnP GPnP GPnP GPnP Profilereplication

Host name to address resolution

Get Node VIP& SCAN VIP

orarootagent

Node &SCAN VIPagents

GPnPd discovery

VIP name and hostname resolution

VIP resolution

Node2 Node3 Node4 Noden

…

8/4/2019 Lesson 01 5day


8/4/2019 Lesson 01 5day



How GPnP Works: Client Database Connections

Database

client

DNS

SCAN

listener

Listener1

Listener2

Listener3 SCAN

listener

SCAN

listener

GNS

8/4/2019 Lesson 01 5day


8/4/2019 Lesson 01 5day



Quiz

Which of the following statements regarding Grid NamingService is not true?

1. GNS is an integral component of Grid Plug and Play.

2. Each node in the cluster runs a multicast DNS (mDNS)

process.3. The GNS virtual IP address must be assigned by DHCP.

4. The cluster subdomain is defined as a delegated domain.

8/4/2019 Lesson 01 5day



Module 3: ASM Architecture

8/4/2019 Lesson 01 5day


8/4/2019 Lesson 01 5day



ASM and ASM Cluster File System

• ASM manages Oracledatabase files.

• ACFS manages otherfiles.

• Spreads data acrossdisks to balance load

• Provides integratedmirroring across disks

• Solves many storage

managementchallenges

ASM/ADVM

3rd

PartyFS

Operating System

ACFSDatabase

Application

8/4/2019 Lesson 01 5day



ASM Key Features and Benefits

• Stripes files rather than logical volumes• Provides redundancy on a file basis

• Enables online disk reconfiguration and dynamicrebalancing

• Reduces the time significantly to resynchronize a transientfailure by tracking changes while disk is offline

• Provides adjustable rebalancing speed

• Is cluster-aware

• Supports reading from mirrored copy instead of primarycopy for extended clusters

• Is automatically installed as part of the Grid Infrastructure

8/4/2019 Lesson 01 5day



ASM Instance Designs:Nonclustered ASM and Oracle Databases

ASM disk group A ASM disk group B

Single-instance

database server

ASM instance

Oracle DB Ainstance

Oracle DB Binstance

Oracle DB Cinstance

8/4/2019 Lesson 01 5day



ASM Instance Designs:Clustered ASM for Clustered Databases

ASM disk group A ASM disk group B

Oracle RAC

servers

ASM instance 3

Oracle DB Ainstance 1

Oracle DB Ainstance 2

Oracle DB Binstance 1

ASM instance 2ASM instance 1 ASM instance 4

Oracle DB Binstance 2

8/4/2019 Lesson 01 5day


8/4/2019 Lesson 01 5day



ASM System Privileges

• An ASM instance does not have a data dictionary, so theonly way to connect to ASM is by using these systemprivileges:

• The SYS user on ASM is automatically created with theSYSASM privilege.

ASM Privilege Privilege Group Privilege

SYSASM OSASM Full administrative privilege

SYSDBA OSDBA for ASM Access to data stored on ASM

Create and delete files

Grant and revoke file access

SYSOPER OSOPER for ASM Limited privileges to start and stop the ASMinstance along with a set of nondestructiveALTER DISKGROUP commands

8/4/2019 Lesson 01 5day



ASM OS Groups with Role Separation

To separate the duties of ASM administrators and DBAs, there aresix OS groups:

Group For Example OS Group Privilege

OSASM ASM asmadmin SYSASM

OSDBA ASM asmdba SYSDBA

OSOPER ASM asmoper SYSOPER

oraInventorygroup

Both oinstall

OSDBA DB dba SYSDBA

OSOPER DB oper SYSOPER

8/4/2019 Lesson 01 5day



Authentication for Accessing ASM Instances

There are three modes of connecting to ASM instances:• Local connection using operating system authentication

• Local connection using password file authentication

• Remote connection using Oracle Net Services andpassword authentication

$ sqlplus / AS SYSASM

SQL> CONNECT / AS SYSOPER

$ sqlplus fred/xyzabc AS SYSASM

SQL> CONNECT bill/abc123 AS SYSASM

$ sqlplus bill/abc123@asm1 AS SYSASM

SQL> CONNECT fred/xyzabc@asm2 AS SYSDBA

8/4/2019 Lesson 01 5day



Password-Based Authentication for ASM

• Password-based authentication: – Uses a password file

– Can work both locally and remotely

— REMOTE_LOGIN_PASSWORDFILE must be set to a value otherthan NONE to enable remote password-based authentication.

• A password file is created initially: – By Oracle Universal Installer when installing ASM

– Manually with the orapwd utility

– Containing only the SYS and ASMSNMP users

• Users can be added to the password file using:

– SQL*Plus GRANT command

– ASMCMD orapwuser command

8/4/2019 Lesson 01 5day



Managing the ASM Password File

For the ASM instance, the password file:• Can be created by a user that owns the ASM software

• Holds roles assigned to users

• Is required for Oracle Enterprise Manager to connect to

ASM remotely• Can be viewed from

– SQL*Plus SELECT * FROM V$PWFILE_USERS

– ASMCMD lspwusr

8/4/2019 Lesson 01 5day



Using a Single OS Group

Role/Software SoftwareOwner

Groups/Privileges

Oracle ASM administrator/OracleGrid Infrastructure home

oracle dba/SYSASM, SYSDBA,SYSOPER

Database administrator 1/Database

home 1

oracle dba/SYSASM, SYSDBA,

SYSOPERDatabase administrator 2/Databasehome 2

oracle dba/SYSASM, SYSDBA,SYSOPER

Operating system disk deviceowner

oracle dba

8/4/2019 Lesson 01 5day



Using Separate OS Groups

Role/Software Software

Owner

Groups/Privileges/OS Group

Oracle ASM administrator

Oracle Grid Infrastructurehome

grid asmadmin/SYSASM/OSASM

asmdba/SYSDBA/OSDBA for ASM

asmoper/SYSOPER /OSOPER for ASM

Database administrator 1Database home 1

oracle1 asmdba/SYSDBAdba1/SYSDBA for db1

oper1/SYSOPER for db1

Database administrator 2

Database home 2

oracle2 asmdba/SYSDBA

dba2/SYSDBA

oper2/SYSOPER

Operating system diskdevice owner

grid asmadmin

8/4/2019 Lesson 01 5day



ASM Components:Software

For ASM installation of software:• The directories are located by the operating system

environment variables.

– ORACLE_BASE is the top-level directory for a particular

software owner.

– ORACLE_HOME is used to identify the top-level directory ofthe Grid Infrastructure software.

• Use a common ORACLE_BASE for all Oracle products

owned by the same user.

• Use an isolatedORACLE_HOME

location from other Oracle

products even if they are the same version.

• Do not place Grid ORACLE_HOME below ORACLE_BASE.

• ORACLE_HOME requires 3 GB to 5 GB of disk space.

8/4/2019 Lesson 01 5day



ASM Components:ASM Instance

The ASM instance comprises the process and memorycomponents for ASM.

Other misc. processes

System Global Area (SGA) – memory

Sharedpool

Largepool

ASMcache

Freememory

Processes – CPU components

ASM instance

RBAL ARBn GMON Onnn PZ9n

MARK

8/4/2019 Lesson 01 5day



ASM Components:ASM Instance Primary Processes

Process Description

RBAL Opens all device files as part of discovery and coordinates therebalance activity

ARBn One or more slave processes that do the rebalance activity

GMON Responsible for managing the disk-level activities such as drop oroffline and advancing the ASM disk group compatibility

MARK Marks ASM allocation units as stale when needed

Onnn One or more ASM slave processes forming a pool of connections to theASM instance for exchanging messages

PZ9n One or more parallel slave processes used in fetching data onclustered ASM installation from GV$ views

The ASM instance primary processes are responsible for ASM-related activities.

8/4/2019 Lesson 01 5day



ASM Components:Node Listener

The node listener is a process that helps establish networkconnections from ASM clients to the ASM instance.

• Runs by default from the Grid $ORACLE_HOME/bin

directory

• Listens on port 1521 by default

• Is the same as a database instance listener

• Is capable of listening for all database instances on thesame machine in addition to the ASM instance

• Can run concurrently with separate database listeners or

be replaced by a separate database listener

• Is named tnslsnr on the Linux platform

8/4/2019 Lesson 01 5day



ASM Components:Configuration Files

The ASM installation of software uses several configurationfiles to define the environment.

• ASM instance configuration files include:

– The server parameter file (SPFILE), which initializes theASM instance and defines startup parameters

– orapw+ASM which is the binary password file used forremote authentication to the ASM instance

• Node listener configuration files include:

– listener.ora, a text file that defines the node listener

– sqlnet.ora, an optional text file that provides additional

listener options

• Other miscellaneous text configuration files include: – /etc/oratab, which lists all the instances on the host machine

– /etc/oraInst.loc, which defines the Oracle inventory directory

8/4/2019 Lesson 01 5day



ASM Components:Group Services

Group services provided by Oracle Clusterware allow forcooperating applications to communicate in a peerenvironment.

• Group services for the Oracle environment:

– Provide information necessary to establish connections

– Provide assistance in doing lock recovery

– Guarantee ASM disk group number uniqueness

– Monitor node membership, evictions, and cluster locks

• Oracle Clusterware is responsible for:

– Starting and stopping ASM instances

– Starting and stopping dependent database instances

– Mounting and dismounting disk groups

– Mounting and dismounting ACFS volumes

8/4/2019 Lesson 01 5day



ASM Components:ASM Disk Group

The ASM disk group is the fundamental object that ASMmanages; it:

• Consists of one or more ASM disks that provide space

• Includes self-contained metadata and logging informationfor management of space within each disk group

• Is the basis for storage of ASM files

• Supports three disk group redundancy levels:

– Normal defaults to internal two-way mirroring of ASM files.

– High defaults to internal three-way mirroring of ASM files.

– External uses no ASM mirroring and relies on externaldisk hardware or redundant array of inexpensive disks(RAID) to provide redundancy.

• Supports ASM files from multiple databases

8/4/2019 Lesson 01 5day



ASM Disk Group: Failure Groups

A failure group is a subset of the disks in a disk group, whichcould fail at the same time because of shared hardware.

• Failure groups enable the mirroring of metadata and userdata.

• The default failure group creation puts every disk in its own

failure group.• Multiple disks can be placed in a singe failure group at disk

group creation.

• Failure groups apply only to normal and high redundancydisk groups.

– A normal redundancy disk group requires at least two failuregroups to implement two-way mirroring of files.

– A high redundancy disk group requires at least three failuregroups to implement three-way mirroring of files.

8/4/2019 Lesson 01 5day



ASM Components: ASM Disks

ASM disks are the storage devices provisioned to ASM disk

groups.

• Are formed from five sources as follows:

– A disk or partition from a storage array

– An entire physical disk or partitions of a physical disk

– Logical volumes (LV) or logical units (LUN) – Network-Attached Files (NFS)

– Exadata grid disk

• Are named when added to a disk group using a differentname than the operating system device name

• May use different operating system device names ondifferent nodes in a cluster for the same ASM disk

• Are divided into allocation units (AU) with sizes 1, 2, 4, 8,16, 32, or 64 MB allowed

8/4/2019 Lesson 01 5day



ASM Components:ASM Files

ASM files are a limited set of file types stored in an ASM diskgroup.

• Some supported file types:

• Are stored as a set or collection of data extents

• Are striped across all disks in a disk group

• Use names that begin with a plus sign (+), which areautomatically generated or from user-defined aliases

Control files Flashback logs Data Pump dump sets

Data files DB SPFILE Data Guard configuration

Temporary data files RMAN backup sets Change tracking bitmaps

Online redo logs RMAN data file copies OCR files

Archive logs Transport data files ASM SPFILE

8/4/2019 Lesson 01 5day


8/4/2019 Lesson 01 5day



ASM mirroring is specified at the file level.• Two files can share the same disk group with one file being

mirrored while the other is not.

• ASM will allocate the extents for a file with the primary andmirrored copies in different failure groups.

• The mirroring options for ASM disk group types are:

ASM Files: Mirroring

Disk Group Type Supported MirroringLevels

Default MirroringLevel

External redundancy Unprotected (None) Unprotected (None)

Normal redundancy Two-way

Three-way

Unprotected (None)

Two-way

High redundancy Three-way Three-way

8/4/2019 Lesson 01 5day



ASM Components:ASM Clients

Any active database instance that is using ASM storage andcurrently connected to the ASM instance is an ASM client.

• ASM clients are tracked in the v$asm_client dynamic

performance view.

• Each file in ASM is associated with a single database.

Oracle DB Ainstance

Oracle DB Binstance

Oracle DB Cinstance

ASM instance

ADVM MountedACFS

OCR

8/4/2019 Lesson 01 5day



ASM Components:ASM Utilities

Many utilities can be used for ASM administration. Theseutilities may include:

• Oracle Universal Installer (OUI)

• ASM Configuration Assistant (ASMCA)

• Oracle Enterprise Manager (EM)• SQL*Plus

• ASM Command-Line utility (ASMCMD)

• Listener controller utility (lsnrctl)

• Server controller utility (srvctl)• XML DB (FTP and HTTP)

8/4/2019 Lesson 01 5day



ASM Scalability

ASM imposes the following limits:• 63 disk groups in a storage system

• 10,000 ASM disks in a storage system

• Two-terabyte maximum storage for each ASM disk (non-

Exadata)• Four-petabyte maximum storage for each ASM disk

(Exadata)

• 40-exabyte maximum storage for each storage system

• 1 million files for each disk group

• ASM file size limits (database limit is 128 TB):

– External redundancy maximum file size is 140 PB.

– Normal redundancy maximum file size is 42 PB.

– High redundancy maximum file size is 15 PB.

8/4/2019 Lesson 01 5day


Summary

In this lesson, you should have learned how to:• Explain the principles and purposes of clusters

• Describe Cluster hardware best practices

• Describe the Oracle Clusterware architecture

• Describe how Grid Plug and Play affects Clusterware• Describe the ASM architecture

• Describe the components of ASM

lesson 01 5day

Documents