Oracle 10G RAC - 某个节点上缺失某些归档日志后删除报错问题

最新推荐文章于 2022-08-24 22:47:48 发布
最新推荐文章于 2022-08-24 22:47:48 发布
阅读量811 收藏
点赞数
分类专栏： Oracle 10G RAC ORA-xxx 文章标签： oracle archive validation disk thread
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/deanza/article/details/7746294
版权

备份日志及删除步骤如下(在节点vmrac1上操作):
a.RMAN> backup database plus archivelog;(完成成功的全备)
Starting backup at 04-JAN-12
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=5 recid=23 stamp=771704739
input archive log thread=1 sequence=6 recid=20 stamp=771704735
input archive log thread=1 sequence=8 recid=18 stamp=771704733
input archive log thread=1 sequence=10 recid=22 stamp=771704736
input archive log thread=2 sequence=2 recid=24 stamp=771704739
input archive log thread=2 sequence=3 recid=19 stamp=771704734
input archive log thread=2 sequence=4 recid=16 stamp=771704732
input archive log thread=2 sequence=5 recid=17 stamp=771704732
input archive log thread=2 sequence=6 recid=21 stamp=771704736
channel ORA_DISK_1: starting piece 1 at 04-JAN-12
channel ORA_DISK_1: finished piece 1 at 04-JAN-12
piece handle=+RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t221927_0.267.771718769 tag=TAG20120104T221927 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:08
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=1 recid=32 stamp=771718491
input archive log thread=1 sequence=2 recid=34 stamp=771718682
input archive log thread=1 sequence=3 recid=39 stamp=771718763
input archive log thread=2 sequence=1 recid=29 stamp=771705382
input archive log thread=2 sequence=2 recid=30 stamp=771718485
input archive log thread=2 sequence=3 recid=36 stamp=771718684
input archive log thread=2 sequence=4 recid=38 stamp=771718762
channel ORA_DISK_1: starting piece 1 at 04-JAN-12
channel ORA_DISK_1: finished piece 1 at 04-JAN-12
piece handle=+RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t221927_0.266.771718777 tag=TAG20120104T221927 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 04-JAN-12

Starting backup at 04-JAN-12
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DATA/jtods/system01.dbf
input datafile fno=00003 name=+DATA/jtods/sysaux01.dbf
input datafile fno=00002 name=+DATA/jtods/undotbs01.dbf
input datafile fno=00005 name=+DATA/jtods/undotbs02.dbf
input datafile fno=00004 name=+DATA/jtods/users01.dbf
channel ORA_DISK_1: starting piece 1 at 04-JAN-12
channel ORA_DISK_1: finished piece 1 at 04-JAN-12
piece handle=+RECOVERY/jtods/backupset/2012_01_04/nnndf0_tag20120104t221941_0.265.771718783 tag=TAG20120104T221941 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:56
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 04-JAN-12
channel ORA_DISK_1: finished piece 1 at 04-JAN-12
piece handle=+RECOVERY/jtods/backupset/2012_01_04/ncsnf0_tag20120104t221941_0.264.771718841 tag=TAG20120104T221941 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:06
Finished backup at 04-JAN-12

Starting backup at 04-JAN-12
current log archived
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=4 recid=42 stamp=771718844
input archive log thread=2 sequence=5 recid=44 stamp=771718845
channel ORA_DISK_1: starting piece 1 at 04-JAN-12
channel ORA_DISK_1: finished piece 1 at 04-JAN-12
piece handle=+RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t222046_0.263.771718849 tag=TAG20120104T222046 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 04-JAN-12

