Asm diskgroup add disk 失败一例
ASM add disk force失败的原因 Bug 5160038 : UNABLE TO ADD A DISK TO A DISKGROUP THAT WAS PREVIOUSLY FORCE DROPPED之前的一次drop disk force没有清理header ，导致disknum被重复使用，再次add disk时报duplicate disknum错误
看了下 目前这个bug没有补丁可用，基于10gR2的政策不会再有补丁。
2、add datafile size 10g 报错ORA-15041的原因可能是 DATA DISKGROUP没有正常完成rebalance ，这导致该DG下的disk的free space不平衡。
部分disk例如 # 4 # 5 # 6 #7 #8 #9仅有100多兆的FREE SPACE
group# disk# V COUNT(*)
---------- ---------- - ----------
1 0 F 74100
1 0 V 28492
1 1 F 74108
1 1 V 28484
1 2 F 74101
1 2 V 28491
1 3 F 74093
1 3 V 28499
2 0 F 109
2 0 V 102483
2 1 F 96
2 1 V 102496
2 2 F 124
2 2 V 102468
2 3 F 109
2 3 V 102483
2 4 F 111
2 4 V 102481
2 5 F 115
2 5 V 102477
2 6 F 112
2 6 V 102480
2 7 F 109
2 7 V 102483
2 8 F 112
2 8 V 102480
2 9 F 115
2 9 V 102477
2 10 F 115
2 10 V 102477
2 11 F 96840
2 11 V 5752
2 12 F 96839
2 12 V 5753
2 13 F 99818
2 13 V 2774
2 14 F 99817
2 14 V 2775
2 15 F 99815
2 15 V 2777
建议找一个空闲时间 做一次手动rebalance ；rebalance后应当可以加数据文件
3、对于add disk失败 ，建议在首先备份asm disk header的情况下，dd 清空disk header 再尝试加入到diskgroup ，或者不处置。 Bug 5160038 Unable to add a disk to a diskgroup that was previously force dropped (ORA-15020)
This note gives a brief overview of bug 5160038.
The content was last updated on: 12-APR-2013
Click here for details of each of the sections below.
Affects:
Product (Component) Oracle Server (Rdbms)
Range of versions believed to be affected Versions BELOW 11.1
Versions confirmed as being affected
10.2.0.4
10.1.0.2
Platforms affected Generic (all / most platforms affected)
Fixed:
This issue is fixed in
11.1.0.6 (Base Release)
Symptoms:
Related To:
Error May Occur
ORA-15020
Automatic Storage Management (ASM)
Description
ORA-15020 is signaled when a disk is being added with force.
Rediscovery Notes:
ORA-15020 is signaled when a disk is being added with force and its header
states that it already belongs to the diskgroup with a disk number that is
currently assigned to some other disk.
No Workaround.
页:
[1]