oracle-归档和非归档模式

数据库可以运行在归档和非归档两种模式下。

一、非归档和归档模式介绍

非归档模式——建库以后，数据库默认是在非归档模式的。
When you run your database in NOARCHIVELOG mode, you disable the archiving of the redo log. The database control file indicates that filled groups are not required to be archived. Therefore, when a filled group becomes inactive after a log switch, the group is available for reuse by LGWR.
当你将库运行在非归档模式，将没有归档日志。数据库的控制文件将控制满的日志组不被要求做归档。因此，在日志切换后，满的日志组状态将变为inactive，这个组是available状态，可以被LGWR重新使用。

NOARCHIVELOG mode protects a database from instance failure but not from media failure. Only the most recent changes made to the database, which are stored in the online redo log groups, are available for instance recovery. If a media failure occurs while the database is in NOARCHIVELOG mode, you can only restore the database to the point of the most recent full database backup. You cannot recover transactions subsequent to that backup.
非归档模式只能保护实例失败情况，无法保护介质损坏。仅仅最近的改变被保存在数据库中，他们存储在online redo log中，被用于instance recover。如果一个介质损坏发生在非归档模式的数据库，你只能使用最近时间点的全备，恢复到备份时间点。你不能恢复备份时间点到故障时间点之间的数据。

In NOARCHIVELOG mode you cannot perform online tablespace backups, nor can you use online tablespace backups taken earlier while the database was in ARCHIVELOG mode. To restore a database operating in NOARCHIVELOG mode, you can use only whole database backups taken while the database is closed. Therefore, if you decide to operate a database in NOARCHIVELOG mode, take whole database backups at regular, frequent intervals.
在非归档模式，你不能执行online tablespace备份，但是在归档模式，你可以很容易的做online tablespace 的备份。在非归档模式做restore a database操作，你只能用全库备份并且数据库是在关闭状态。因此，如果你决定操作一个数据库在非归档模式，做全库备份需要定期的、频繁的间隔。

归档模式——生产库大部分采用这种模式
When you run a database in ARCHIVELOG mode, you enable the archiving of the r