Unable to open the database in read only mode after restore/recovery
(Doc ID 316154.1)
Last updated on JANUARY 30, 2020
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 to 188.8.131.52 [Release 8.1.7 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
This article address the reasons behind failure of opening the database in read only mode. It discuss the ways to open the database in read only mode.
This is intended for DBA and Oracle Support personnel.
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
|Case 1: When database is mounted using current controlfile , datafiles are restored from cold backup|
|Case 2: When controlfile is recreated and datafiles are restored from cold backup.|
|Case 3: When controlfile is from earlier cold backup than datafiles.|
|Case 4: READ ONLY tablespaces, which never have switched to READ WRITE after a RESETLOGS|