My Oracle Support Banner

Flashback is automatically turned off due to OS-errors (Doc ID 1270306.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.1 to 11.2]
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)


Customer uses fallowing configuration:

Windows Platform, no RAC, physical standby database.

Within alert.log on physical standby fallowing errors are reported:

Tue Nov 09 15:22:35 2010
Media Recovery Waiting for thread 1 sequence 149 (in transit)
Recovery of Online Redo Log: Thread 1 Group 21 Seq 149 Reading mem 0
Tue Nov 09 15:22:51 2010
RVWR I/O error (a1261200, 959, 35946496, 4)
Errors in file d:\<PATH>\oracle\admin\diag\rdbms\<PATH>\trace\<FILE_NAME>.trc:
ORA-38701: Flashback database log 236 seq 331 thread 1: "D:\<PATH>\FLASHBACK\<PATH>\FLASHBACK\<FILE_NAME>.FLB"
ORA-27070: async read/write failed
OSD-04008: WriteFile() failure, unable to write to file
O/S-Error: (OS 1450) Insufficient system resources exist to complete the requested service.
RVWR stuck due to I/O error when writing flashback database logs.
See error stack in alert for details of the I/O error.
To shutdown RVWR, you may shutdown abort the instance or
turn off flashback database.
Tue Nov 09 15:23:10 2010


Due to this errors flashback will be disabled to avoid a instance crash.
Since flashback is disabled no flashback logs will be written anymore, flashback
(e.g. in case of failover) will not be possible.


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.