Getting ORA-01157: CANNOT IDENTIFY/LOCK DATA FILE 37 when datafile is in ASM (Doc ID 978335.1)

Last updated on AUGUST 05, 2015

Applies to:

Oracle Server - Enterprise Edition - Version 11.1.0.6 and later
Information in this document applies to any platform.

Symptoms


Comments
--------
=== 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.


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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms