如果自己搞不定可以找诗檀软件专业ORACLE数据库修复团队成员帮您恢复!
诗檀软件专业数据库修复团队
服务热线 : 13764045638 QQ号:47079569 邮箱:[email protected]
SQL> alter diskgroup datadg add disk ‘/dev/asm-diskh’ rebalance power 2;
alter diskgroup datadg add disk ‘/dev/asm-diskh’ rebalance power 2
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15075: disk(s) are not visible cluster-wide
SQL> alter diskgroup datadg add disk ‘/dev/asm-diskh’ ;
alter diskgroup datadg add disk ‘/dev/asm-diskh’
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15075: disk(s) are not visible cluster-wide
15032, 00000, “not all alterations performed”
// *Cause: At least one ALTER DISKGROUP action failed.
// *Action: Check the other messages issued along with this summary error.
//
15075, 00000, “disk(s) are not visible cluster-wide”
// *Cause: An ALTER DISKGROUP ADD DISK command specified a disk that could
// not be discovered by one or more nodes in a RAC cluster
// configuration.
// *Action: Determine which disks are causing the problem from the
// GV$ASM_DISK fixed view. Check operating system permissions
// for the device and the storage sub-system configuration on
// each node in a RAC cluster that cannot identify the disk.
//
SQL> alter diskgroup datadg add disk ‘/dev/asm-diskh’ ;
Diskgroup altered.
1节点
1* select GROUP_NUMBER,DISK_NUMBER,path,HEADER_STATUS from v$ASM_DISK order by 1,2
SQL> /
GROUP_NUMBER DISK_NUMBER PATH HEADER_STATUS
———— ———– ——————– ————————————
1 0 /dev/asm-diske MEMBER
1 1 /dev/asm-diskf MEMBER
1 2 /dev/asm-diskg MEMBER
1 5 /dev/asm-diskh MEMBER
2 0 /dev/asm-diskb MEMBER
2 1 /dev/asm-diskc MEMBER
2 2 /dev/asm-diskd MEMBER
7 rows selected.
2节点
SQL> select GROUP_NUMBER,DISK_NUMBER,path,HEADER_STATUS from v$ASM_DISK order by 1,2;
GROUP_NUMBER DISK_NUMBER PATH HEADER_STATUS
———— ———– ——————– ————————————
1 0 /dev/asm-diske MEMBER
1 1 /dev/asm-diskf MEMBER
1 2 /dev/asm-diskg MEMBER
1 5 /dev/asm-diskz MEMBER
2 0 /dev/asm-diskb MEMBER
2 1 /dev/asm-diskc MEMBER
2 2 /dev/asm-diskd MEMBER
7 rows selected.
NOTE: disk validation pending for group 1/0x5448421c (DATADG)
SUCCESS: validated disks for 1/0x5448421c (DATADG)
NOTE: disk validation pending for group 1/0x5448421c (DATADG)
NOTE: Assigning number (1,5) to disk (/dev/asm-diskz)
SUCCESS: validated disks for 1/0x5448421c (DATADG)
NOTE: membership refresh pending for group 1/0x5448421c (DATADG)
Tue Mar 12 20:36:59 2013
GMON querying group 1 at 7 for pid 18, osid 2763
NOTE: cache opening disk 5 of grp 1: DATADG_0005 path:/dev/asm-diskz
GMON querying group 1 at 8 for pid 18, osid 2763
SUCCESS: refreshed membership for 1/0x5448421c (DATADG)
Tue Mar 12 20:37:02 2013
NOTE: Attempting voting file refresh on diskgroup DATADG
Tue Mar 12 20:37:06 2013
ALTER SYSTEM SET local_listener=’ (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.184)(PORT=1521))))’ SCOPE=MEMORY SID=’+ASM2′;
Tue Mar 12 20:37:54 2013
NOTE: membership refresh pending for group 1/0x5448421c (DATADG)
Tue Mar 12 20:37:56 2013
GMON querying group 1 at 9 for pid 18, osid 2763
SUCCESS: refreshed membership for 1/0x5448421c (DATADG)
NOTE: Attempting voting file refresh on diskgroup DATADG
[grid@vmac2 ~]$ kfed read /dev/asm-diskz
kfbh.endian: 1 ; 0x000: 0x01
kfbh.hard: 130 ; 0x001: 0x82
kfbh.type: 1 ; 0x002: KFBTYP_DISKHEAD
kfbh.datfmt: 1 ; 0x003: 0x01
kfbh.block.blk: 0 ; 0x004: blk=0
kfbh.block.obj: 2147483653 ; 0x008: disk=5
kfbh.check: 1582693660 ; 0x00c: 0x5e55fd1c
kfbh.fcn.base: 0 ; 0x010: 0x00000000
kfbh.fcn.wrap: 0 ; 0x014: 0x00000000
kfbh.spare1: 0 ; 0x018: 0x00000000
kfbh.spare2: 0 ; 0x01c: 0x00000000
kfdhdb.driver.provstr: ORCLDISK ; 0x000: length=8
kfdhdb.driver.reserved[0]: 0 ; 0x008: 0x00000000
kfdhdb.driver.reserved[1]: 0 ; 0x00c: 0x00000000
kfdhdb.driver.reserved[2]: 0 ; 0x010: 0x00000000
kfdhdb.driver.reserved[3]: 0 ; 0x014: 0x00000000
kfdhdb.driver.reserved[4]: 0 ; 0x018: 0x00000000
kfdhdb.driver.reserved[5]: 0 ; 0x01c: 0x00000000
kfdhdb.compat: 186646528 ; 0x020: 0x0b200000
kfdhdb.dsknum: 5 ; 0x024: 0x0005
kfdhdb.grptyp: 1 ; 0x026: KFDGTP_EXTERNAL
kfdhdb.hdrsts: 3 ; 0x027: KFDHDR_MEMBER
kfdhdb.dskname: DATADG_0005 ; 0x028: length=11
kfdhdb.grpname: DATADG ; 0x048: length=6
kfdhdb.fgname: DATADG_0005 ; 0x068: length=11
kfdhdb.capname: ; 0x088: length=0
kfdhdb.crestmp.hi: 32984459 ; 0x0a8: HOUR=0xb DAYS=0xc MNTH=0x3 YEAR=0x7dd
kfdhdb.crestmp.lo: 2470649856 ; 0x0ac: USEC=0x0 MSEC=0xc8 SECS=0x34 MINS=0x24
kfdhdb.mntstmp.hi: 32984459 ; 0x0b0: HOUR=0xb DAYS=0xc MNTH=0x3 YEAR=0x7dd
kfdhdb.mntstmp.lo: 2470650880 ; 0x0b4: USEC=0x0 MSEC=0xc9 SECS=0x34 MINS=0x24
kfdhdb.secsize: 512 ; 0x0b8: 0x0200
kfdhdb.blksize: 4096 ; 0x0ba: 0x1000
kfdhdb.ausize: 1048576 ; 0x0bc: 0x00100000
kfdhdb.mfact: 113792 ; 0x0c0: 0x0001bc80
kfdhdb.dsksize: 5120 ; 0x0c4: 0x00001400
kfdhdb.pmcnt: 2 ; 0x0c8: 0x00000002
kfdhdb.fstlocn: 1 ; 0x0cc: 0x00000001
kfdhdb.altlocn: 2 ; 0x0d0: 0x00000002
kfdhdb.f1b1locn: 0 ; 0x0d4: 0x00000000
kfdhdb.redomirrors[0]: 0 ; 0x0d8: 0x0000
kfdhdb.redomirrors[1]: 0 ; 0x0da: 0x0000
kfdhdb.redomirrors[2]: 0 ; 0x0dc: 0x0000
kfdhdb.redomirrors[3]: 0 ; 0x0de: 0x0000
kfdhdb.dbcompat: 168820736 ; 0x0e0: 0x0a100000
kfdhdb.grpstmp.hi: 32983191 ; 0x0e4: HOUR=0x17 DAYS=0x4 MNTH=0x2 YEAR=0x7dd
kfdhdb.grpstmp.lo: 2328331264 ; 0x0e8: USEC=0x0 MSEC=0x1e1 SECS=0x2c MINS=0x22
kfdhdb.vfstart: 0 ; 0x0ec: 0x00000000
kfdhdb.vfend: 0 ; 0x0f0: 0x00000000
kfdhdb.spfile: 0 ; 0x0f4: 0x00000000
kfdhdb.spfflg: 0 ; 0x0f8: 0x00000000
kfdhdb.ub4spare[0]: 0 ; 0x0fc: 0x00000000
kfdhdb.ub4spare[1]: 0 ; 0x100: 0x00000000
kfdhdb.ub4spare[2]: 0 ; 0x104: 0x00000000
kfdhdb.ub4spare[3]: 0 ; 0x108: 0x00000000
kfdhdb.ub4spare[4]: 0 ; 0x10c: 0x00000000
kfdhdb.ub4spare[5]: 0 ; 0x110: 0x00000000
kfdhdb.ub4spare[6]: 0 ; 0x114: 0x00000000
kfdhdb.ub4spare[7]: 0 ; 0x118: 0x00000000
kfdhdb.ub4spare[8]: 0 ; 0x11c: 0x00000000
kfdhdb.ub4spare[9]: 0 ; 0x120: 0x00000000
kfdhdb.ub4spare[10]: 0 ; 0x124: 0x00000000
kfdhdb.ub4spare[11]: 0 ; 0x128: 0x00000000
kfdhdb.ub4spare[12]: 0 ; 0x12c: 0x00000000
kfdhdb.ub4spare[13]: 0 ; 0x130: 0x00000000
kfdhdb.ub4spare[14]: 0 ; 0x134: 0x00000000
kfdhdb.ub4spare[15]: 0 ; 0x138: 0x00000000
kfdhdb.ub4spare[16]: 0 ; 0x13c: 0x00000000
kfdhdb.ub4spare[17]: 0 ; 0x140: 0x00000000
kfdhdb.ub4spare[18]: 0 ; 0x144: 0x00000000
kfdhdb.ub4spare[19]: 0 ; 0x148: 0x00000000
kfdhdb.ub4spare[20]: 0 ; 0x14c: 0x00000000
kfdhdb.ub4spare[21]: 0 ; 0x150: 0x00000000
kfdhdb.ub4spare[22]: 0 ; 0x154: 0x00000000
kfdhdb.ub4spare[23]: 0 ; 0x158: 0x00000000
kfdhdb.ub4spare[24]: 0 ; 0x15c: 0x00000000
kfdhdb.ub4spare[25]: 0 ; 0x160: 0x00000000
kfdhdb.ub4spare[26]: 0 ; 0x164: 0x00000000
kfdhdb.ub4spare[27]: 0 ; 0x168: 0x00000000
kfdhdb.ub4spare[28]: 0 ; 0x16c: 0x00000000
kfdhdb.ub4spare[29]: 0 ; 0x170: 0x00000000
kfdhdb.ub4spare[30]: 0 ; 0x174: 0x00000000
kfdhdb.ub4spare[31]: 0 ; 0x178: 0x00000000
kfdhdb.ub4spare[32]: 0 ; 0x17c: 0x00000000
kfdhdb.ub4spare[33]: 0 ; 0x180: 0x00000000
kfdhdb.ub4spare[34]: 0 ; 0x184: 0x00000000
kfdhdb.ub4spare[35]: 0 ; 0x188: 0x00000000
kfdhdb.ub4spare[36]: 0 ; 0x18c: 0x00000000
kfdhdb.ub4spare[37]: 0 ; 0x190: 0x00000000
kfdhdb.ub4spare[38]: 0 ; 0x194: 0x00000000
kfdhdb.ub4spare[39]: 0 ; 0x198: 0x00000000
kfdhdb.ub4spare[40]: 0 ; 0x19c: 0x00000000
kfdhdb.ub4spare[41]: 0 ; 0x1a0: 0x00000000
kfdhdb.ub4spare[42]: 0 ; 0x1a4: 0x00000000
kfdhdb.ub4spare[43]: 0 ; 0x1a8: 0x00000000
kfdhdb.ub4spare[44]: 0 ; 0x1ac: 0x00000000
kfdhdb.ub4spare[45]: 0 ; 0x1b0: 0x00000000
kfdhdb.ub4spare[46]: 0 ; 0x1b4: 0x00000000
kfdhdb.ub4spare[47]: 0 ; 0x1b8: 0x00000000
kfdhdb.ub4spare[48]: 0 ; 0x1bc: 0x00000000
kfdhdb.ub4spare[49]: 0 ; 0x1c0: 0x00000000
kfdhdb.ub4spare[50]: 0 ; 0x1c4: 0x00000000
kfdhdb.ub4spare[51]: 0 ; 0x1c8: 0x00000000
kfdhdb.ub4spare[52]: 0 ; 0x1cc: 0x00000000
kfdhdb.ub4spare[53]: 0 ; 0x1d0: 0x00000000
kfdhdb.acdb.aba.seq: 0 ; 0x1d4: 0x00000000
kfdhdb.acdb.aba.blk: 0 ; 0x1d8: 0x00000000
kfdhdb.acdb.ents: 0 ; 0x1dc: 0x0000
kfdhdb.acdb.ub2spare: 0 ; 0x1de: 0x0000
以上 ORA-15032、ORA-15075 ASM DISK PATH Problem就是由于LUN配置不当,导致LUN并非在RAC的多个节点上可见所导致的。
对于此类问题 首先确认已经合理设置了设备文件权限。
接着做如下操作来进一步确认:
echo "======================" > fakedata.txt
date >> fakedata.txt
echo "======================" >> fakedata.txt
dd if=/home/oracle/test/fakedata.txt of=你要检验的设备名 bs=4096 count=1 conv=notrunc
之后使用od命令在多个节点上查看该设备上的内容即可确认在集群环境中该设备是否指向同一个LUN
od -c 你要检验的设备名 | more
Leave a Reply