Ora-38760:this database instance failed to turn on flashback database third article
First article
Second article
Problem phenomenon:
See the following information in the Database Alert alert log:
Completed:alter database MOUNT
Wed Nov 04:57:28 2014
ALTER DATABASE open
Errors in file/dbsoft/diag/ RDBMS/WOO/WOO/TRACE/WOO_ORA_5936.TRC:
Ora-38760:this Database instance failed to turn on flashback database
ORA-38760 signalled during:alter database open ...
Problem Analysis:
The error was learned after viewing the Metalink because the flash back information was incomplete.
[Oracle@db01 ~]$ oerr or 38760
oerr:unknown facility ' or ' [Oracle@db01 ~]$ oerr ora, 38760 38760, 00000
, "this Database instance failed to turn on flashback database "
//*cause:database flashback are on but this instance failed To
// start generating flashback data. Look in alert log for more
// specific errors.
*action:correct the error or turn off the database flashback.
This time I based on previous experience to try to turn off flashback, open the database again, or reported ORA-38760 error, at this point, the alarm log only produced a woo_ora_5936.trc trace file, which has seen useful information.
This time, I think I need to check the status of the flash back.
Sql> select flashback_on from V$database;
flashback_on
------------------
RESTORE Point only
And then review the recovery checkpoint:
Sql> select * from V$restore_point;
SCN database_incarnation# GUA storage_size time restore_point_time PRE NAME
--------------------------- ------------------------------------------------------------------------------------------------------
1187867 2 Yes 3056812032 04-oct-14 02.41.43.000000000 AM Yes Maclean_rollback
Solution:
1, delete the recovery point maclean_rollback
sql> drop restore points maclean_rollback;
Restore Point dropped.
Sql> select * from V$restore_point;
No rows selected
2, start the database, and view flashback status
sql> ALTER DATABASE open;
Database altered.
Sql> select flashback_on from V$database;
flashback_on
------------------
NO
Summary:
The control file is not consistent with the information recorded in the Flash back log file When this problem occurs. Therefore, when the cold backup, it is best to flash back together for backup.
Of course the problem can also be started directly by using a cold standby plus a backup for flashing back.