b.RMAN> report obsolete;(根据备份策略,查询出可以删除的归档及备份集)
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Archive Log          1      01-JAN-12          /arch/JTODS2_arch/1_2_771381498.dbf
Archive Log          2      01-JAN-12          /arch/JTODS2_arch/1_2_771381498.dbf
Archive Log          3      01-JAN-12          /arch/JTODS1_arch/1_3_771381498.dbf
Archive Log          4      01-JAN-12          /arch/JTODS1_arch/1_3_771381498.dbf
Archive Log          5      01-JAN-12          /arch/JTODS1_arch/1_4_771381498.dbf
Archive Log          6      01-JAN-12          /arch/JTODS1_arch/1_4_771381498.dbf
Archive Log          7      01-JAN-12          /arch/JTODS2_arch/2_1_771381498.dbf
Archive Log          8      01-JAN-12          /arch/JTODS2_arch/2_1_771381498.dbf
Backup Set           1      01-JAN-12         
  Backup Piece       1      01-JAN-12          +RECOVERY/jtods/backupset/2012_01_01/annnf0_tag20120101t134439_0.259.771428681
Backup Set           2      01-JAN-12         
  Backup Piece       2      01-JAN-12          +RECOVERY/jtods/backupset/2012_01_01/nnndf0_tag20120101t134448_0.258.771428689
Backup Set           4      04-JAN-12         
  Backup Piece       4      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_01/ncsnf0_tag20120101t134448_0.256.771428763
Backup Set           5      04-JAN-12         
  Backup Piece       5      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_01/annnf0_tag20120101t134613_0.257.771428775
Archive Log          17     04-JAN-12          /arch/JTODS1_arch/2_5_771381498.dbf
Backup Set           3      04-JAN-12         
  Backup Piece       3      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_02/annnf0_tag20120102t151600_0.260.771520587
Archive Log          16     04-JAN-12          /arch/JTODS1_arch/2_4_771381498.dbf
Archive Log          18     04-JAN-12          /arch/JTODS1_arch/1_8_771381498.dbf
Archive Log          19     04-JAN-12          /arch/JTODS1_arch/2_3_771381498.dbf
Archive Log          20     04-JAN-12          /arch/JTODS1_arch/1_6_771381498.dbf
Archive Log          22     04-JAN-12          /arch/JTODS1_arch/1_10_771381498.dbf
Archive Log          21     04-JAN-12          /arch/JTODS1_arch/2_6_771381498.dbf
Archive Log          24     04-JAN-12          /arch/JTODS1_arch/2_2_771381498.dbf
Archive Log          23     04-JAN-12          /arch/JTODS1_arch/1_5_771381498.dbf
Archive Log          29     04-JAN-12          /arch/JTODS1_arch/2_1_771704921.dbf
Archive Log          30     04-JAN-12          /arch/JTODS2_arch/2_2_771704921.dbf
Archive Log          31     04-JAN-12          /arch/JTODS1_arch/1_1_771704921.dbf
Archive Log          32     04-JAN-12          /arch/JTODS1_arch/1_1_771704921.dbf
Archive Log          33     04-JAN-12          /arch/JTODS1_arch/1_2_771704921.dbf
Archive Log          34     04-JAN-12          /arch/JTODS1_arch/1_2_771704921.dbf
Archive Log          35     04-JAN-12          /arch/JTODS2_arch/2_3_771704921.dbf
Archive Log          36     04-JAN-12          /arch/JTODS2_arch/2_3_771704921.dbf
Archive Log          37     04-JAN-12          /arch/JTODS2_arch/2_4_771704921.dbf
Archive Log          38     04-JAN-12          /arch/JTODS2_arch/2_4_771704921.dbf
Archive Log          39     04-JAN-12          /arch/JTODS1_arch/1_3_771704921.dbf
Archive Log          40     04-JAN-12          /arch/JTODS1_arch/1_3_771704921.dbf
Backup Set           6      04-JAN-12         
  Backup Piece       6      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t221927_0.267.771718769
Backup Set           7      04-JAN-12         
  Backup Piece       7      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t221927_0.266.771718777

RMAN> delete obsolete; (删除上述"无用"的文件)
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Archive Log          1      01-JAN-12          /arch/JTODS2_arch/1_2_771381498.dbf
Archive Log          2      01-JAN-12          /arch/JTODS2_arch/1_2_771381498.dbf
Archive Log          3      01-JAN-12          /arch/JTODS1_arch/1_3_771381498.dbf
Archive Log          4      01-JAN-12          /arch/JTODS1_arch/1_3_771381498.dbf
Archive Log          5      01-JAN-12          /arch/JTODS1_arch/1_4_771381498.dbf
Archive Log          6      01-JAN-12          /arch/JTODS1_arch/1_4_771381498.dbf
Archive Log          7      01-JAN-12          /arch/JTODS2_arch/2_1_771381498.dbf
Archive Log          8      01-JAN-12          /arch/JTODS2_arch/2_1_771381498.dbf
Backup Set           1      01-JAN-12         
  Backup Piece       1      01-JAN-12          +RECOVERY/jtods/backupset/2012_01_01/annnf0_tag20120101t134439_0.259.771428681
