the moment that you run the command, it has the following limitations:
因为闪回数据库工作采用回滚数据文件改变,那些在你运行命令时已经存在的。
闪回DB存在以上限制:
database. It cannot be used to repair media failures, or to recover from accidential
deletion of datafiles.
#FD仅能回滚被ORACLE数据库修改的数据文件,它不能修复介质失败或者从被删除文件
的事故中还原。
■ If the database control file is restored from backup or re-created, all accumulated
flashback log information is discarded. You cannot use FLASHBACK DATABASE to
return to a point in time before the restore or re-creation of a control file.
#你不能使用FD去回滚数据文件的SHRINK操作。
#如果数据库控制文件从备份里修复或者重建,所有累积的闪回日志信息将失效。你不能使用
FD去返回到修复或重建控制文件的时间点。
operation was in progress, block corruption is likely in the database objects and
datafiles affected by the NOLOGGING operation. For example, if you perform a
direct-path INSERT operation in NOLOGGING mode, and that operation runs
from 9:00 to 9:15 on April 3, 2005, and you later need to use Flashback Database to
return to the target time 09:07 on that date, the objects and datafiles updated by
the direct-path INSERT may be left with block corruption after the Flashback
Database operation completes.
#当使用FD使用一个目标时间,在那个时间一个NOLOGGING操作在那个过程中,
块的损坏可能存在于数据库的对象里并且数据文件通过NOLOGGING操作影响。比如
你执行一个直接的插入操作在NOLOGGING模式,并且那个操作在2005年4月3号的9:00
-9:15执行,而后你需要将数据库返回到目标时间09:07那个点,对象和数据文件的更新通过
直接插入将遗留坏块问题在FD操作完成后。
coincides with a NOLOGGING operation. Also, perform a full or incremental
backup of the affected datafiles immediately after any NOLOGGING operation to
ensure recoverability to points in time after the operation. If you expect to use
Flashback Database to return to a point in time during an operation such as a
direct-path INSERT, consider performing the operation in LOGGING mode.
如果可以,避免使用FD使用一个目标时间或SCN,那些要求一个NOLOGGING操作保持
一致性。另外快速执行一个全备份或者受影响的数据文件的增量备份在任何的NOLOGGING
操作后去确保可还原到NOLOGGING操作后的时间点。如果你预期使用FD去返回到一个时间点
,它属于在执行直接路径插入的操作过程,确定执行的操作在LOGGING模式下进行。