Chinaunix首页 | 论坛 | 博客
  • 博客访问: 1102690
  • 博文数量: 276
  • 博客积分: 10077
  • 博客等级: 上将
  • 技术积分: 2513
  • 用 户 组: 普通用户
  • 注册时间: 2007-08-24 20:31
文章分类

全部博文(276)

文章存档

2020年(1)

2015年(5)

2012年(2)

2011年(6)

2010年(7)

2009年(224)

2008年(31)

我的朋友

分类: Oracle

2009-07-16 21:19:41

This morning, I recover a database and forget to using the parameter 'UNTIL CANCEL'. Then open the database with resetlogs, it warn that system datafile is not consist. After read the online document, know that I am always confused about this concept. Remind it!

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

In cancel-based recovery, recovery proceeds by prompting you with the suggested filenames of archived redo log files. Recovery stops when you specify CANCEL instead of a filename or when all redo has been applied to the datafiles.

Cancel-based recovery is better than change-based or time-based recovery if you want to control which archived log terminates recovery. For example, you may know that you have lost all logs past sequence 1234, so you want to cancel recovery after log 1233 is applied.

RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE

The database indicates whether recovery is successful. If you cancel before all the datafiles have been recovered to a consistent SCN and then try to open the database, you will get an ORA-1113 error if more recovery is necessary. As explained in , you can query V$RECOVER_FILE to determine whether more recovery is needed, or if a backup of a datafile was not restored prior to starting incomplete recovery.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
阅读(903) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~