Getting ORA-01157: CANNOT IDENTIFY/LOCK DATA FILE 37 when datafile is in ASM
Last updated on MARCH 21, 2018
Applies to:Oracle Server - Enterprise Edition - Version 126.96.36.199 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: '+DATA02/tqa01/datafile/tradebeam_data.306'
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)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms