Instance Crashes when the Flashback Log is Inaccessible
(Doc ID 311150.1)
Last updated on FEBRUARY 19, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.1.0.4 [Release 10.1]
Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2]
Information in this document applies to any platform.
This problem can occur on any platform.
If the flashback logfile is inaccessible, the instance will crash.
It also means that if the current flashback logfile is lost, the instance will crash.
It means that losing this file will cause a database downtime.
Sample errors : When the current flashbacklog is deleted, then the database
will crash with the following errors:
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
RVWR: terminating instance due to error 38701
Instance terminated by RVWR, pid = ...
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