Getting ORA-01157: CANNOT IDENTIFY/LOCK DATA FILE xx When datafile is in ASM
(Doc ID 978335.1)
Last updated on DECEMBER 08, 2022
Applies to:
Oracle Database Exadata Express Cloud Service - Version N/A and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 11.1.0.6 and later
Information in this document applies to any platform.
Symptoms
Added a datafile to a tablespace on instance 2, but the asm diskgroup where the datafile is residing is not mounted in the node 1 (asm1). As a result, accessing the problem tablespace from instance 1 gives the following error:
ORA-01157: cannot identify/lock data file 37 - see DBWR trace file
ORA-01110: data file 37: '+<DG_NAME>/<INST_NAME>/datafile/<DATAFILENAME>'
Mounting the diskgroup in asm1 did not resolve the problem.
Accessing the same tablespace from instance 2 works fine.
Changes
Added a datafile to a tablespace on instance 2, but the asm diskgroup where the datafile is residing is not mounted in the node 1 (asm1)
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 |
| Changes |
| Cause |
| Solution |