天萃荷净
运维DBA反映在Oracle数据库中MOUNT磁盘组是遇到报错ORA-15032 ORA-15036,结合MOS官方分析产生原因为OS中磁盘的大小与ASM磁盘头中保留的磁盘大小不一致,导致报错。
测试环境出现下面报错
SQL> alter diskgroup data mount;
alter diskgroup data mount
*
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15036: disk ‘/dev/rdsk/c1t3d0p0’ is truncated
1,查看ASM中磁盘大小
$ kfod disks=all
——————————————————————————–
Disk Size Path
================================================================================
1: 5215 Mb /dev/rdsk/c1t2d0p0
2: 5748 Mb /dev/rdsk/c1t2d0p1
3: 5018 Mb /dev/rdsk/c1t2d0s0
4: 5215 Mb /dev/rdsk/c1t3d0p0
5: 5215 Mb /dev/rdsk/c1t4d0p0
——————————————————————————–
ORACLE_SID ORACLE_HOME
================================================================================
+ASM /oracle/app/oracle/product/10.2.0/db_1
$ kfed dev=/dev/rdsk/c1t2d0s0 op=read
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: T=0 NUMB=0x0
kfbh.block.obj: 2147483648 ; 0x008: TYPE=0x8 NUMB=0x0
kfbh.check: 2257558236 ; 0x00c: 0x868f9adc
kfbh.fcn.base: 443 ; 0x010: 0x000001bb
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
kfdhOracleоdb.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: 168820736 ; 0x020: 0x0a100000
kfdhdb.dsknum: 0 ; 0x024: 0x0000
kfdhdb.grptyp: 1 ; 0x026: KFDGTP_EXTERNAL
kfdhdb.hdrsts: 3 ; 0x027: KFDHDR_MEMBER
kfdhdb.dskname: DATA_0000 ; 0x028: length=9
kfdhdb.grpname: DATA ; 0x048: length=4
kfdhdb.fgname: DATA_0000 ; 0x068: length=9
kfdhdb.capname: ; 0x088: length=0
kfdhdb.crestmp.hi: 33006767 ; 0x0a8: HOUR=0xf DAYS=0x5 MNTH=0x9 YEAR=0x7de
kfdhdb.crestmp.lo: 3853630464 ; 0x0ac: USEC=0x0 MSEC=0x6f SECS=0x1b MINS=0x39
kfdhdb.mntstmp.hi: 33006768 ; 0x0b0: HOUR=0x10 DAYS=0x5 MNTH=0x9 YEAR=0x7de
kfdhdb.mntstmp.lo: 1590160384 ; 0x0b4: USEC=0x0 MSEC=0x1fb SECS=0x2c MINS=0x17
kfdhdb.secsize: 512 ; 0x0b8: 0x0200
kfdhdb.blksize: 4096 ; 0x0ba: 0x1000
kfdhdb.ausize: 1048576 ; 0x0bc: 0x00100000
kfdhdb.mfact: 113792 ; 0x0c0: 0x0001bc80
kfdhdb.dsksize: 5018 ; 0x0c4: 0x0000139a
kfdhdb.pmcnt: 2 ; 0x0c8: 0x00000002
kfdhdb.fstlocn: 1 ; 0x0cc: 0x00000001
kfdhdb.altlocn: 2 ; 0x0d0: 0x00000002
kfdhdb.f1b1locn: 2 ; 0x0d4: 0x00000002
kfdhdb.redomirrors[0]: 0 ; 0x0d8: 0x0000
kfdhdb.redomirrors[1]: 65535 ; 0x0da: 0xffff
kfdhdb.redomirrors[2]: 65535 ; 0x0dc: 0xffff
kfdhdb.redomirrors[3]: 65535 ; 0x0de: 0xffff
kfdhdb.dbcompat: 168820736 ; 0x0e0: 0x0a100000
kfdhdb.grpstmp.hi: 33006767 ; 0x0e4: HOUR=0xf DAYS=0x5 MNTH=0x9 YEAR=0x7de
kfdhdb.grpstmp.lo: 3853574144 ; 0x0e8: USEC=0x0 MSEC=0x38 SECS=0x1b MINS=0x39
$ kfed dev=/dev/rdsk/c1t3d0p0 op=read
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: T=0 NUMB=0x0
kfbh.block.obj: 2147483649 ; 0x008: TYPE=0x8 NUMB=0x1
kfbh.check: 806530272 ; 0x00c: 0x3012ace0
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: 168820736 ; 0x020: 0x0a100000
kfdhdb.dsknum: 1 ; 0x024: 0x0001
kfdhdb.grptyp: 1 ; 0x026: KFDGTP_EXTERNAL
kfdhdb.hdrsts: 3 ; 0x027: KFDHDR_MEMBER
kfdhdb.dskname: DATA_0001 ; 0x028: length=9
kfdhdb.grpname: DATA ; 0x048: length=4
kfdhdb.fgname: DATA_0001 ; 0x068: length=9
kfdhdb.capname: ; 0x088: length=0
kfdhdb.crestmp.hi: 33006768 ; 0x0a8: HOUR=0x10 DAYS=0x5 MNTH=0x9 YEAR=0x7de
kfdhdb.crestmp.lo: 1733936128 ; 0x0ac: USEC=0x0 MSEC=0x271 SECS=0x35 MINS=0x19
kfdhdb.mntstmp.hi: 33006768 ; 0x0b0: HOUR=0x10 DAYS=0x5 MNTH=0x9 YEAR=0x7de
kfdhdb.mntstmp.lo: 1733937152 ; 0x0b4: USEC=0x0 MSEC=0x272 SECS=0x35 MINS=0x19
kfdhdb.secsize: 512 ; 0x0b8: 0x0200
kfdhdb.blksize: 4096 ; 0x0ba: 0x1000
kfdhdb.ausize: 1048576 ; 0x0bc: 0x00100000
kfdhdb.mfact: 113792 ; 0x0c0: 0x0001bc80
kfdhdb.dsksize: 33408 ; 0x0c4: 0x00008280这里明显是错误的
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: 33006767 ; 0x0e4: HOUR=0xf DAYS=0x5 MNTH=0x9 YEAR=0x7de
kfdhdb.grpstmp.lo: 3853574144 ; 0x0e8: USEC=0x0 MSEC=0x38 SECS=0x1b MINS=0x39
kfdhdb.ub4spare[0]: 0 ; 0x0ec: 0x00000000
由于OS中磁盘的大小与ASM磁盘头中保留的磁盘大小不一致,导致报错
查看OS信息
format> disk
AVAILABLE DISK SELECTIONS:
0. c1t0d0 /pci@0,0/pci15ad,1976@10/sd@0,0
1. c1t1d0 /pci@0,0/pci15ad,1976@10/sd@1,0
2. c1t2d0 /pci@0,0/pci15ad,1976@10/sd@2,0
3. c1t3d0 /pci@0,0/pci15ad,1976@10/sd@3,0
4. c1t4d0 /pci@0,0/pci15ad,1976@10/sd@4,0
Specify disk (enter its number)[3]: 3
selecting c1t3d0
[disk formatted]
format> parition
`parition’ is not expected.
format> partition
WARNING – This disk may be in use by an application that has
modified the fdisk table. Ensure that this disk is
not currently in use before proceeding to use fdisk.
2 修改磁盘大小
$ kfed dev=/dev/rdsk/c1t3d0p0 op=read >/tmp/c1t3d0p0.txt
$ vi /tmp/c1t3d0p0.txt
kfdhdb.dsksize: 5017 ; 0x0c4: 0x00008280
$ kfed dev=/dev/rdsk/c1t3d0p0 op=merge text=/tmp/c1t3d0p0.txt
SQL> alter diskgroup data mount;
Diskgroup altered.
本文固定链接: http://www.htz.pw/2014/09/07/ora-15036-disk-devrdskc1t3d0p0-is-truncated.html | 认真就输
--------------------------------------ORACLE-DBA----------------------------------------
最权威、专业的Oracle案例资源汇总之【案例】Oracle报错ORA-15032 ORA-15036产生原因和MOS官方解决办法