Justin Mungal wrote:good explanation Justin.... :)
As SB mentioned, Flashback Database requires downtime. When troubleshooting individual transactions in production, such as a job gone awry, you would be better off making use of Flashback Technology that operates at the logical level, which use UNDO as opposed to flashback logs. Please study the following carefully.
Use Flashback Database in your production environment as a replacement for traditional point-in-time media recovery, when physical corruption is not the issue (see http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmflash.htm#BGBDCAFA for more information on this). Flashback Database can be preferable to traditional media recovery because it does not restore the entire database, rather, it rewinds changes that have been made to it.
You can also use LogMiner to analyze changes made to the database. It's easier to use than you might expect.
Think of it this way: Flashback Database is drastic, and is designed as a potential alternative to media recovery. It rewinds the entire database and requires downtime. Flashback Technology such Flashback Transaction or Flashback Query let you analyze and make changes at the object/transaction level, and are designed to assist you in troubleshooting and reversing erroneous changes made to the database. There may be times when Flashback Database is necessary, but consider alternative options first. I hope this clears things up for you slightly.
Main objective is to show that in using Flashback Database, the DBA has great flexibility and control over in determine the best Point-in-Time recovery.
No - Flashback is AN ALTERNATIVE to using point-in-time recovery.
Secondary objective is to show that Flashback Database can be used to determine the time of error occurred.
No - Flashback won't determine anything at all. YOU have to determine if there was an error and, if so, what time the error occured. Flashback can assist you by giving you more efficient access to the entire database from a previous savepoint or point-in-time.