ORA-15038: ディスク''が''でターゲット・ディスク・グループ[] []と一致しません エラ解析

プロのOracle Databaseの復旧サービスを提供
携帯番号： +86 13764045638 メール：service@parnassusdata.com

ORA-15038: ディスク''が''でターゲット・ディスク・グループ[] []と一致しません

【Oracle ASMデータリカバリ】ORA-15038: disk ‘XXXXXXX’ mismatch on ‘Time Stamp’ with Target Disk Groupエラ解析

Diskgroupをmountするときに、以下のようなエラが現れた、以下の文を読んでください：

SQL> alter diskgroup DATA mount;

alter diskgroup DATA mount

*

ERROR at line 1:

ORA-15032: not all alterations performed

ORA-15040: diskgroup is incomplete

ORA-15042: ASM disk “17” is missing from group number “1”

ORA-15042: ASM disk “16” is missing from group number “1”

ORA-15042: ASM disk “15” is missing from group number “1”

ORA-15042: ASM disk “14” is missing from group number “1”

ORA-15042: ASM disk “13” is missing from group number “1”

ORA-15038: disk ‘ORCL:DATA25’ mismatch on ‘Time Stamp’ with target disk group [1861040353] [1861808156]

ORA-15038: disk ‘ORCL:DATA24’ mismatch on ‘Time Stamp’ with target disk group [1861040353] [1861808156]

ORA-15038: disk ‘ORCL:DATA23’ mismatch on ‘Time Stamp’ with target disk group [1861040353] [1861808156]

ORA-15038: disk ‘ORCL:DATA22’ mismatch on ‘Time Stamp’ with target disk group [1861040353] [1861808156]

ORA-15038: disk ‘ORCL:DATA21’ mismatch on ‘Time Stamp’ with target disk group [1861040353] [1861808156]

[oracle@mlab2 ~]$ oerr ora 15042

15042, 00000, “ASM disk \”%s\” is missing from group number \”%s\” ”

// *Cause:  The specified disk, which is a necessary part of a diskgroup,

//          could not be found on the system.

// *Action: Check the hardware configuration.

//

[oracle@mlab2 ~]$ oerr ora 15038

15038, 00000, “disk ‘%s’ mismatch on ‘%s’ with target disk group [%s] [%s]”

// *Cause:  An attempt was made to mount into a disk group a disk whose

//          recorded allocation unit size, metadata block size, physical

//          sector size, or creation time stamp was inconsistent with the other

//          disk group members.

// *Action: Check if the system configuration has changed. Verify disk

//          discovery string.

//

一般的に、そのエラはOSレベルの多パス配置にトラブルが起こった。あるノートに大量なストレージが現れたことに引き起こした。

例えば：

NOTE: cache opening disk 11 of grp 1: DATA2 label:DATA2 <<<<<<<<<<<<<<<<<< 5 NOTE: cache opening disk 12 of grp 1: DATA20 label:DATA20 >

NOTE: cache opening disk 13 of grp 1: DATA3 label:DATA3 <<<<<<<<<<<<<<<<<<<<<< 6

NOTE: cache opening disk 14 of grp 1: DATA4 label:DATA4

NOTE: cache opening disk 15 of grp 1: DATA5 label:DATA5

NOTE: cache opening disk 16 of grp 1: DATA6 label:DATA6

NOTE: cache opening disk 17 of grp 1: DATA7 label:DATA7

NOTE: cache opening disk 18 of grp 1: DATA8 label:DATA8

NOTE: cache opening disk 19 of grp 1: DATA9 label:DATA9

そしてkfedでDISK HEADERを検証する、以下のスクリプトを使ってください：

#! /bin/sh

rm /tmp/kfed_DH.out /tmp/kfed_FS.out /tmp/kfed_BK.out /tmp/kfed_FD.out /tmp/kfed_DD.out /tmp/kfed_PST.out

for i in `ls /dev/asm-disk*`

do

echo $i >> /tmp/kfed_DH.out

kfed read $i >> /tmp/kfed_DH.out

echo $i >> /tmp/kfed_FS.out

kfed read $i blkn=1 >> /tmp/kfed_FS.out

echo $i >> /tmp/kfed_BK.out

kfed read $i aun=1 blkn=254 >> /tmp/kfed_BK.out

echo $i >> /tmp/kfed_FD.out

kfed read $i aun=2 blkn=1 >> /tmp/kfed_FD.out

echo $i >> /tmp/kfed_DD.out

kfed read $i aun=2 blkn=2 >> /tmp/kfed_DD.out

echo $i >> /tmp/kfed_PST.out

kfed read $i aun=1 blkn=2 >> /tmp/kfed_PST.out

done