Explore topic-wise InterviewSolutions in Current Affairs.

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.

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.

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. In a MOMENT we will LOOK at how file I/O works with respect to the ASM instance.

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. In a moment we will look at how file I/O works with respect to the ASM instance.

ASM imposed 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):

1. External redundancy maximum file size is 140 PB.
2. Normal redundancy maximum file size is 42 PB.
3. High redundancy maximum file size is 15 PB.

ASM imposed the following limits:

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

• 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.

The data extent size is:

ASM stripes files using extents with a coarse method for load balancing or a fine method to reduce latency.

• 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

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

Control files:

Data files:

Temporary data files:

Online redo logs:

Archive logs:

No, ASM PROVIDES even distribution of extents ACROSS all disks in a disk group. Since each disk will EQUAL number of extents, no single disk will be hotter than another. Thus the answer NO, ASM does not dynamically move hot SPOTS, because hot spots simply do not occur in ASM configurations. Rebalance only occurs on storage configuration changes (e.g. add, DROP, or resize disks).

No, ASM provides even distribution of extents across all disks in a disk group. Since each disk will equal number of extents, no single disk will be hotter than another. Thus the answer NO, ASM does not dynamically move hot spots, because hot spots simply do not occur in ASM configurations. Rebalance only occurs on storage configuration changes (e.g. add, drop, or resize disks).

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.

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.

No. Cross-platform DISK group migration not SUPPORTED. To move datafiles between endian-ness PLATFORMS, you NEED to USE XTTS, Datapump or Streams.

No. Cross-platform disk group migration not supported. To move datafiles between endian-ness platforms, you need to use XTTS, Datapump or Streams.

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

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

REBALANCE TIME is heavily DRIVEN by the THREE items

1. AMOUNT of data currently in the diskgroup
2. IO bandwidth available on the server
3. ASM_POWER_LIMIT or Rebalance Power Level

Rebalance time is heavily driven by the three items

RMAN is the recommended and most COMPLETE and flexible method to backup and transport database files in ASM.

ASMCMD copy is good for copying SINGLE files:

• Supports all Oracle file types
• • Can be used to instantiate a DATA GUARD environment
• • Does not UPDATE the controlfile
• • Does not create OMF files

RMAN is the recommended and most complete and flexible method to backup and transport database files in ASM.

ASMCMD copy is good for copying single files:

Not APPLICABLE! ASM has no files to BACKUP, as its does not contain CONTROLFILE,redo LOGS etc.

Not applicable! ASM has no files to backup, as its does not contain controlfile,redo logs etc.

It is recommended to RUN the LISTENER from the ASM HOME. This is particularly important for RAC ENV, since the listener is a node-level resource. In this config, you can create additional [user] listeners from the DATABASE homes as needed.

It is recommended to run the listener from the ASM HOME. This is particularly important for RAC env, since the listener is a node-level resource. In this config, you can create additional [user] listeners from the database homes as needed.

YES. ASM can be at a HIGHER version or at lower version than its client databases. There’s two

• -components of compatiblity
• -Software COMPATIBILITY

Diskgroup compatibility ATTRIBUTES:

• compatible.asm
• compatible.rdbms

Yes. ASM can be at a higher version or at lower version than its client databases. There’s two

Diskgroup compatibility attributes:

For clarification:

• SEPARATE Oracle Home for ASM and RDBMS.
• RDBMS instance connects to ASM USING OSDBA group of the ASM instance.
• Thus, software owner for each RDBMS instance CONNECTING to ASM must bea member of ASM's OSDBA group.
• CHOOSE a different OSDBA group for ASM instance (asmdba) than forRDBMS instance (dba)
• In 11g, ASM administrator has to be member of a separate SYSASM group toseparate ASM Admin and DBAS.

For clarification:

There is no best size! In most CASES the storage team will dictate to you based on their standardized LUN size. The ASM ADMINISTRATOR merely has to communicate.

the ASM Best Practices and application characteristics to storage folks :

• Need equally sized / PERFORMANCE LUNs
• Minimum of 4 LUNs
• The capacity requirement
• The workload characteristic (RANDOM r/w, SEQUENTIAL r/w) & any response time SLA

Using this info , and their standards, the storage folks should build a nice LUN group set for you.

There is no best size! In most cases the storage team will dictate to you based on their standardized LUN size. The ASM administrator merely has to communicate.

the ASM Best Practices and application characteristics to storage folks :

Using this info , and their standards, the storage folks should build a nice LUN group set for you.

The use of Bigfile tablespaces has no bearing on ASM (or vice VERSA). In FACT most database object related DECISIONS are transparent to ASM.

The use of Bigfile tablespaces has no bearing on ASM (or vice versa). In fact most database object related decisions are transparent to ASM.

For 11G ASM/RDBMS it is recommended to USE 4MB ASM AU for disk GROUPS. See Metalink NOTE 810484.1

For 11g ASM/RDBMS it is recommended to use 4MB ASM AU for disk groups. See Metalink Note 810484.1

For VLDBs you will probably end up with different storage TIERS; e.g with some of our LARGE customers they have Tier1 (RAID10 FC), Tier2 (RAID5 FC), Tier3 (SATA), etc. Each ONE of these is mapped to a diskgroup.

For VLDBs you will probably end up with different storage tiers; e.g with some of our large customers they have Tier1 (RAID10 FC), Tier2 (RAID5 FC), Tier3 (SATA), etc. Each one of these is mapped to a diskgroup.

