Linux-x86_64 Error: 2: No such file or directory "/u01/app/oracle/fast_recovery_area/CDB/flashback/o1_mf_hg6h7dyn_.flb" ORA-38701: Flashback database log 1 seq 1 thread 1: If flashback logs are missing, you may find the V$RESTORE_POINT view is not working. You can then drop the restore points, which will allow you to open the database. If you can, query the restore points from the V$RESTORE_POINT view. ORA-38760: This database instance failed to turn on flashback database On some occasions you will get ORA-38760 errors and the database won't start. To flashback to this restore point, we would issue the following command.įlashback database to restore point before_changes Įxisting restore points can be dropped as follows.ĭrop restore point before_changes ORA-38760 You should delete all unnecessary guaranteed restore points.Ĭreate restore point before_changes guarantee flashback database Įxisting restore points can be displayed using the V$RESTORE_POINT view. A guaranteed restore point means the database doesn't delete any flashback logs between that point and the current time. A restore point is just a text alias representing a SCN. In addition to using SCNs and timestamps, we can create restore points and guaranteed restore points. It is only possible to flashback to a point in time after flashback was enabled on the database and since the last resetlogs command. The maximum flashback can be determined by querying the V$FLASHBACK_DATABASE_LOG view. The window of time that is available for flashback is determined by the DB_FLASHBACK_RETENTION_TARGET parameter. Some other variations of the flashback database command include the following.įlashback database to timestamp In the following example a table is created, the database is then flashbacked to a time before the table was created.įlashback the database to 5 minutes previous, to before the test table was created.įlashback database to timestamp sysdate-(1/24/12) With flashback enabled the database can be switched back to a previous point-in-time or SCN without the need for a manual incomplete recovery. As a result, you could just issue the following.įor 10g and 11gR1 releases, the database needs to be restarted to achieve this, as follows. In Oracle 11gR2, this process was simplified, allowing flashback database to be enabled/disabled without the need for a database restart. If the database is in NOARCHIVELOG it must be switched to ARCHIVELOG mode.Īlter system set log_archive_dest_1='location=d:\oracle\oradata\DB10G\archive\' scope=spfile Īlter system set log_archive_format='ARC%S_%R.%T' scope=spfile įlashback must be enabled before any flashback operations are performed. The FLASHBACK_ON column of the V$DATABASE view shows the current status of flashback database.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |