1.What is a diskgroup in ASM?
- A disk group consists of multiple disks and is the fundamental object that ASM manages.
- Each disk group contains the metadata that is required for the management of space in the disk group.
- The ASM instance manages the metadata about the files in a Disk Group in the same way that a file system manages metadata about its files.
- However, the vast majority of I/O operations do not pass through the ASM instance.
2.Can my disks in a diskgroup can be varied size? For example one disk is of 100GB and another disk is of 50GB. If so how does ASM manage the extents?
Yes, disk sizes can be varied, Oracle ASM will manage data efficiently and intelligent by placing the extents proportional to the size of the disk in the disk group, bigger diskgroups have more extents than lesser ones.
3.What is the major difference between 10g and 11g RAC?
Well, there is not much difference between 10g and 11g (Release-1) RAC.
But there is a significant difference in 11gR2.
Prior to 11gR1(10g) RAC, the following were managed by Oracle CRS
- Databases
- Instances
- Applications
- Node Monitoring
- Event Services
- High Availability
From 11gR2 its completed HA stack managing and providing the following resources as like the other cluster software like VCS etc.
- Databases
- Instances
- Applications
- Cluster Management
- Node Management
- Event Services
- High Availability
- Network Management (provides DNS/GNS/MDNSD services on behalf of other traditional services) and SCAN – Single Access Client Naming method, HAIP
- Storage Management (with help of ASM and other new ACFS filesystem)
- Time synchronization (rather depending upon traditional NTP)
- Removed OS dependent hang checker etc, manages with own additional monitor process
4.What is Grid Naming Service(GNS)?
Grid Naming service (GNS) is alternative service to Domain Naming Service (DNS) , which will act as a sub domain in your DNS but managed by Oracle, with GNS the connection is routed to the cluster IP and manages internally.
5.What are the file types that ASM support and keep in disk groups?
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 |
6.List Key benefits of ASM?
- Stripes files rather than logical volumes
- Provides redundancy on a file basis
- Enables online disk reconfiguration and dynamic rebalancing
- Reduces the time significantly to resynchronize a transient failure by tracking changes while disk is offline
- Provides adjustable rebalancing speed
- Is cluster-aware
- Supports reading from mirrored copy instead of primary copy for extended clusters
- Is automatically installed as part of the Grid Infrastructure
7.List some of the background process that used in ASM?
Process |
Description |
RBAL | Opens all device files as part of discovery and coordinates the rebalance activity |
ARBn | One or more slave processes that do the rebalance activity |
GMON | Responsible for managing the disk-level activities such as drop or offline 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 the ASM instance for exchanging messages |
PZ9n | One or more parallel slave processes used in fetching data on clustered ASM installation from GV$ views |
8.What is node listener?
In 11gr2 the listeners will run from Grid Infrastructure software home
- The node listener is a process that helps establish network connections 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 the same 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
9.What is the difference between CRSCTL and SRVCTL?
crsctl manages clusterware-related operations:
- Starting and stopping Oracle Clusterware
- Enabling and disabling Oracle Clusterware daemons
- Registering cluster resources
srvctl manages Oracle resource–related operations:
- Starting and stopping database instances and services
- Also from 11gR2 manages the cluster resources like network,vip,disks etc
10.How to find Voting Disk location?
To determine the location of the voting disk write the following command on Linux terminal as Root User:
# crsctl query css votedisk
11.What are types of ASM Mirroring?
Disk Group Type | Supported MirroringLevels | Default Mirroring Level |
External redundancy | Unprotected (None) | Unprotected (None) |
Normal redundancy | Two-wayThree-way
Unprotected (None) |
Two-way |
High redundancy | Three-way | Three-way |
12.What is ASM Striping?
ASM can use variable size data extents to support larger files, reduce memory requirements, and improve performance.
Each data extent resides on an individual disk.
Data extents consist of one or more allocation units.
The data extent size is:
- Equal to AU for the first 20,000 extents (0–19999)
- Equal to 4 × AU for the next 20,000 extents (20000–39999)
- Equal to 16 × AU for extents above 40,000
ASM stripes files using extents with a coarse method for load balancing or a fine method to reduce latency.
- Coarse-grained striping is always equal to the effective AU size.
- Fine-grained striping is always equal to 128 KB.
13.How many ASM Diskgroups can be created under one ASM Instance?
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.
14.How to find the cluster network settings?
To determine the list of interfaces available to the cluster:
$ oifcfg iflist –p -n
To determine the public and private interfaces that have been configured:
$ oifcfg getif
To determine the Virtual IP (VIP) host name, VIP address, VIP subnet mask, and VIP interface name:
$ srvctl config nodeapps -a
15.Managing or Modifying SCAN in Oracle RAC?
To add a SCAN VIP resource:
$ srvctl add scan -n cluster01-scan
To remove Clusterware resources from SCAN VIPs:
$ srvctl remove scan [-f]
To add a SCAN listener resource:
$ srvctl add scan_listener
$ srvctl add scan_listener -p 1521
To remove Clusterware resources from all SCAN listeners:
$ srvctl remove scan_listener [-f]
16.I’m going to do add disks to my ASM diskgroup, how long will this rebalance take?
Rebalance time is heavily driven by the three items:
- Amount of data currently in the diskgroup
- IO bandwidth available on the server
- ASM_POWER_LIMIT or Rebalance Power Level
17.We are migrating to a new storage array. How do I move my ASM database from storage A to storage B?
Given that the new and old storage are both visible to ASM, simply add the new disks to the ASM disk group and drop the old disks. ASM rebalance will migrate data online.
Note 428681.1 covers how to move OCR/Voting disks to the new storage array
18.Is it possible to unplug an ASM disk group from one platform and plug into a server on another platform (for example, from Solaris to Linux)?
No, Cross-platform disk group migration not supported. To move datafiles between endian-ness platforms, you need to use XTTS, Datapump or Streams.
19.How does ASM work with multipathing software?
It works great! Multipathing software is at a layer lower than ASM, and thus is transparent.
You may need to adjust ASM_DISKSTRING to specify only the path to the multipathing pseudo devices.