Backup Set           2      01-JAN-12         
  Backup Piece       2      01-JAN-12          +RECOVERY/jtods/backupset/2012_01_01/nnndf0_tag20120101t134448_0.258.771428689
Backup Set           4      04-JAN-12         
  Backup Piece       4      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_01/ncsnf0_tag20120101t134448_0.256.771428763
Backup Set           5      04-JAN-12         
  Backup Piece       5      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_01/annnf0_tag20120101t134613_0.257.771428775
Archive Log          17     04-JAN-12          /arch/JTODS1_arch/2_5_771381498.dbf
Backup Set           3      04-JAN-12         
  Backup Piece       3      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_02/annnf0_tag20120102t151600_0.260.771520587
Archive Log          16     04-JAN-12          /arch/JTODS1_arch/2_4_771381498.dbf
Archive Log          18     04-JAN-12          /arch/JTODS1_arch/1_8_771381498.dbf
Archive Log          19     04-JAN-12          /arch/JTODS1_arch/2_3_771381498.dbf
Archive Log          20     04-JAN-12          /arch/JTODS1_arch/1_6_771381498.dbf
Archive Log          22     04-JAN-12          /arch/JTODS1_arch/1_10_771381498.dbf
Archive Log          21     04-JAN-12          /arch/JTODS1_arch/2_6_771381498.dbf
Archive Log          24     04-JAN-12          /arch/JTODS1_arch/2_2_771381498.dbf
Archive Log          23     04-JAN-12          /arch/JTODS1_arch/1_5_771381498.dbf
Archive Log          29     04-JAN-12          /arch/JTODS1_arch/2_1_771704921.dbf
Archive Log          30     04-JAN-12          /arch/JTODS2_arch/2_2_771704921.dbf
Archive Log          31     04-JAN-12          /arch/JTODS1_arch/1_1_771704921.dbf
Archive Log          32     04-JAN-12          /arch/JTODS1_arch/1_1_771704921.dbf
Archive Log          33     04-JAN-12          /arch/JTODS1_arch/1_2_771704921.dbf
Archive Log          34     04-JAN-12          /arch/JTODS1_arch/1_2_771704921.dbf
Archive Log          35     04-JAN-12          /arch/JTODS2_arch/2_3_771704921.dbf
Archive Log          36     04-JAN-12          /arch/JTODS2_arch/2_3_771704921.dbf
Archive Log          37     04-JAN-12          /arch/JTODS2_arch/2_4_771704921.dbf
Archive Log          38     04-JAN-12          /arch/JTODS2_arch/2_4_771704921.dbf
Archive Log          39     04-JAN-12          /arch/JTODS1_arch/1_3_771704921.dbf
Archive Log          40     04-JAN-12          /arch/JTODS1_arch/1_3_771704921.dbf
Backup Set           6      04-JAN-12         
  Backup Piece       6      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t221927_0.267.771718769
Backup Set           7      04-JAN-12         
  Backup Piece       7      04-JAN-12          +RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t221927_0.266.771718777

