ASMLIB::libasm.so version failed with 2 :cluster is down after reboot
(Doc ID 1559308.1)
Last updated on JANUARY 24, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
After rebooting the node cluster is not coming up.
As asm instance was not able to see devices at OS level.
From ASM alertlog file,
NOTE: cache registered group <DGNAME> number=3 incarn=0xfcc8f30e
NOTE: cache began mount (not first) of group <DGNAME> number=3 incarn=0xfcc8f30e
ASM Health Checker found 1 new failures
ERROR: no read quorum in group: required 2, found 0 disks
NOTE: cache dismounting (clean) group 3/0xFCC8F30E (<DGNAME>)
NOTE: messaging CKPT to quiesce pins Unix process pid: 18002, image: oracle@<HOSTNAME>.<DOMAIN_NAME> (TNS V1-V3)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 3/0xFCC8F30E (<DGNAME>)
NOTE: cache ending mount (fail) of group <DGNAME> number=3 incarn=0xfcc8f30e
NOTE: cache deleting context for group <DGNAME> 3/0xfcc8f30e
Mon Jun 03 22:31:35 2013
ERROR: -14(asmlib /opt/oracle/extapi/64/asm/orcl/1/libasm.so version failed with 2
GMON dismounting group 3 at 10 for pid 25, osid 18002
ERROR: diskgroup <DGNAME> was not mounted
ORA-15032: not all alterations performed
ORA-15017: diskgroup "<DGNAME>" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup "<DGNAME>"
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