Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Guaranteed restore point won't allow flashback in MOUNT state

Rob_JJan 20 2011 — edited Jan 21 2011
Hello,

Oracle Version: 11.2.0.2
OS Version: Windows Server 2003

I have a problem whereby I can't flashback my database to a guaranteed restore point. I have two guaranteed restore points; the first taken when the DB was version 10.2.0.4, before I upgraded the DB, and the second taken after the 11.2.0.2 upgrade. Here they are:
SQL> select GUARANTEE_FLASHBACK_DATABASE,TIME,PRESERVED,NAME from v$restore_point;

GUA TIME                                                                        PRE NAME
--- --------------------------------------------------------------------------- --- ------------------
YES 19-JAN-11 15.43.37.000000000                                                YES PRE_CHANGE_FLXCUT
YES 19-JAN-11 17.23.37.000000000                                                YES POST_11G_UPGRADE
I now want to flashback to the restore point called POST_11G_UPGRADE and this is what's happening:
SQL> select log_mode, open_mode from v$database;

LOG_MODE     OPEN_MODE
------------ --------------------
ARCHIVELOG   MOUNTED

SQL> FLASHBACK DATABASE TO RESTORE POINT POST_11G_UPGRADE;
FLASHBACK DATABASE TO RESTORE POINT POST_11G_UPGRADE
*
ERROR at line 1:
ORA-16433: The database must be opened in read/write mode.

SQL> alter database open read write;

Database altered.

SQL> FLASHBACK DATABASE TO RESTORE POINT POST_11G_UPGRADE;
FLASHBACK DATABASE TO RESTORE POINT POST_11G_UPGRADE
*
ERROR at line 1:
ORA-38757: Database must be mounted and not open to FLASHBACK.
I should also point out that after creating the 2nd guaranteed restore point, I enabled a capture process for Real Application Testing and run in a load of DB actions so I could capture the load, then flash back, make some parameter settings and re-run the captured workload against the DB.

Has anyone seen this before? Or perhaps you may have any comments about why this is happening?

Thanks,
Rob
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Feb 18 2011
Added on Jan 20 2011
11 comments
2,781 views