Do you really want to delete the above objects (enter YES or NO)? YES
deleted archive log
archive log filename=/arch/JTODS2_arch/1_2_771381498.dbf recid=1 stamp=771427950
deleted archive log
archive log filename=/arch/JTODS2_arch/1_2_771381498.dbf recid=2 stamp=771428138
deleted archive log
archive log filename=/arch/JTODS1_arch/1_3_771381498.dbf recid=3 stamp=771428251
deleted archive log
archive log filename=/arch/JTODS1_arch/1_3_771381498.dbf recid=4 stamp=771428252
deleted archive log
archive log filename=/arch/JTODS1_arch/1_4_771381498.dbf recid=5 stamp=771428668
deleted archive log
archive log filename=/arch/JTODS1_arch/1_4_771381498.dbf recid=6 stamp=771428670
deleted archive log
archive log filename=/arch/JTODS2_arch/2_1_771381498.dbf recid=7 stamp=771428673
deleted archive log
archive log filename=/arch/JTODS2_arch/2_1_771381498.dbf recid=8 stamp=771428673
deleted backup piece
backup piece handle=+RECOVERY/jtods/backupset/2012_01_01/annnf0_tag20120101t134439_0.259.771428681 recid=1 stamp=771428680
deleted backup piece
backup piece handle=+RECOVERY/jtods/backupset/2012_01_01/nnndf0_tag20120101t134448_0.258.771428689 recid=2 stamp=771428689
deleted backup piece
backup piece handle=+RECOVERY/jtods/backupset/2012_01_01/ncsnf0_tag20120101t134448_0.256.771428763 recid=4 stamp=771704091
deleted backup piece
backup piece handle=+RECOVERY/jtods/backupset/2012_01_01/annnf0_tag20120101t134613_0.257.771428775 recid=5 stamp=771704092
deleted archive log
archive log filename=/arch/JTODS1_arch/2_5_771381498.dbf recid=17 stamp=771704732
deleted backup piece
backup piece handle=+RECOVERY/jtods/backupset/2012_01_02/annnf0_tag20120102t151600_0.260.771520587 recid=3 stamp=771704091
deleted archive log
archive log filename=/arch/JTODS1_arch/2_4_771381498.dbf recid=16 stamp=771704732
deleted archive log
archive log filename=/arch/JTODS1_arch/1_8_771381498.dbf recid=18 stamp=771704733
deleted archive log
archive log filename=/arch/JTODS1_arch/2_3_771381498.dbf recid=19 stamp=771704734
deleted archive log
archive log filename=/arch/JTODS1_arch/1_6_771381498.dbf recid=20 stamp=771704735
deleted archive log
archive log filename=/arch/JTODS1_arch/1_10_771381498.dbf recid=22 stamp=771704736
deleted archive log
archive log filename=/arch/JTODS1_arch/2_6_771381498.dbf recid=21 stamp=771704736
deleted archive log
archive log filename=/arch/JTODS1_arch/2_2_771381498.dbf recid=24 stamp=771704739
deleted archive log
archive log filename=/arch/JTODS1_arch/1_5_771381498.dbf recid=23 stamp=771704739
deleted archive log
archive log filename=/arch/JTODS1_arch/2_1_771704921.dbf recid=29 stamp=771705382
deleted archive log
archive log filename=/arch/JTODS2_arch/2_2_771704921.dbf recid=30 stamp=771718485
deleted archive log
archive log filename=/arch/JTODS1_arch/1_1_771704921.dbf recid=31 stamp=771718489
deleted archive log
archive log filename=/arch/JTODS1_arch/1_2_771704921.dbf recid=33 stamp=771718681
deleted archive log
archive log filename=/arch/JTODS2_arch/2_3_771704921.dbf recid=35 stamp=771718683
deleted archive log
archive log filename=/arch/JTODS2_arch/2_4_771704921.dbf recid=37 stamp=771718761
deleted archive log
archive log filename=/arch/JTODS1_arch/1_3_771704921.dbf recid=39 stamp=771718763
deleted backup piece
backup piece handle=+RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t221927_0.267.771718769 recid=6 stamp=771718769
deleted backup piece
backup piece handle=+RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t221927_0.266.771718777 recid=7 stamp=771718777
Deleted 31 objects

RMAN-06207: WARNING: 5 objects could not be deleted for DISK channel(s) due
RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Archivelog      /arch/JTODS1_arch/1_1_771704921.dbf
RMAN-06214: Archivelog      /arch/JTODS1_arch/1_2_771704921.dbf
RMAN-06214: Archivelog      /arch/JTODS2_arch/2_3_771704921.dbf
RMAN-06214: Archivelog      /arch/JTODS2_arch/2_4_771704921.dbf
RMAN-06214: Archivelog      /arch/JTODS1_arch/1_3_771704921.dbf


