最近在学习rman,恢复的时候报错,大家看看,怎么解决SQL> alter database open ;
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database openSQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-19901: database needs more recovery to create new incarnation网上关于ora-19901的处理好少啊
alter database open
*
ERROR at line 1:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database openSQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-19901: database needs more recovery to create new incarnation网上关于ora-19901的处理好少啊
解决方案 »
- 如何取出存在oracle数据库中blob类型中的word文档呢?请高手指点
- 统计软件的日访问量,月访问量,年访问量
- 大数据量优化问题
- SQL*LOAD中ZONED类型的问题
- oracle10g如何创建表空间
- oracle中like的效率为什么看起来很低?
- 如何删除表空间所有表的数据???
- oracle 9i 安装完成后发现没有enterprise manager console.再线等待
- 我oracle进不处,假如要重新安装oracle,原来的数据库数据还在不在?
- 高分求教Enterprise Manager Console的问题(每天+10分),兄弟们帮忙啊,我的信誉很高哦^_^
- SQL优化的东东,大家帮个忙
- oracle不小心吧表truncate了,求帮助
recover database until cancel;2、rman下
restore database;
recover database;
+1
database needs more recovery to create new incarnation
Cause: Recovery was done to an incarnation after changing the destination incarnation using RMAN's RESET DATABASE command, but one or more of the recovered datafiles still belongs to the parent incarnation. This usually happens when recovery is ended before any logs from the desired incarnation have been applied.
Action: Continue recovery.
可以借助隐藏参数 _allow_resetlogs_corruption=true来进行打开,然后导出并重建数据库
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 restoreRMAN-06025: no backup of log thread 1 seq 2428 lowscn 997173052 found to restoreRMAN-06025: no backup of log thread 1 seq 2427 lowscn 997165018 found to restoreRMAN-06025: no backup of log thread 1 seq 2426 lowscn 997156390 found to restoreRMAN-06025: no backup of log thread 1 seq 2425 lowscn 997148327 found to restoreRMAN-06025: no backup of log thread 1 seq 2424 lowscn 997142921 found to restoreRMAN-06025: no backup of log thread 1 seq 2423 lowscn 997139905 found to restoreRMAN-06025: no backup of log thread 1 seq 2422 lowscn 997137418 found to restoreRMAN-06025: no backup of log thread 1 seq 2421 lowscn 997132151 found to restoreRMAN-06025: no backup of log thread 1 seq 2420 lowscn 997122744 found to restoreRMAN-06025: no backup of log thread 1 seq 2419 lowscn 997114426 found to restoreRMAN-06025: no backup of log thread 1 seq 2418 lowscn 997105934 found to restoreRMAN-06025: no backup of log thread 1 seq 2417 lowscn 997097451 found to restoreRMAN-06025: no backup of log thread 1 seq 2416 lowscn 997090221 found to restoreRMAN-06025: no backup of log thread 1 seq 2415 lowscn 997083259 found to restoreRMAN-06025: no backup of log thread 1 seq 2414 lowscn 997080987 found to restoreRMAN-06025: no backup of log thread 1 seq 2413 lowscn 997072936 found to restoreRMAN-06025: no backup of log thread 1 seq 2412 lowscn 997065308 found to restoreRMAN-06025: no backup of log thread 1 seq 2411 lowscn 997057305 found to restoreRMAN-06025: no backup of log thread 1 seq 2410 lowscn 997049490 found to restoreRMAN-06025: no backup of log thread 1 seq 2409 lowscn 997041050 found to restoreRMAN-06025: no backup of log thread 1 seq 2408 lowscn 997032588 found to restoreRMAN-06025: no backup of log thread 1 seq 2407 lowscn 997029224 found to restoreRMAN-06025: no backup of log thread 1 seq 2406 lowscn 997025167 found to restoreRMAN-06025: no backup of log thread 1 seq 2405 lowscn 997017988 found to restoreRMAN-06025: no backup of log thread 1 seq 2404 lowscn 997010350 found to restoreRMAN-06025: no backup of log thread 1 seq 2403 lowscn 997002302 found to restoreRMAN-06025: no backup of log thread 1 seq 2402 lowscn 996994913 found to restoreRMAN-06025: no backup of log thread 1 seq 2401 lowscn 996991338 found to restore
或者 recover database until time "to_date('','')";
alter database open resetlogs;
第二。没全备份的话,肯定没back啦
Media recovery complete.2、SQL> alter database open resetlogs;
Database altered.