Alejandro Vargas' Blog

ASMLib provide an easy way to present storage to ASM on Linux, it takes care of device labeling and improves the performance of open-close calls to the devices. Is Oracle Best Practice for managing disks on Linux.

Lab2-Install-and-Configure-ASMLib.pdf

The following points are covered on this lab:

Install The ASMLib:

Cheking The Kernel Version
Downloading the Drivers for ASMLib
Installing the ASMLib Drivers

Configure ASMLib :

Create ASM Disks
ASMLib Directory Structures
ASM Directories
ASM files on /opt directory
Map ASMLib Disks to Physical Devices
File /etc/sysconfig/oracleasm
ASM init file

Annex:

Scripts

On this Lab we create the ASM instance on a single instance environment, and create ASM diskgroups in several different ways using different kind of devices. Note that these exercises provide some degree of confidence on managing devices but are valid only for training.

On a production environment we will use mostly a high end SAN or NAS storage, usually connected by fiber channel, and we will provision LUN's for ASM.

The lab can be accessed here : Lab3-Create-ASM-Instance-and-Managing-Diskgroups.pdf

Lab Index

Create The ASM Instance
Create the Cluster Synchronization Services Daemon
Configure and Start a Listener
Sizing the ASM Shared Pool
Setup a minimal ASM Pfile
Disk Discovery
Discovering Raw Devices
Discovering Block Devices
Discovering ASMLib Devices
Creating Disk Groups Using Loop Devices
KFED
Build the Kfed Utility
Kfed Help
Check Disk Headers Using Kfed
Creating Normal Redundancy Disk Groups Using Block Devices
Comparing External And Normal Redundancy Disk Using Kfed
Using File System Based Files As ASM Disks
Creating a diskgroup on ASM based on files
Check the diskgroups created on this Lab
Scripts

Oracle Input Output Numbers, ORION, provides a simple way to check storage performance before the Oracle Database is created, that gives us a clean storage performance report that can be compared with the awr IO statistics once the database is running.
When performance problems related to poor performance at the storage level are detected in a late implementation stage the number of variables may make the task to detect the bottleneck difficult, and the time to find a solution scarce.

Orion can simulate the type of IO's an OLTP or DSS system does and provide detailed response times in terms of IOPS and MBPS.

The lab can be downloaded here: Lab 4, Install, Configure and Run ORION

Lab Index:

Download
Install
Running a Simple Test
Orion Generated Reports
Running and advanced test

One of the ways to migrate a database to ASM is to use the Rman “Backup as Copy” command to create a database copy into ASM storage and then switch the database to the copy.

This technique can be used, combined with incremental backups, to move even very large databases into ASM.

The first backup may take a long time, one or more incremental backups can be used to update the first backup and close the gap, until a downtime window is obtained to switch the database on filesystem to the backup on ASM.

This Lab can be downloaded here: Using RMAN To Migrate a Database Into ASM

Lab Topics:

Summary
Migrating a Database Into ASM
Backup Database Into ASM
Spfile Backup into ASM
Consistent database shutdown
Prepare Pfile for the ASM Database
Start the database in NOMOUNT mode
Change Parameters on Spfile to point to ASM
Move the controlfiles into ASM
Switch the Database from File System to ASM
Recover The Database
Migrate the Temporary Datafiles to ASM
Move Flashback logs into flash recovery Area
Move RMAN Change Tracking File Into ASM
Remove the File System Old Files
Remove the Old Spfile from Filesystem
Scripts