c.RMAN> crosscheck backup;
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=117 instance=JTODS1 devtype=DISK
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=+RECOVERY/jtods/backupset/2012_01_04/nnndf0_tag20120104t221941_0.265.771718783 recid=8 stamp=771718782
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=+RECOVERY/jtods/backupset/2012_01_04/ncsnf0_tag20120104t221941_0.264.771718841 recid=9 stamp=771718840
crosschecked backup piece: found to be 'AVAILABLE'
backup piece handle=+RECOVERY/jtods/backupset/2012_01_04/annnf0_tag20120104t222046_0.263.771718849 recid=10 stamp=771718848
Crosschecked 3 objects

RMAN> crosscheck archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=117 instance=JTODS1 devtype=DISK
validationfailedfor archived log
archive log filename=/arch/JTODS1_arch/1_1_771704921.dbf recid=32 stamp=771718491
validationfailedfor archived log
archive log filename=/arch/JTODS1_arch/1_2_771704921.dbf recid=34 stamp=771718682
validationfailedfor archived log
archive log filename=/arch/JTODS1_arch/1_3_771704921.dbf recid=40 stamp=771718763
validation succeeded for archived log
archive log filename=/arch/JTODS1_arch/1_4_771704921.dbf recid=42 stamp=771718844
validation succeeded for archived log
archive log filename=/arch/JTODS1_arch/1_4_771704921.dbf recid=41 stamp=771718843
validationfailedfor archived log
archive log filename=/arch/JTODS2_arch/2_3_771704921.dbf recid=36 stamp=771718684
validationfailedfor archived log
archive log filename=/arch/JTODS2_arch/2_4_771704921.dbf recid=38 stamp=771718762
validation succeeded for archived log
archive log filename=/arch/JTODS2_arch/2_5_771704921.dbf recid=44 stamp=771718845
validation succeeded for archived log
archive log filename=/arch/JTODS2_arch/2_5_771704921.dbf recid=43 stamp=771718844
Crosschecked 9 objects

d.RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Archive Log          32     04-JAN-12          /arch/JTODS1_arch/1_1_771704921.dbf
Archive Log          34     04-JAN-12          /arch/JTODS1_arch/1_2_771704921.dbf
Archive Log          36     04-JAN-12          /arch/JTODS2_arch/2_3_771704921.dbf
Archive Log          38     04-JAN-12          /arch/JTODS2_arch/2_4_771704921.dbf
Archive Log          40     04-JAN-12          /arch/JTODS1_arch/1_3_771704921.dbf

e.RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Archive Log          32     04-JAN-12          /arch/JTODS1_arch/1_1_771704921.dbf
Archive Log          34     04-JAN-12          /arch/JTODS1_arch/1_2_771704921.dbf
Archive Log          36     04-JAN-12          /arch/JTODS2_arch/2_3_771704921.dbf
Archive Log          38     04-JAN-12          /arch/JTODS2_arch/2_4_771704921.dbf
Archive Log          40     04-JAN-12          /arch/JTODS1_arch/1_3_771704921.dbf

Do you really want to delete the above objects (enter YES or NO)? YES

RMAN-06207: WARNING: 5 objects could not be deleted for DISK channel(s) due
RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status
RMAN-06210: List of Mismatched objects
RMAN-06211: ==========================
RMAN-06212:   Object Type   Filename/Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: Archivelog      /arch/JTODS1_arch/1_1_771704921.dbf
RMAN-06214: Archivelog      /arch/JTODS1_arch/1_2_771704921.dbf
RMAN-06214: Archivelog      /arch/JTODS2_arch/2_3_771704921.dbf
RMAN-06214: Archivelog      /arch/JTODS2_arch/2_4_771704921.dbf
RMAN-06214: Archivelog      /arch/JTODS1_arch/1_3_771704921.dbf

f.将缺失的archivelog从另外一个节点vmrac2拷贝至备份节点vmrac1使得归档日志完整.

