My Oracle Support Banner

Flashback Database to Timestamp on Physical Standby Fails with ORA-289 (Doc ID 2530015.1)

Last updated on DECEMBER 05, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms

FLASHBACK DATABASE TO TIMESTAMP on physical standby database fails:

SQL> flashback database to timestamp to_date('2019-02-06 23:46:02','YYYY-MM-DD HH24:MI:SS');
flashback database to timestamp to_date('2019-02-06 23:46:02','YYYY-MM-DD HH24:MI:SS');
*
ERROR at line 1:
ORA-38770: FLASHBACK DATABASE failed during recovery.
ORA-00279: change 2221879 generated at 02/06/2019 23:44:20 needed for thread 1
ORA-00289: suggestion: <archive directory>/dg_1_0000000005_999560628.arc
ORA-00280: change 2221879 for thread 1 is in sequence 5

Changes

This problem occurs like the following steps at standby database.

1. convert to snapshot standby from physical standby.

SQL> recover managed standby database cancel;
SQL> alter database convert to snapshot standby;
SQL> shutdown immediate
SQL> startup

2. convert back to physical standby.

SQL> shutdown immediate
SQL> startup mount
SQL> alter database convert to physical standby;
SQL> shutdown immediate
SQL> startup mount
SQL> recover managed standby database using current logfile disconnect;

3. failover

SQL> recover managed standby database cancel;
SQL> alter database activate physical standby database;
SQL> alter database open;

4. flashback with a time earlier than the time when failover is performed.

SQL> flashback database to timestamp to_date('2019-02-06 23:46:02','YYYY-MM-DD HH24:MI:SS');

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.