My Oracle Support Banner

OpenVMS: ORA-1110, ORA-1157, ORA-27037 When Using DB_FILE_NAME_CONVERT (Doc ID 353204.1)

Last updated on SEPTEMBER 15, 2023

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 9.0.1 to 10.2]
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
HP OpenVMS Alpha
HP OpenVMS Itanium



The following errors are reported in the Alert log of a standby database when using the INIT parameter DB_FILE_NAME_CONVERT to replace primary datafile locations with standby datafile locations :

ORA-01157: cannot identify/lock data file # - see DBWR trace file
ORA-01110: data file #: '<filename specification>'
ORA-27037: unable to obtain file status
MRP0: Background Media Recovery terminated with error 1110

MRP0: Background Media Recovery process shutdown

Depending on the current configuration and actions being done (for example adding a new datafile to the primary database), the following errors may also be seen :

ORA-600: internal error code, arguments: [3051]

ORA-600: internal error code, arguments: [kcbkubc_1]

ORA-01119: error in creating database file '<filename specification>'

ORA-1516 signalled during: alter database create datafile '<filename specification>'


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

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