[oracle@vmrac2 JTODS2_arch]$ scp 2_3_771704921.dbf 2_4_771704921.dbf oracle@vmrac1:/arch/JTODS2_arch/
2_3_771704921.dbf                                                       100%   55KB  55.0KB/s   00:00    
2_4_771704921.dbf                                                       100%   12KB  11.5KB/s   00:00  
[oracle@vmrac2 JTODS1_arch]$ scp 1_1_771704921.dbf 1_2_771704921.dbf 1_3_771704921.dbf oracle@vmrac1:/arch/JTODS1_arch/
1_1_771704921.dbf                                                       100%   11MB  11.3MB/s   00:01    
1_2_771704921.dbf                                                       100%   88KB  87.5KB/s   00:00    
1_3_771704921.dbf                                                       100%   19KB  18.5KB/s   00:00 

g.RMAN> crosscheck archivelog all;(此时全部为succeeded)

released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=117 instance=JTODS1 devtype=DISK
validation succeeded for archived log
archive log filename=/arch/JTODS1_arch/1_1_771704921.dbf recid=32 stamp=771718491
validation succeeded for archived log
archive log filename=/arch/JTODS1_arch/1_2_771704921.dbf recid=34 stamp=771718682
validation succeeded for archived log
archive log filename=/arch/JTODS1_arch/1_3_771704921.dbf recid=40 stamp=771718763
validation succeeded for archived log
archive log filename=/arch/JTODS1_arch/1_4_771704921.dbf recid=42 stamp=771718844
validation succeeded for archived log
archive log filename=/arch/JTODS1_arch/1_4_771704921.dbf recid=41 stamp=771718843
validation succeeded for archived log
archive log filename=/arch/JTODS2_arch/2_3_771704921.dbf recid=36 stamp=771718684
validation succeeded for archived log
archive log filename=/arch/JTODS2_arch/2_4_771704921.dbf recid=38 stamp=771718762
validation succeeded for archived log
archive log filename=/arch/JTODS2_arch/2_5_771704921.dbf recid=44 stamp=771718845
validation succeeded for archived log
archive log filename=/arch/JTODS2_arch/2_5_771704921.dbf recid=43 stamp=771718844
Crosschecked 9 objects

h.RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Archive Log          32     04-JAN-12          /arch/JTODS1_arch/1_1_771704921.dbf
Archive Log          34     04-JAN-12          /arch/JTODS1_arch/1_2_771704921.dbf
Archive Log          36     04-JAN-12          /arch/JTODS2_arch/2_3_771704921.dbf
Archive Log          38     04-JAN-12          /arch/JTODS2_arch/2_4_771704921.dbf
Archive Log          40     04-JAN-12          /arch/JTODS1_arch/1_3_771704921.dbf

Do you really want to delete the above objects (enter YES or NO)? YES
deleted archive log
archive log filename=/arch/JTODS1_arch/1_1_771704921.dbf recid=32 stamp=771718491
deleted archive log
archive log filename=/arch/JTODS1_arch/1_2_771704921.dbf recid=34 stamp=771718682
deleted archive log
archive log filename=/arch/JTODS2_arch/2_3_771704921.dbf recid=36 stamp=771718684
deleted archive log
archive log filename=/arch/JTODS2_arch/2_4_771704921.dbf recid=38 stamp=771718762
deleted archive log
archive log filename=/arch/JTODS1_arch/1_3_771704921.dbf recid=40 stamp=771718763
Deleted 5 objects

RMAN> report obsolete;(已经正常)
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN>

总结一下

1,为什么在节点1,vmrac1的/arch/JTODS1_arch会缺失节点1本身的归档日志?

2,因为是首次进行全备份,所以日志的缺失并没有备份时的报错.

3,此时也可以通过RMAN>list expired copy;RMAN>crosscheck copy;进行检查,再进行RMAN>delete expired copy删除,但删除前如果需要使用,则出现日志不完整.


