My Oracle Support Banner

ORA-01157 Cannot Identify Lock On Datafile Error During Upgrade (Doc ID 1917635.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 11.2.0.4 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.

Symptoms

ALTER DATABASE OPEN MIGRATE
ERROR: clonedb parameter not set. Make sure clonedb=TRUE is set
Errors in file /oracle/admin/DB/diag/rdbms/db/DB_new/trace/DB_new_dbw0_31749.trc:
ORA-01157: cannot identify/lock data file 107 - see DBWR trace file
ORA-01110: data file 107: '/dev/mapper/oraDB_data_008_4600Mp3'
ORA-17503: ksfdopn:1 Failed to open file /dev/mapper/oraDB_data_008_4600Mp3
ORA-17515: Creation of clonedb failed using snapshot file

Changes

 Datafile is corrupt or not restored properly from backup.

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
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.