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)
#Oracle 10g poster manual#
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.
Multitenant : Flashback of a Container Database (CDB) in Oracle Database 12c Release 1 (12.1).Flashback New Features and Enhancements in Oracle Database 10g.
In order to flashback the database you must have SYSDBA privilege and the flash recovery area must have been prepared in advance. The FLASHBACK DATABASE command is a fast alternative to performing an incomplete recovery, also known as a point-in-time recovery (PITR). Home » Articles » 10g » Here Flashback Database in Oracle Database 10g