deanza
关注
专栏目录
Oracle11g RAC 在Centos7上安装步骤
weixin_44167712的博客
05-18 6042
Oracle11204+ASM+RAC+Centos71 准备工作1.1 软件需求1.2 网络需求1.3 划分节点IP（各节点）1.4 防火墙和Selinux（各节点）1.5 创建组和用户（各节点）1.6 创建安装目录（各节点）1.7 配置安装用户的环境变量（各节点）1.8 资源限制（各节点）1.9 配置Linux内核参数1.10 修改pam登陆验证模块（各节点）1.11 修改/etc/profile文件（各节点）1.12 安装介质1.13 停用NTP服务(各节点)1.14 配置互信1.14.1 配置及验证
Oracle RAC环境实时数据迁移
夜澜偶作庄周梦 酒后聊为楚客狂
01-06 7707
Oracle RAC环境实时数据迁移———————————————————————————————————————系统要求及安装前的说明Oracle GoldenGate可以在Oracle不同版本间移动数据，也可以在Oracle和其它类型数据库之间移动数据。Oracle GoldenGate支持数据的过滤、映射和转换。Oracle还能在相似的Oracle数据库之间复制DDL操作。注意下面一句：当D
Oracle rac误删归档,Oracle RAC集群环境下删除归档日志
weixin_34746924的博客
04-03 184
归档日志存放形式主要存放方式有以下方式：一、ASM方式Oracle 10G、oracle11g、oracle 12C版本如果操作系统是AIX、HPUX、Linux下，一般都会采取ASM建库方式，特别是oracle 11g和oracle12C，因为oracle已经不支持裸设备建库(手工建库还是可以裸设备)，如果没有购买HACMP、HP MC软件，那一般开启归档，归档日志只能放在ASM上面，当然也可以...
rac 缺失本地节点node1的信息
cikuaizhen9509的博客
08-05 211
rac 缺失本地节点node1的信息问题原因:public网卡和private网卡设置反了会出现这个问题要修改网卡的优先级，public的高于private的，具体步骤就是：右键网络邻居－》选择属性－》进入后选择windows菜...
oracle rac的归档日志,oracle RAC－－归档日志的开启方法
weixin_28847199的博客
04-04 176
oracle RAC－－归档日志的开启方法＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝10g R1 要修改cluster_database参数 ，10G R2和以后的版本就不需要了1. 例子(10g R1或之前)：srvctl stop database -d RAC节点1sql>startup mountSQL> alter system set log_...
Oracle rac误删归档,Oracle Rac 开启归档日志并修改归档路径
weixin_31238185的博客
04-03 164
一、开启归档日志：1、查看归档状态：SQL> archive log list;Database log mode No Archive ModeAutomatic archival DisabledArchive destination USE_DB_RECOVERY_FILE_DESTOldest online log sequ...
在ARCHIVELOG模式下丢失了系统关键数据文件如何进行恢复
m0_67751585的博客
08-24 195
如果某个数据文件丢失或损坏，且该文件属于 SYSTEM 或 UNDO 表空间，执行一下步骤： a．实例可能会也可能不会自动关闭。如果未自动关闭，使用 SHUTDOWN ABORT 关闭实例。 b. 装载数据库。 c. 还原并恢复缺失的数据文件。 d. 打开数据库。
oracle 报错总结
qq_40126657的博客
09-06 2236
ORA-00001: 违反唯一约束条件 (.) 错误说明：当在唯一索引所对应的列上键入重复值时，会触发此异常。 ORA-00017: 请求会话以设置跟踪事件 ORA-00018: 超出最大会话数 ORA-00019: 超出最大会话许可数 ORA-00020: 超出最大进程数 () ORA-00021: 会话附属于其它某些进程；无法转换会话 ORA-00022: 无效的会话 ID；访问
Oracle DBA 摘录 Chapter1-4
Wang Wenly的博客
08-31 525
最近在看杨建荣编著的Oracle DBA工作笔记，颇有所得吧。 Chapter1.数据库安装配置 1.    查看内存情况(root)：grep MemTotal /proc/menifo 2.    查看swap情况(root)：grep SwapTotal /proc/menifo 3.    查看磁盘空间(root)：df -k或df -h 4.    /tmp目录空间大于4
ORACLE错误代码对照表
曾经的你
10-21 2809
ORA-00001: 违反唯一约束条件 (.) ORA-00017: 请求会话以设置跟踪事件 ORA-00018: 超出最大会话数 ORA-00019: 超出最大会话许可数 ORA-00020: 超出最大进程数 () ORA-00021: 会话附属于其它某些进程；无法转换会话 ORA-00022: 无效的会话 ID；访问被拒绝 ORA-00023: 会话引用进程私用内存；无法分离会话 ORA-00024: 单一进程模式下不允许从多个进程注册 ORA-00025: 无法分配 ORA-00026: 丢失或无效
RMAN 错误集锦
搞怪的索引
05-09 1083
SQL> select * from v$version; Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Prod PL/SQL Release 10.2.0.3.0 - Production CORE 10.2.0.3.0Production TNS for 32-bit Windows: Version 10
RMAN-06214
Data & Analysis
02-01 1333
备份命令发现报错： report obsolete; delete noprompt obsolete; 报错如下： RMAN-06207: WARNING: 12 objects could not be deleted for DISK channel(s) due 2567 RMAN-06208: to mismatched status. Use CRO...
oracle清除过期备份,删除过期备份报错RMAN-06207 RMAN-06208解决方案
weixin_31951365的博客
04-03 519
RMAN备份日志中出现了警告日志文件目录如下：[root@erpdbs rmanback]# lltotal 88-rw-r--r-- 1 oraprod dba 81011 Sep 7 22:52 rmanback.log -rwxr--r-- 1 oraprod dba 2581 Jun 24 2011 rmanback.sh[root@erpdbs rmanback]# pwd/data/s...
validateion_failed_for_archived_log处理
TheoGo的专栏
08-14 1670
近几天一个小机节点的archive空间老是100%，手工删除了一下，后来发现rman 备份失败了 查了一下资料发现删除后没有进行crosscheck 记录过程如下： 1、rman target / 2、crosscheck archivelog all; 发现 validation failed for archived log 错误 3、delete expired archivelo
RMAN--如何從controlfile中清除已經在OS上刪除掉的archivelog
cuifan5176的博客
07-18 115
如從controlfile中清除已經在OS上刪除掉的archivelog如果我們手工從os上刪除了archive log 就需要用rman的crosscheck來做一次檢查，然后用delete expired命令來從contro...
使用 RMAN 管理 archivelog
DBA never sleep-DBA，永不眠
12-19 8757
因为archivelog的相关信息是记录在controlfile中的，当物理删除后不会改变controlfile的设置。并且在查询相关的动态视图(例如v$archived_log)时，该部分日志仍然标注为存在，也就是说 Oracle并不认为这些日志被删除了。 这种错误信息会导致在rman在备份archivelog终止，出现不能完成备份，并且阻塞后续的备份操作。 一、直接使用RMAN删除arc
RMAN正确地删除Archivelog以及设置有备库的归档删除策略
Programmer.Wenlong 小龙在线
08-17 1108
原文链接：http://blog.sina.com.cn/s/blog_64e166580100xks5.html 如何正确地删除Archivelog： Archivelog并不能直接得从OS层直接物理删除，因为archivelog的相关信息是记录在controlfile中的，当物理删除后不会改变controlfile的设置。并且在查询相关的动态视图(例如v$archived_log)时，...
RMAN-06214: Datafile Copy
about database article
05-28 5869
在使用rman备份的时候最后出现一个这样的错误： RMAN-06207: WARNING: 1 objects could not be deleted for DISK channel(s) due RMAN-06208:          to mismatched status.  Use CROSSCHECK command to fix status RMAN-06210: Lis
[Rman]RMAN-06207 WARNING:2 objects could not be deleted for DISK channel(s) due
不忘初心、方得始终
12-03 1465
MAN> delete obsolete; RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 1 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=28 device type=DISK
Oracle10g RAC切换到归档模式详细步骤
"Oracle10g RAC归档模式的修改和管理，涉及数据库的状态检查、参数修改、归档日志处理" Oracle10g Real Application Clusters (RAC) 是一个高可用性的数据库解决方案，它允许多个实例同时访问同一个物理数据库。在...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值