万兆 2008-8-15 14:01
日志全，但recover database报丢失日志的问题
我在做一个[url=http://whatis.ctocio.com.cn/searchwhatis/99/5947599.shtml]data[/url] guard，源[url=http://database.ctocio.com.cn/]数据库[/url]是ORACLE 10.2.0.1的[url=http://whatis.ctocio.com.cn/searchwhatis/466/6028466.shtml]RAC[/url]，用rman把databae做了全[url=http://storage.ctocio.com.cn/tt-storage-bfrz/]备份[/url]，放在本地一个目录下用[url=http://whatis.ctocio.com.cn/searchwhatis/417/6093417.shtml]NFS[/url]共享出来，在备份库主机上MOUNT该目录，把源数据库的两台主机的归档日志全部FTP传到备份库主机的归档目录下，在oracle mount状态下做完[url=http://whatis.ctocio.com.cn/searchwhatis/144/6093644.shtml]restore[/url] database，执行recover [url=http://whatis.ctocio.com.cn/searchwhatis/132/5947632.shtml]database[/url]时报错，提示丢失日志，如下
RMAN> recover database;
Starting recover at 14-AUG-08
allocated [url=http://whatis.ctocio.com.cn/searchwhatis/141/5947141.shtml]channel[/url]: ORA_DISK_1
channel ORA_DISK_1: sid=331 devtype=DISK
starting media recovery
[url=http://whatis.ctocio.com.cn/searchwhatis/328/6025328.shtml]archive[/url] log [url=http://whatis.ctocio.com.cn/searchwhatis/195/6092695.shtml]thread[/url] 1 sequence 10346 is already on disk as [url=http://whatis.ctocio.com.cn/searchwhatis/398/5947898.shtml]file[/url] /oralog/dgsi/1_10346_643203591.dbf
archive log thread 1 sequence 10347 is already on disk as file /oralog/dgsi/1_10347_643203591.dbf
archive log thread 1 sequence 10348 is already on disk as file /oralog/dgsi/1_10348_643203591.dbf
archive log thread 1 sequence 10349 is already on disk as file /oralog/dgsi/1_10349_643203591.dbf
archive log thread 1 sequence 10350 is already on disk as file /oralog/dgsi/1_10350_643203591.dbf
archive log thread 1 sequence 10359 is already on disk as file /oralog/dgsi/1_10359_643203591.dbf
archive log thread 1 sequence 10360 is already on disk as file /oralog/dgsi/1_10360_643203591.dbf
archive log thread 1 sequence 10361 is already on disk as file /oralog/dgsi/1_10361_643203591.dbf
archive log thread 1 sequence 10362 is already on disk as file /oralog/dgsi/1_10362_643203591.dbf
archive log thread 1 sequence 10363 is already on disk as file /oralog/dgsi/1_10363_643203591.dbf
archive log thread 1 sequence 10364 is already on disk as file /oralog/dgsi/1_10364_643203591.dbf
archive log thread 1 sequence 10365 is already on disk as file /oralog/dgsi/1_10365_643203591.dbf
archive log thread 1 sequence 10366 is already on disk as file /oralog/dgsi/1_10366_643203591.dbf
archive log thread 1 sequence 10367 is already on disk as file /oralog/dgsi/1_10367_643203591.dbf
archive log thread 1 sequence 10368 is already on disk as file /oralog/dgsi/1_10368_643203591.dbf
archive log thread 1 sequence 10369 is already on disk as file /oralog/dgsi/1_10369_643203591.dbf
archive log thread 1 sequence 10370 is already on disk as file /oralog/dgsi/1_10370_643203591.dbf
archive log thread 1 sequence 10371 is already on disk as file /oralog/dgsi/1_10371_643203591.dbf
archive log thread 1 sequence 10372 is already on disk as file /oralog/dgsi/1_10372_643203591.dbf
archive log thread 1 sequence 10373 is already on disk as file /oralog/dgsi/1_10373_643203591.dbf
archive log thread 1 sequence 10374 is already on disk as file /oralog/dgsi/1_10374_643203591.dbf
archive log thread 1 sequence 10375 is already on disk as file /oralog/dgsi/1_10375_643203591.dbf
archive log thread 2 sequence 8427 is already on disk as file /oralog/dgsi/2_8427_643203591.dbf
archive log thread 2 sequence 8428 is already on disk as file /oralog/dgsi/2_8428_643203591.dbf
archive log thread 2 sequence 8429 is already on disk as file /oralog/dgsi/2_8429_643203591.dbf
archive log thread 2 sequence 8430 is already on disk as file /oralog/dgsi/2_8430_643203591.dbf
archive log thread 2 sequence 8431 is already on disk as file /oralog/dgsi/2_8431_643203591.dbf
archive log thread 2 sequence 8432 is already on disk as file /oralog/dgsi/2_8432_643203591.dbf
archive log thread 2 sequence 8433 is already on disk as file /oralog/dgsi/2_8433_643203591.dbf
archive log thread 2 sequence 8434 is already on disk as file /oralog/dgsi/2_8434_643203591.dbf
archive log thread 2 sequence 8435 is already on disk as file /oralog/dgsi/2_8435_643203591.dbf
archive log thread 2 sequence 8436 is already on disk as file /oralog/dgsi/2_8436_643203591.dbf
archive log thread 2 sequence 8437 is already on disk as file /oralog/dgsi/2_8437_643203591.dbf
archive log thread 2 sequence 8438 is already on disk as file /oralog/dgsi/2_8438_643203591.dbf
archive log thread 2 sequence 8439 is already on disk as file /oralog/dgsi/2_8439_643203591.dbf
archive log thread 2 sequence 8461 is already on disk as file /oralog/dgsi/2_8461_643203591.dbf
archive log thread 2 sequence 8462 is already on disk as file /oralog/dgsi/2_8462_643203591.dbf
archive log thread 2 sequence 8463 is already on disk as file /oralog/dgsi/2_8463_643203591.dbf
archive log thread 2 sequence 8464 is already on disk as file /oralog/dgsi/2_8464_643203591.dbf
archive log thread 2 sequence 8465 is already on disk as file /oralog/dgsi/2_8465_643203591.dbf
archive log thread 2 sequence 8466 is already on disk as file /oralog/dgsi/2_8466_643203591.dbf
archive log thread 2 sequence 8467 is already on disk as file /oralog/dgsi/2_8467_643203591.dbf
archive log thread 2 sequence 8468 is already on disk as file /oralog/dgsi/2_8468_643203591.dbf
archive log thread 2 sequence 8469 is already on disk as file /oralog/dgsi/2_8469_643203591.dbf
archive log thread 2 sequence 8470 is already on disk as file /oralog/dgsi/2_8470_643203591.dbf
archive log thread 2 sequence 8471 is already on disk as file /oralog/dgsi/2_8471_643203591.dbf
archive log thread 2 sequence 8472 is already on disk as file /oralog/dgsi/2_8472_643203591.dbf
archive log thread 2 sequence 8473 is already on disk as file /oralog/dgsi/2_8473_643203591.dbf
archive log thread 2 sequence 8474 is already on disk as file /oralog/dgsi/2_8474_643203591.dbf
archive log thread 2 sequence 8475 is already on disk as file /oralog/dgsi/2_8475_643203591.dbf
archive log thread 2 sequence 8476 is already on disk as file /oralog/dgsi/2_8476_643203591.dbf
archive log thread 2 sequence 8477 is already on disk as file /oralog/dgsi/2_8477_643203591.dbf
archive log thread 2 sequence 8478 is already on disk as file /oralog/dgsi/2_8478_643203591.dbf
archive log thread 2 sequence 8479 is already on disk as file /oralog/dgsi/2_8479_643203591.dbf
archive log thread 2 sequence 8480 is already on disk as file /oralog/dgsi/2_8480_643203591.dbf
archive log thread 2 sequence 8481 is already on disk as file /oralog/dgsi/2_8481_643203591.dbf
archive log thread 2 sequence 8482 is already on disk as file /oralog/dgsi/2_8482_643203591.dbf
archive log thread 2 sequence 8483 is already on disk as file /oralog/dgsi/2_8483_643203591.dbf
archive log thread 2 sequence 8484 is already on disk as file /oralog/dgsi/2_8484_643203591.dbf
archive log thread 2 sequence 8485 is already on disk as file /oralog/dgsi/2_8485_643203591.dbf
archive log thread 2 sequence 8486 is already on disk as file /oralog/dgsi/2_8486_643203591.dbf
archive log thread 2 sequence 8487 is already on disk as file /oralog/dgsi/2_8487_643203591.dbf
archive log thread 2 sequence 8488 is already on disk as file /oralog/dgsi/2_8488_643203591.dbf
archive log thread 2 sequence 8489 is already on disk as file /oralog/dgsi/2_8489_643203591.dbf
archive log thread 2 sequence 8490 is already on disk as file /oralog/dgsi/2_8490_643203591.dbf
archive log thread 2 sequence 8491 is already on disk as file /oralog/dgsi/2_8491_643203591.dbf
archive log thread 2 sequence 8492 is already on disk as file /oralog/dgsi/2_8492_643203591.dbf
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover [url=http://whatis.ctocio.com.cn/searchwhatis/311/5947311.shtml]command[/url] at 08/14/2008 17:47:32
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 2 seq 8456 lowscn 7007311256 found to restore
RMAN-06025: no backup of log thread 2 seq 8452 lowscn 7007214497 found to restore
RMAN-06025: no backup of log thread 2 seq 8451 lowscn 7007125886 found to restore
RMAN-06025: no backup of log thread 2 seq 8450 lowscn 7007057695 found to restore
RMAN-06025: no backup of log thread 2 seq 8449 lowscn 7005658911 found to restore
RMAN-06025: no backup of log thread 2 seq 8448 lowscn 7004799223 found to restore
RMAN-06025: no backup of log thread 2 seq 8447 lowscn 7004196256 found to restore
RMAN-06025: no backup of log thread 2 seq 8446 lowscn 7004152229 found to restore
RMAN-06025: no backup of log thread 2 seq 8445 lowscn 7004120100 found to restore
RMAN-06025: no backup of log thread 2 seq 8444 lowscn 7004101424 found to restore
RMAN-06025: no backup of log thread 2 seq 8443 lowscn 7003927628 found to restore
RMAN-06025: no backup of log thread 2 seq 8442 lowscn 7003825243 found to restore
RMAN-06025: no backup of log thread 2 seq 8441 lowscn 7003792497 found to restore
RMAN-06025: no backup of log thread 2 seq 8440 lowscn 7003696335 found to restore
RMAN-06025: no backup of log thread 1 seq 10358 lowscn 7007258879 found to restore
RMAN-06025: no backup of log thread 1 seq 10357 lowscn 7007125980 found to restore
RMAN-06025: no backup of log thread 1 seq 10356 lowscn 7005658893 found to restore
RMAN-06025: no backup of log thread 1 seq 10355 lowscn 7005657495 found to restore
RMAN-06025: no backup of log thread 1 seq 10354 lowscn 7004799332 found to restore
RMAN-06025: no backup of log thread 1 seq 10353 lowscn 7004121128 found to restore
RMAN-06025: no backup of log thread 1 seq 10352 lowscn 7003825262 found to restore
RMAN-06025: no backup of log thread 1 seq 10351 lowscn 7003620594 found to restore
报丢失的这些日志我在备份库主机的归档目录下察看了，一个不少，怎么会这样，明明在那，且说丢失找不到，更奇怪的是，说丢失找不到的居然是前头的一些日志，而后头的反而没有说丢失，很疑惑