Unable to Start CRS After Restoring the Failed Hardware with a New ASM Disk Name
(Doc ID 1463719.1)
Last updated on JANUARY 24, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1 and laterOracle 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.
Symptoms
Unable to start CRS even after restoring the failed hardware.
2 Node RAC.
There was a HBA failure and a disk failure on Node2
After replacing the HBA card, it changed the device id's. specifically the controller id was changed from 6 to 0
old device : /dev/rdsk/c6t60080E5...
New device : /dev/rdsk/c0t60080E5
The server uses mpxio and raw devices configured with ASM.
The CRS unable to start ASM and mount the disk group DG1 on the affected Node2.
This Diskgroup contains the Voting Disk
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |