Troubleshooting a multi-node ASMLib installation
(Doc ID 811457.1)
Last updated on AUGUST 04, 2018
Applies to:Linux OS - Version 2.0.0-1 to 2.0.5-1 [Release RHEL4 to OL5]
Information in this document applies to any platform.
Linux Kernel - Version: 2.0.0-1 to 2.0.5-1
***Checked for relevance on 28-Jul-2011***
***Checked for relevance on 06-Sep-2015***
This procedure will verify that a new or existing Oracle ASMLib installation is configured correctly and operating properly across each node of a cluster. An important supplementary document is the Technical Information section of the Oracle ASMLib homepage and ASMLib Installation Guide. Metalink note references at the end of this document provide additional troubleshooting resources.
A properly installed and fully functional ASMLib installation requires the following:
1. The minimal set of ASMLib packages
2. The ASMLib system must be initially configured and a valid /etc/sysconfig/oracleasm file in place on all nodes
3. The shared devices (LUNs) for the Oracle ASMLib devices must properly partitioned and available with consistent and repeatable naming (across reboots) on all nodes
4. The oracleasm service must start and be running without errors on all nodes
Generic, cut and paste commands provide a 15 minute, step-by-step verification procedure for each of these requirements. Commands in bold are shortcut indicators for experienced system administrators that highlight the most important steps.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. ASMLib Installation Package checks|
|2. ASMLib Service Checks|
|3. ASMLib LUN and Naming Checks|
|4. Final Service Checks|