ORA-38760: This database instance failed to turn on flashback database article 3, ora-38760flashback
ORA-38760: This database instance failed to turn on flashback database Article 3
Article 1
Article 2
Symptom:
The following information is displayed in the Database alert alarm log:
Completed: ALTER DATABASE MOUNTWed Nov 19 04:57:28 2014alter database openErrors in file /DBSoft/diag/rdbms/woo/woo/trace/woo_ora_5936.trc:ORA-38760: This database instance failed to turn on flashback databaseORA-38760 signalled during: alter database open...
Problem Analysis:
This error is returned after you view Metalink because the Flash back information is incomplete.
[oracle@db01 ~]$ oerr or 38760oerr: Unknown facility 'or'[oracle@db01 ~]$ oerr ora 3876038760, 00000, "This database instance failed to turn on flashback database"// *Cause: Database flashback is 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 database flashback.
At this time I tried to close the flash back based on previous experience, open the database again, or report ORA-38760 error, at this time, the alarm log only generated a woo_ora_5936.trc tracking file, which contains useful information.
At this time, I want to check the status of the flash back.
SQL> select flashback_on from v$database;FLASHBACK_ON------------------RESTORE POINT ONLY
Then, view 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_ROLLBACKSQL> drop restore point MACLEAN_ROLLBACK; Restore point dropped. SQL> select * from v $ restore_point; no rows selected2, start the database, and view the flashback status SQL> alter Database open; database altered. SQL> select flashback_on from v $ database; FLASHBACK_ON------------------NO
Summary:
This problem occurs because the control file is inconsistent with the information recorded in the Flash log file. Therefore, during cold backup, it is best to roll back the data together for backup.
Of course, you can also use the cold backup and flash back backup to directly start the database instance.