Oracle recommends TWO disk GROUPS to PROVIDE a balance of MANAGEABILITY, UTILIZATION, and performance.

Oracle recommends two disk groups to provide a balance of manageability, utilization, and performance.

No. The RDBMS does I/O DIRECTLY to the raw DISK devices, the FILESYSTEMIO_OPTIONS PARAMETER is only for filesystems.

No. The RDBMS does I/O directly to the raw disk devices, the FILESYSTEMIO_OPTIONS parameter is only for filesystems.

ASM is not in the I/O PATH so ASM does not impede the database file access. Since the RDBMS instance is performing RAW I/O, the I/O is as fast as possible.

ASM is not in the I/O path so ASM does not impede the database file access. Since the RDBMS instance is performing raw I/O, the I/O is as fast as possible.

The default parameter settings work perfectly for ASM.

The only parameters NEEDED for 11G ASM:

• PROCESSES*
• ASM_DISKSTRING*
• ASM_DISKGROUPS
• INSTANCE_TYPE

The default parameter settings work perfectly for ASM.

The only parameters needed for 11g ASM:

The database communicates with ASM instance using the ASMB (umblicus process) process. Once the database obtains the necessary EXTENTS from extent MAP, all database IO going forward is processed through by the database processes, bypassing ASM. Thus we SAY ASM is not really in the IO PATH.

The database communicates with ASM instance using the ASMB (umblicus process) process. Once the database obtains the necessary extents from extent map, all database IO going forward is processed through by the database processes, bypassing ASM. Thus we say ASM is not really in the IO path.

Automatic STORAGE Management (ASM) instance. Instance that MANAGES the diskgroup metadata

Disk Groups:

• Logcal grouping of DISKS
• Determines file mirroring options

ASM Disks:

• LUNs presented to ASM

ASM Files:

Files that are stored in ASM disk groups are called ASM files, this includes database files

NOTES:

• Many databases can CONNECT as clients to single ASM instances
• ASM instance name should only be +ASM only
• One diskgroup can serve many databases

Automatic Storage Management (ASM) instance. Instance that manages the diskgroup metadata

Disk Groups:

ASM Disks:

ASM Files:

Files that are stored in ASM disk groups are called ASM files, this includes database files

Notes:

ASM provides filesystem and VOLUME manager capabilities built into the Oracle database kernel. Withthis capability, ASM simplifies storage management tasks, such as creating/laying out databases and disk space management. Since ASM allows disk management to be done using familiar create/alter/drop SQL statements, DBAs do not need to learn a new skill set or make crucial decisions on provisioning.

The following are some key benefits of ASM:

• ASM spreads I/O evenly across all available disk drives to prevent hot spots and maximize performance.
• ASM eliminates the need for over provisioning and maximizes storage resource utilization facilitating database consolidation.
• INHERENT large file support.
• Performs automatic online redistribution after the incremental addition or removal of storage capacity.
• Maintains redundant copies of data to provide high availability, or leverages 3rd party RAID functionality.
• Supports Oracle Database as WELL as Oracle Real Application Clusters (RAC).
• Capable of leveraging 3rd party multipathing TECHNOLOGIES.
• For simplicity and easier migration to ASM, an Oracle database can contain ASM and non-ASM files.
• Any new files can be created as ASM files whilst existing files can also be migrated to ASM.
• RMAN commands enable non-ASM managed files to be relocated to an ASM disk group.
• Enterprise Manager Database Control or Grid Control can be used to manage ASM disk and file activities.

ASM provides filesystem and volume manager capabilities built into the Oracle database kernel. Withthis capability, ASM simplifies storage management tasks, such as creating/laying out databases and disk space management. Since ASM allows disk management to be done using familiar create/alter/drop SQL statements, DBAs do not need to learn a new skill set or make crucial decisions on provisioning.

The following are some key benefits of ASM:

In Oracle Database 10g/11g there are two types of instances: database and ASM instances. The ASM instance, which is generally named +ASM, is started with the INSTANCE_TYPE=ASM init.ora parameter. This parameter, when SET, signals the Oracle initialization routine to start an ASM instance and not a standard database instance. Unlike the standard database instance, the ASM instance contains no physical files; such as logfiles, controlfiles or datafiles, and only requires a few init.ora parameters for startup.

Upon startup, an ASM instance will spawn all the basic background processes, plus some NEW ones that are specific to the operation of ASM. The STARTUP clauses for ASM instances are similar to those for database instances. For example, RESTRICT prevents database instances from connecting to this ASM instance. NOMOUNT starts up an ASM instance without mounting any disk group. MOUNT option simply MOUNTS all DEFINED diskgroups For RAC configurations, the ASM SID is +ASMx instance, where X represents the instance number.

In Oracle Database 10g/11g there are two types of instances: database and ASM instances. The ASM instance, which is generally named +ASM, is started with the INSTANCE_TYPE=ASM init.ora parameter. This parameter, when set, signals the Oracle initialization routine to start an ASM instance and not a standard database instance. Unlike the standard database instance, the ASM instance contains no physical files; such as logfiles, controlfiles or datafiles, and only requires a few init.ora parameters for startup.

Upon startup, an ASM instance will spawn all the basic background processes, plus some new ones that are specific to the operation of ASM. The STARTUP clauses for ASM instances are similar to those for database instances. For example, RESTRICT prevents database instances from connecting to this ASM instance. NOMOUNT starts up an ASM instance without mounting any disk group. MOUNT option simply mounts all defined diskgroups For RAC configurations, the ASM SID is +ASMx instance, where x represents the instance number.