Getting ORA-01157: CANNOT IDENTIFY/LOCK DATA FILE xx When datafile is in ASM
(Doc ID 978335.1)
Last updated on OCTOBER 30, 2019
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
=== ODM Issue Clarification ===
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.
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)
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