最近在学习rman,恢复的时候报错，大家看看，怎么解决
SQL> alter database open ;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-19901: database needs more recovery to create new incarnation
网上关于ora-19901的处理好少啊
SQL> alter database open ;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-19901: database needs more recovery to create new incarnation
网上关于ora-19901的处理好少啊
---------------------------
首先感谢大家的帮助，
1、sqlplus下
recover database until cancel;
2、rman下
restore database;
recover database;
这个方法不行，一，我没有全表备份，二，我备份了spfile,controlfile,archivelog,spfile和controlfile我都恢复了，没有异常的问题，主要是archivelog file ，我之前做过backup archivelog all delete input ;后来又重新备份的时候还是这个语句，我在想是不是第一次备份删除了日志文件，第二次备份的时候删除的文件找不到了，所以恢复的时候出现问题了??
恢复的时候部分错误信息：
RMAN-03002: failure of recover command at 06/03/2011 09:09:32
RMAN-06053: unable to perform. media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 2429 lowscn 997181116 found to restore
RMAN-06025: no backup of log thread 1 seq 2428 lowscn 997173052 found to restore
RMAN-06025: no backup of log thread 1 seq 2427 lowscn 997165018 found to restore
RMAN-06025: no backup of log thread 1 seq 2426 lowscn 997156390 found to restore
RMAN-06025: no backup of log thread 1 seq 2425 lowscn 997148327 found to restore
RMAN-06025: no backup of log thread 1 seq 2424 lowscn 997142921 found to restore
RMAN-06025: no backup of log thread 1 seq 2423 lowscn 997139905 found to restore
RMAN-06025: no backup of log thread 1 seq 2422 lowscn 997137418 found to restore
RMAN-06025: no backup of log thread 1 seq 2421 lowscn 997132151 found to restore
RMAN-06025: no backup of log thread 1 seq 2420 lowscn 997122744 found to restore
RMAN-06025: no backup of log thread 1 seq 2419 lowscn 997114426 found to restore
RMAN-06025: no backup of log thread 1 seq 2418 lowscn 997105934 found to restore
RMAN-06025: no backup of log thread 1 seq 2417 lowscn 997097451 found to restore
RMAN-06025: no backup of log thread 1 seq 2416 lowscn 997090221 found to restore
RMAN-06025: no backup of log thread 1 seq 2415 lowscn 997083259 found to restore
RMAN-06025: no backup of log thread 1 seq 2414 lowscn 997080987 found to restore
RMAN-06025: no backup of log thread 1 seq 2413 lowscn 997072936 found to restore
RMAN-06025: no backup of log thread 1 seq 2412 lowscn 997065308 found to restore
RMAN-06025: no backup of log thread 1 seq 2411 lowscn 997057305 found to restore
RMAN-06025: no backup of log thread 1 seq 2410 lowscn 997049490 found to restore
RMAN-06025: no backup of log thread 1 seq 2409 lowscn 997041050 found to restore
RMAN-06025: no backup of log thread 1 seq 2408 lowscn 997032588 found to restore
RMAN-06025: no backup of log thread 1 seq 2407 lowscn 997029224 found to restore
RMAN-06025: no backup of log thread 1 seq 2406 lowscn 997025167 found to restore
RMAN-06025: no backup of log thread 1 seq 2405 lowscn 997017988 found to restore
RMAN-06025: no backup of log thread 1 seq 2404 lowscn 997010350 found to restore
RMAN-06025: no backup of log thread 1 seq 2403 lowscn 997002302 found to restore
RMAN-06025: no backup of log thread 1 seq 2402 lowscn 996994913 found to restore
RMAN-06025: no backup of log thread 1 seq 2401 lowscn 996991338 found to restore
1、sqlplus下
recover database until cancel;
2、rman下
restore database;
recover database;
这个方法不行，一，我没有全表备份，二，我备份了spfile,controlfile,archivelog,spfile和controlfile我都恢复了，没有异常的问题，主要是archivelog file ，我之前做过backup archivelog all delete input ;后来又重新备份的时候还是这个语句，我在想是不是第一次备份删除了日志文件，第二次备份的时候删除的文件找不到了，所以恢复的时候出现问题了??
恢复的时候部分错误信息：
RMAN-03002: failure of recover command at 06/03/2011 09:09:32
RMAN-06053: unable to perform. media recovery because of missing log
RMAN-06025: no backup of log thread 1 seq 2429 lowscn 997181116 found to restore
RMAN-06025: no backup of log thread 1 seq 2428 lowscn 997173052 found to restore
RMAN-06025: no backup of log thread 1 seq 2427 lowscn 997165018 found to restore
RMAN-06025: no backup of log thread 1 seq 2426 lowscn 997156390 found to restore
RMAN-06025: no backup of log thread 1 seq 2425 lowscn 997148327 found to restore
RMAN-06025: no backup of log thread 1 seq 2424 lowscn 997142921 found to restore
RMAN-06025: no backup of log thread 1 seq 2423 lowscn 997139905 found to restore
RMAN-06025: no backup of log thread 1 seq 2422 lowscn 997137418 found to restore
RMAN-06025: no backup of log thread 1 seq 2421 lowscn 997132151 found to restore
RMAN-06025: no backup of log thread 1 seq 2420 lowscn 997122744 found to restore
RMAN-06025: no backup of log thread 1 seq 2419 lowscn 997114426 found to restore
RMAN-06025: no backup of log thread 1 seq 2418 lowscn 997105934 found to restore
RMAN-06025: no backup of log thread 1 seq 2417 lowscn 997097451 found to restore
RMAN-06025: no backup of log thread 1 seq 2416 lowscn 997090221 found to restore
RMAN-06025: no backup of log thread 1 seq 2415 lowscn 997083259 found to restore
RMAN-06025: no backup of log thread 1 seq 2414 lowscn 997080987 found to restore
RMAN-06025: no backup of log thread 1 seq 2413 lowscn 997072936 found to restore
RMAN-06025: no backup of log thread 1 seq 2412 lowscn 997065308 found to restore
RMAN-06025: no backup of log thread 1 seq 2411 lowscn 997057305 found to restore
RMAN-06025: no backup of log thread 1 seq 2410 lowscn 997049490 found to restore
RMAN-06025: no backup of log thread 1 seq 2409 lowscn 997041050 found to restore
RMAN-06025: no backup of log thread 1 seq 2408 lowscn 997032588 found to restore
RMAN-06025: no backup of log thread 1 seq 2407 lowscn 997029224 found to restore
RMAN-06025: no backup of log thread 1 seq 2406 lowscn 997025167 found to restore
RMAN-06025: no backup of log thread 1 seq 2405 lowscn 997017988 found to restore
RMAN-06025: no backup of log thread 1 seq 2404 lowscn 997010350 found to restore
RMAN-06025: no backup of log thread 1 seq 2403 lowscn 997002302 found to restore
RMAN-06025: no backup of log thread 1 seq 2402 lowscn 996994913 found to restore
RMAN-06025: no backup of log thread 1 seq 2401 lowscn 996991338 found to restore
------------------------
sqlplus下
1、SQL> recover database using backup controlfile until cancel;
根据提示输入 redo.log文件的目录，如果redo.log文件不止一个，可以一个一个的尝试，直到出现以下两句话：
Log applied.
Media recovery complete.
2、SQL> alter database open resetlogs;
Database altered.
---------
1、SQL> recover database using backup controlfile until cancel;
根据提示输入 redo.log文件的目录，如果redo.log文件不止一个，可以一个一个的尝试，直到出现以下两句话：
Log applied.
Media recovery complete.
2、SQL> alter database open resetlogs;
Database altered.
---------
感谢lks2004,也感谢大家的帮助，
问题按照lks2004的方法解决了，
想再问一下，我从最近的归档日志往回试，为什么最近的不行，一直到某一个就可以了呢？？
------------
问题按照lks2004的方法解决了，
想再问一下，我从最近的归档日志往回试，为什么最近的不行，一直到某一个就可以了呢？？
------------
不太清楚，
根据猜想，应该是控制文件也需要用最近的才行，因为控制文件决定了数据库某一时刻的数据库各种文件信息。需要控制文件和数据文件，日志文件同步，否则就恢复不了。
根据猜想，应该是控制文件也需要用最近的才行，因为控制文件决定了数据库某一时刻的数据库各种文件信息。需要控制文件和数据文件，日志文件同步，否则就恢复不了。