rac 其中一个节点 mount diskgroup 提示如下错误

taoy_2008

SQL> alter diskgroup REDOLOG mount;
alter diskgroup REDOLOG mount
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15017: diskgroup "REDOLOG" cannot be mounted
ORA-15063: ASM discovered an insufficient number of disks for diskgroup
"REDOLOG"

Maclean Liu(刘相兵

ASM Disk 可能存在问题

运行以下脚本，并上传输出:

1. spool asm_diag1.txt
   
2. set pagesize 1000
   
3. set lines 500
   
4. col "Group Name"   form a25
   
5. col "Disk Name"    form a30
   
6. col "State"  form a15
   
7. col "Type"   form a7
   
8. col "Free GB"   form 9,999
   
9. alter session set nls_date_format='DD-MON-YYYY HH24:MI:SS';
   
10. select sysdate "Date and Time" from dual;
    
11. 
    
12. select * from v$asm_diskgroup order by 1;
    
13. select * from v$asm_disk order by 1, 2, 3;
    
14. select * from gv$asm_operation order by 1;
    
15. select * from v$version where banner like '%Database%' order by 1;
    
16. select * from gv$asm_client order by 1;
    
17. 
    
18. prompt
    
19. 
    
20. prompt ASM Disk Groups
    
21. prompt ===============
    
22. 
    
23. select group_number  "Group"
    
24. ,      name          "Group Name"
    
25. ,      state         "State"
    
26. ,      type          "Type"
    
27. ,      total_mb/1024 "Total GB"
    
28. ,      free_mb/1024  "Free GB"
    
29. from   v$asm_diskgroup
    
30. /
    
31. 
    
32. prompt
    
33. prompt ASM Disks
    
34. prompt ==============
    
35. 
    
36. col "Group"          form 999
    
37. col "Disk"           form 999
    
38. col "Header"         form a9
    
39. col "Mode"           form a8
    
40. col "Redundancy"     form a10
    
41. col "Failure Group"  form a10
    
42. col "Path"           form a19
    
43. 
    
44. select group_number  "Group"
    
45. ,      disk_number   "Disk"
    
46. ,      header_status "Header"
    
47. ,      mode_status   "Mode"
    
48. ,      state         "State"
    
49. ,      redundancy    "Redundancy"
    
50. ,      total_mb      "Total MB"
    
51. ,      free_mb       "Free MB"
    
52. ,      name          "Disk Name"
    
53. ,      failgroup     "Failure Group"
    
54. ,      path          "Path"
    
55. from   v$asm_disk
    
56. order by group_number
    
57. ,        disk_number
    
58. 
    
59. /
    
60. 
    
61. prompt
    
62. prompt Instances currently accessing these diskgroups
    
63. prompt ==============================================
    
64. 
    
65. select c.group_number  "Group"
    
66. ,      g.name          "Group Name"
    
67. ,      c.instance_name "Instance"
    
68. from   v$asm_client c
    
69. ,      v$asm_diskgroup g
    
70. where  g.group_number=c.group_number
    
71. /
    
72. 
    
73. prompt
    
74. prompt Report the Percentage of Imbalance in all Mounted Diskgroups
    
75. prompt ==============================================
    
76. select dfail, count(dfail) from
    
77. (
    
78. select disk, count(failgroup) as dfail
    
79. from x$kfdpartner, v$asm_disk where
    
80. number_kfdpartner=disk_number and grp=group_number
    
81. group by disk, failgroup
    
82. )
    
83. group by dfail;
    
84. 
    
85. select g.name as "GROUP", d.name as "DISK", d.failgroup, fcnt, pcnt,
    
86. decode(pcnt - fcnt, 0, 'MUST', 'SHOULD') as action from
    
87. (select gnum, DISK1, failgroup, count(failgroup) as fcnt from
    
88. (select gnum, DISK1
    
89. from
    
90. (
    
91. select d.group_number as gnum, disk as disk1,
    
92. count(distinct failgroup) as dfail
    
93. from x$kfdpartner, v$asm_disk_stat d where
    
94. number_kfdpartner=disk_number and grp=d.group_number
    
95. and active_kfdpartner=1
    
96. group by d.group_number, disk
    
97. ), v$asm_disk_stat
    
98. where dfail < 3
    
99. and disk1=disk_number
    
100. and gnum=group_number),
     
101. x$kfdpartner, v$asm_disk_stat d where
     
102. number_kfdpartner=disk_number and grp=d.group_number and grp=gnum
     
103. and disk1=disk
     
104. and active_kfdpartner=1
     
105. group by gnum, disk1, failgroup),
     
106. (select grp, disk, count(disk) as pcnt from x$kfdpartner where
     
107. active_kfdpartner=1 group by grp, disk),
     
108. v$asm_diskgroup_stat g, v$asm_disk_stat d
     
109. where gnum=grp and gnum=g.group_number and gnum=d.group_number and
     
110. disk=disk1 and disk=disk_number and
     
111. ((fcnt = 1 and (pcnt - fcnt) > 3) or ((pcnt - fcnt) = 0))
     
112. /
     
113. 
     
114. col TYPE form a15
     
115. col FILE_NUMBER form 9999 head FILE_NUM
     
116. col GROUP_NUMBER form 9999 head GR_NUM
     
117. col GB for 9999.99
     
118. 
     
119. select GROUP_NUMBER   ,
     
120. FILE_NUMBER          ,
     
121. COMPOUND_INDEX       ,
     
122. INCARNATION          ,
     
123. BLOCK_SIZE           ,
     
124. BLOCKS               ,
     
125. BYTES/1024/1024/1024 GB ,
     
126. TYPE                 ,
     
127. STRIPED              ,
     
128. CREATION_DATE        ,
     
129. MODIFICATION_DATE
     
130. from v$asm_file
     
131. where TYPE != 'ARCHIVELOG'
     
132. /
     
133. 
     
134. prompt
     
135. prompt free ASM disks and their paths
     
136. prompt ===========================
     
137. select header_status , mode_status, path from V$asm_disk
     
138. where header_status in ('FORMER','CANDIDATE')
     
139. /
     
140. 
     
141. show parameter asm
     
142. show parameter size
     
143. show parameter proc
     
144. show parameter cluster
     
145. show parameter instance_type
     
146. show parameter instance_name
     
147. 
     
148. show parameter pfile
     
149. 
     
150. show sga

复制代码

taoy_2008

原因
Storage cloning doesn't create a consistent image during split copy.

There is a problem in other disk metadata structures (PST block, listheader f1b1locn, disk directory, etc.)
该问题是不是一个bug呢？
Solution
The problem is the incorrect initial configuration of the clones on the storage array. The first time copy must be the full sync. After only having a full first copy, it is possible to do incremental clone.
There is various storage cloning methods and technologies used by different storage vendors. As long as the cloning techology creates consistent snapshots of all the disks in an ASM disk group then the diskgroup based on the copied LUNs can be mounted at an alternate site.
- EMC CLARiiON SnapView and MirrorView (also known as BCV copy)
- Hitachi Data Systems (HDS):
Universal Storage Platform Replication Software
- IBM FlashCopy
Most common disk cloning technologies is mentioned in the following link. The documents specific for each vendor also explains the best practices when creating the disk copies.

Maclean Liu(刘相兵

如果你在提问前 已经对你的 问题或症状 有了自己的一些看法，那么可以贴在一楼。

对于这种 你有你的看法， 而与我的诊断方向不一致的情况， 我只能说无法有效的帮助你。


请阅读 《提问的艺术》 http://www.oracledatabase12g.com ... 89%BA%E6%9C%AF.html

在提问的时候 避免说自己的想法， 只说事实。