oracle中15042,【Oracle ASM数据恢复】ORA-15042: ASM disk is missing after add disk took place错误解析...

最新推荐文章于 2023-06-30 16:53:26 发布
最新推荐文章于 2023-06-30 16:53:26 发布
阅读量328 收藏
点赞数
文章标签： oracle中15042

01fac6460a22031b8af8da5848698a70.png

如果在10.2.0.4 以后版本当向ASM Diskgroup中加入新的磁盘后diskgroup被dismount，尝试mount该diskgroup时报错ORA-15042: ASM disk is missing after add disk took place，那么可以参考本帖。

Tue Feb 12 17:33:59 2013

NOTE: X->S down convert bast on F1B3 bastCount=2

Wed Feb 13 04:06:38 2013 < ALTER DISKGROUP DG1 ADD DISK

'/dev/mapper/t1_asm03p1',

'/dev/mapper/t1_asm04p1',

'/dev/mapper/t1_asm05p1',

'/dev/mapper/t1_asm06p1'

rebalance power 4

Wed Feb 13 04:06:38 2013

NOTE: reconfiguration of group 1/0x53bffa1 (DG1), full=1

Wed Feb 13 04:06:39 2013

NOTE: initializing header on grp 1 disk DG1_0026

NOTE: initializing header on grp 1 disk DG1_0027

NOTE: initializing header on grp 1 disk DG1_0028

NOTE: initializing header on grp 1 disk DG1_0029

NOTE: cache opening disk 26 of grp 1: DG1_0026 path:/dev/mapper/t1_asm03p1

NOTE: cache opening disk 27 of grp 1: DG1_0027 path:/dev/mapper/t1_asm04p1

NOTE: cache opening disk 28 of grp 1: DG1_0028 path:/dev/mapper/t1_asm05p1

NOTE: cache opening disk 29 of grp 1: DG1_0029 path:/dev/mapper/t1_asm06p1

NOTE: PST update: grp = 1

NOTE: requesting all-instance disk validation for group=1

Wed Feb 13 04:06:39 2013

NOTE: disk validation pending for group 1/0x53bffa1 (DG1)

Wed Feb 13 04:06:40 2013

NOTE: requesting all-instance membership refresh for group=1

Wed Feb 13 04:06:40 2013

NOTE: membership refresh pending for group 1/0x53bffa1 (DG1)

SUCCESS: validated disks for 1/0x53bffa1 (DG1)

SUCCESS: refreshed membership for 1/0x53bffa1 (DG1)

Wed Feb 13 04:07:11 2013 < ALTER DISKGROUP DG1 ADD DISK

'/dev/mapper/t1_asm03p1',

'/dev/mapper/t1_asm04p1',

'/dev/mapper/t1_asm05p1',

'/dev/mapper/t1_asm06p1'

rebalance power 4

NOTE: cache closing disk 26 of grp 1: DG1_0026 path:/dev/mapper/t1_asm03p1

NOTE: cache closing disk 26 of grp 1: DG1_0026 path:/dev/mapper/t1_asm03p1

NOTE: cache closing disk 27 of grp 1: DG1_0027 path:/dev/mapper/t1_asm04p1

NOTE: cache closing disk 27 of grp 1: DG1_0027 path:/dev/mapper/t1_asm04p1

NOTE: cache closing disk 28 of grp 1: DG1_0028 path:/dev/mapper/t1_asm05p1

NOTE: cache closing disk 28 of grp 1: DG1_0028 path:/dev/mapper/t1_asm05p1

NOTE: cache closing disk 29 of grp 1: DG1_0029 path:/dev/mapper/t1_asm06p1

NOTE: cache closing disk 29 of grp 1: DG1_0029 path:/dev/mapper/t1_asm06p1

Wed Feb 13 04:09:36 2013

SQL> ALTER DISKGROUP DG1 ADD DISK

'/dev/mapper/t1_asm03p1',

'/dev/mapper/t1_asm04p1',

'/dev/mapper/t1_asm05p1',

'/dev/mapper/t1_asm06p1'

rebalance power 4

Wed Feb 13 04:09:36 2013

NOTE: reconfiguration of group 1/0x53bffa1 (DG1), full=1

Wed Feb 13 04:09:36 2013

NOTE: requesting all-instance membership refresh for group=1

Wed Feb 13 04:09:36 2013

NOTE: membership refresh pending for group 1/0x53bffa1 (DG1)

SUCCESS: validated disks for 1/0x53bffa1 (DG1)

NOTE: PST update: grp = 1, dsk = 26, mode = 0x4

NOTE: PST update: grp = 1, dsk = 27, mode = 0x4

NOTE: PST update: grp = 1, dsk = 28, mode = 0x4

NOTE: PST update: grp = 1, dsk = 29, mode = 0x4

Wed Feb 13 04:09:42 2013

ERROR: too many offline disks in PST (grp 1)

Wed Feb 13 04:09:42 2013

SUCCESS: refreshed membership for 1/0x53bffa1 (DG1)

ERROR: ORA-15040 thrown in RBAL for group number 1

Wed Feb 13 04:09:42 2013

Errors in file /opt/oracle/product/10.2.0/asm/admin/+ASM/bdump/+asm1_rbal_30556.trc:

ORA-15040: diskgroup is incomplete

ORA-15066: offlining disk "" may result in a data loss

ORA-15042: ASM disk "29" is missing

ORA-15042: ASM disk "28" is missing

ORA-15042: ASM disk "27" is missing

ORA-15042: ASM disk "26" is missing

Wed Feb 13 04:09:43 2013

ERROR: PST-initiated MANDATORY DISMOUNT of group DG1

Received dirty detach msg from node 3 for dom 1

Wed Feb 13 04:09:43 2013

Dirty detach reconfiguration started (old inc 12, new inc 12)

这时我们需要分析ASM的 DISK DIRECTORY和PST以及 DISK HEADER:

我们来看看：

kfddde[4].entry.incarn: 2 ; 0x724: A=0 NUMM=0x1

kfddde[4].entry.hash: 0 ; 0x728: 0x00000000

kfddde[4].entry.refer.number: 0 ; 0x72c: 0x00000000

kfddde[4].entry.refer.incarn: 0 ; 0x730: A=0 NUMM=0x0

kfddde[4].dsknum: 28 ; 0x734: 0x001c

kfddde[4].state: 8 ; 0x736: KFDSTA_ADDING <<<===============================

kfddde[4].ub1spare: 0 ; 0x737: 0x00

kfddde[4].dskname: DG1_0028 ; 0x738: length=8

kfddde[4].fgname: DG1_0028 ; 0x758: length=8

kfddde[4].crestmp.hi: 32983460 ; 0x778: HOUR=0x4 DAYS=0xd MNTH=0x2 YEAR=0x7dd

kfddde[4].crestmp.lo: 443710464 ; 0x77c: USEC=0x0 MSEC=0x9f SECS=0x27 MINS=0x6

kfddde[4].failstmp.hi: 0 ; 0x780: HOUR=0x0 DAYS=0x0 MNTH=0x0 YEAR=0x0

kfddde[4].failstmp.lo: 0 ; 0x784: USEC=0x0 MSEC=0x0 SECS=0x0 MINS=0x0

kfddde[4].timer: 0 ; 0x788: 0x00000000

kfddde[4].size: 307199 ; 0x78c: 0x0004afff

kfddde[3].entry.incarn: 2 ; 0x564: A=0 NUMM=0x1

kfddde[3].entry.hash: 0 ; 0x568: 0x00000000

kfddde[3].entry.refer.number: 0 ; 0x56c: 0x00000000

kfddde[3].entry.refer.incarn: 0 ; 0x570: A=0 NUMM=0x0

kfddde[3].dsknum: 27 ; 0x574: 0x001b

kfddde[3].state: 8 ; 0x576: KFDSTA_ADDING <<<===============================

kfddde[3].ub1spare: 0 ; 0x577: 0x00

kfddde[3].dskname: DG1_0027 ; 0x578: length=8

kfddde[3].fgname: DG1_0027 ; 0x598: length=8

kfddde[3].crestmp.hi: 32983460 ; 0x5b8: HOUR=0x4 DAYS=0xd MNTH=0x2 YEAR=0x7dd

kfddde[3].crestmp.lo: 443710464 ; 0x5bc: USEC=0x0 MSEC=0x9f SECS=0x27 MINS=0x6

kfddde[3].failstmp.hi: 0 ; 0x5c0: HOUR=0x0 DAYS=0x0 MNTH=0x0 YEAR=0x0

kfddde[3].failstmp.lo: 0 ; 0x5c4: USEC=0x0 MSEC=0x0 SECS=0x0 MINS=0x0

kfddde[4].entry.hash: 0 ; 0x728: 0x00000000

kfddde[4].entry.refer.number: 0 ; 0x72c: 0x00000000

kfddde[4].entry.refer.incarn: 0 ; 0x730: A=0 NUMM=0x0

kfddde[4].dsknum: 28 ; 0x734: 0x001c

kfddde[4].state: 8 ; 0x736: KFDSTA_ADDING <<<===============================

kfddde[4].ub1spare: 0 ; 0x737: 0x00

kfddde[4].dskname: DG1_0028 ; 0x738: length=8

kfddde[4].fgname: DG1_0028 ; 0x758: length=8

kfddde[4].crestmp.hi: 32983460 ; 0x778: HOUR=0x4 DAYS=0xd MNTH=0x2 YEAR=0x7dd

kfddde[4].crestmp.lo: 443710464 ; 0x77c: USEC=0x0 MSEC=0x9f SECS=0x27 MINS=0x6

kfddde[4].failstmp.hi: 0 ; 0x780: HOUR=0x0 DAYS=0x0 MNTH=0x0 YEAR=0x0

kfddde[4].failstmp.lo: 0 ; 0x784: USEC=0x0 MSEC=0x0 SECS=0x0 MINS=0x0

kfddde[4].timer: 0 ; 0x788: 0x00000000

kfddde[4].size: 307199 ; 0x78c: 0x0004afff

kfddde[5].entry.incarn: 2 ; 0x8e4: A=0 NUMM=0x1

kfddde[5].entry.hash: 0 ; 0x8e8: 0x00000000

kfddde[5].entry.refer.number: 0 ; 0x8ec: 0x00000000

kfddde[5].entry.refer.incarn: 0 ; 0x8f0: A=0 NUMM=0x0

kfddde[5].dsknum: 29 ; 0x8f4: 0x001d

kfddde[5].state: 8 ; 0x8f6: KFDSTA_ADDING <<<===============================

kfddde[5].ub1spare: 0 ; 0x8f7: 0x00

kfddde[5].dskname: DG1_0029 ; 0x8f8: length=8

kfddde[5].fgname: DG1_0029 ; 0x918: length=8

kfddde[5].crestmp.hi: 32983460 ; 0x938: HOUR=0x4 DAYS=0xd MNTH=0x2 YEAR=0x7dd

kfddde[5].crestmp.lo: 443710464 ; 0x93c: USEC=0x0 MSEC=0x9f SECS=0x27 MINS=0x6

kfddde[5].failstmp.hi: 0 ; 0x940: HOUR=0x0 DAYS=0x0 MNTH=0x0 YEAR=0x0

kfddde[5].failstmp.lo: 0 ; 0x944: USEC=0x0 MSEC=0x0 SECS=0x0 MINS=0x0

kfddde[5].timer: 0 ; 0x948: 0x00000000

File_name :: dg1_3.kfed

/dev/mapper/t1_asm05p1

kfbh.endian: 0 ; 0x000: 0x00

kfbh.hard: 0 ; 0x001: 0x00

kfbh.type: 0 ; 0x002: KFBTYP_INVALID

kfbh.datfmt: 0 ; 0x003: 0x00

kfbh.block.blk: 0 ; 0x004: T=0 NUMB=0x0

kfbh.block.obj: 0 ; 0x008: TYPE=0x0 NUMB=0x0

kfbh.check: 0 ; 0x00c: 0x00000000

kfbh.fcn.base: 0 ; 0x010: 0x00000000

kfbh.fcn.wrap: 0 ; 0x014: 0x00000000

kfbh.spare1: 0 ; 0x018: 0x00000000

kfbh.spare2: 0 ; 0x01c: 0x00000000

/dev/mapper/t1_asm06p1

kfbh.endian: 0 ; 0x000: 0x00

kfbh.hard: 0 ; 0x001: 0x00

kfbh.type: 0 ; 0x002: KFBTYP_INVALID

kfbh.datfmt: 0 ; 0x003: 0x00

kfbh.block.blk: 0 ; 0x004: T=0 NUMB=0x0

kfbh.block.obj: 0 ; 0x008: TYPE=0x0 NUMB=0x0

kfbh.check: 0 ; 0x00c: 0x00000000

kfbh.fcn.base: 0 ; 0x010: 0x00000000

kfbh.fcn.wrap: 0 ; 0x014: 0x00000000

kfbh.spare1: 0 ; 0x018: 0x00000000

kfbh.spare2: 0 ; 0x01c: 0x00000000

从上面的DISK DIRECTORY中的status可以看到KFDSTA_ADDING ，即新加入的磁盘仍在加入过程中，同时也没有完成rebalance。

查询PST的脚本如下：

vi kfed_pst.sh

-----

#! /bin/sh

rm /tmp/kfed_PST.out

for i in `ls *`

do

echo $i >> /tmp/kfed_PST.out

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

done

----

chmod u+x kfed_pst.sh

对于该问题需要手动Patch ASM metadata的方法来解决，否则无法让diskgroup重新mount起来。

KayJack
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
oracle中15042,oracle中hp平台rdisk中磁盘丢失导致asm启动报ORA-15042恢复
weixin_33502070的博客
04-03 245
有老朋友找到我,说一个客户的数据库异常,问题是asm无法正常mount,提示是缺少两块磁盘.问我是否可以恢复.因为是内网环境,通过他那边发过来的零零散散的信息,大概分析如下asm alert日志报错ERROR: diskgroup DGROUP1 was not mountedFri Aug 12 16:03:12 EAT 2016SQL> alter diskgroup DGROUP1 m...
一次存储盘异常引起的ASM磁盘OFFLINE处理
最新发布
还不算晕的专栏
07-26 887
4.尝试重新MOUNT磁盘组，以及修复OCR（NORMAL冗余）磁盘组中OFFLINE后超过REPAIR时间的DROP状态磁盘。2.检查操作系统的日志（linux /var/opt/message），确定出现了存储盘的IO报错（事后分析为链路问题）登陆系统查看，数据库实例异常关闭，日志指向ASM DISKGROUP异常；1.检查集群状态、ASM实例状态，发现ASM磁盘组已经DISMOUNT；3.目前检查测试，磁盘已经恢复；2.MOUNT 磁盘组报错的解决。3.处理DROP状态的ASM磁盘。
oracle 磁盘组掉了,ASM磁盘组丢失member kfed修复
weixin_35482237的博客
04-02 347
1.报错SQL> alter diskgroup datadg mount;alter diskgroup datadg mount*ERROR at line 1:ORA-15032: not all alterations performedORA-15040: diskgroup is incompleteORA-15042: ASM disk "1" is missing from ...
ORA-15042 故障终极恢复----惜分飞
weixin_34253539的博客
11-20 1310
接到一个朋友恢复请求,19个lun的asm 磁盘组，由于其中一个lun有问题，他们进行了增加一个新lun，删除老lun的方法操作,但是操作一半hang住了(因为坏的lun是底层损坏，无法完成rebalance),然后存储工程师继续修复异常lun，非常幸运异常lun修复好了，但是高兴过了头，直接从存储上删除了新加入的lun(已经rebalance一部分数据...
oracle中15042,ora-15040 diskgroup is incomplete ORA-15042 ASM Disk"2" is missing.
weixin_35728216的博客
04-03 441
hi,unfortunatly our server get rebooted after taht we are try to start ASM instance then we got below errorora-15040 diskgroup is incomplete ORA-15042 ASM Disk"2" is missing.but we are checking from O...
kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rpm
11-27
标题 "kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rpm" 指的是一个特定版本的Oracle Automatic Storage Management (Oracle ASM) 驱动程序，用于Red Hat Enterprise Linux 6 (RHEL 6) 平台上的64位(x86_64)系统。...
kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rar
09-02
这个压缩包"**kmod-oracleasm-2.0.6.rh1-2.el6.x86_64.rar**"包含了适用于Red Hat Enterprise Linux 6.4系统的Oracle ASM内核模块的RPM软件包。 Oracle ASM的主要特点包括： 1. **自动磁盘管理**：ASM能够自动创建...
kmod-oracleasm-2.0.8-8.el7.1.x86_64.rpm
10-15
linux操作系统RHEL7.1或者CentOS7.1安装Oracle RAC时使用ASM磁盘必备依赖包，亲测可用。
kmod-oracleasm-2.0.6.rh1-3.el6.x86_64.rpm和Oracleasmlib、Oracleasm-support
09-04
Oracle ASM (Automatic Storage Management) 是 Oracle 公司提供的一种高效、自动化的磁盘管理解决方案，尤其在Oracle数据库环境中被广泛使用。它简化了存储管理，提供了高性能、高可用性和高可扩展性。Oracleasmlib...
oracleasmlib和oracleasm-support两个依赖包.zip
09-08
在Oracle ASM环境中，Oracle ASMLib (Automatic Storage Management Library) 和 oracleasm-support 包扮演着关键角色。 Oracle ASMLib 是一个专为Oracle ASM设计的设备驱动程序库，它允许ASM直接访问磁盘设备，而...
windows asm磁盘组_ASM磁盘组ORA15042故障处理案例
weixin_33594195的博客
01-31 303
点击上方蓝字 关注我们 何为ASM?ASM是Oracle 10g R2中为了简化Oracle数据库的管理而推出来的一项新功能，这是Oracle自己提供的卷管理器，主要用于替代操作系统所提供的LVM，它不仅支持单实例，同时对RAC的支持也是非常好,使得Oracle RAC运行不在依赖于第三方的存储管理软件。ASM内部结构今天要讲ASM磁盘组ORA-15042恢复案例，将不得不先讲下A...
装与配置 Oracle 11g RAC（17）—— 解决 Oracle ASM 磁盘标签丢失问题
睿思达DBA
07-26 696
装与配置 Oracle 11g RAC（17）—— 解决 Oracle ASM 磁盘标签丢失问题 在启动 Oracle 集群时启动失败。其中节点1可以正常启动，节点2不能启动。 # 节点1 [grid@rac1 ~]$ crs_stat -t Name Type Target State Host ------------------------------------------------------------ ora.BAK.d
【Oracle ASM数据恢复】ORA-15038: disk ‘XXXXXXX’ mismatch on ‘Time Stamp’ with Target Disk Group错误解析
u013260637的专栏
09-17 1860
如果在mount diskgroup时遇到如下错误，则你有必要读一下这篇文章：   SQL> alter diskgroup DATA mount; alter diskgroup DATA mount * ERROR at line 1: ORA-15032: not all alterations performed ORA-15040: diskgroup is incompl
oracle中15042,案例:Oracle报错ORA-15042: ASM disk “N” is missing from group number “M”
weixin_40004502的博客
04-03 496
天萃荷净数据库asm 磁盘组中的LUN被删除，数据库磁盘盘无法mount，报错ORA-15042: ASM disk “N” is missing from group number “M”接到一个朋友恢复请求,19个lun的asm 磁盘组，由于其中一个lun有问题，他们进行了增加一个新lun，删除老lun的方法操作,但是操作一半hang住了(因为坏的lun是底层损坏，无法完成rebalance)...
ASM disk"11" is missing from group number "2"问题分析
mwyu316的博客
04-12 847
有个同事装数据库时，说B机有一个dg是offline状态，在建dg时没有报错。让他lsvg，结果发现B机就看不到这个dg手动mount，发现报了一个错误然后不用disk11就好了，但是还是不知道磁盘问题所在，看了一篇文章写的挺明白，也没敢这么试https://blog.csdn.net/zhengwei125/article/details/50836329...
oracle asm 存储故障,ORACLE 11G RAC ASM磁盘全部丢失后的恢复
weixin_34634720的博客
04-03 830
故障描述(1)存储故障导致ASM磁盘丢失。(2)CRS因为OCR和VOTEDISK的丢失，除了OHAS还联机外，CLUSTERWARE服务都已经停止操作步骤一、恢复OCR和VOTEDISK(1) 在所有RAC节点上停止CRS服务[root@node1 ~]crsctl stop has -f[root@node2 ~]crsctl stop has -f(2) 在一个节点上以NOCRS方式启动CR...
oracle rac ora 15040,Oracle RAC 故障处理(二)(+DATA磁盘组故障)
weixin_42316933的博客
04-05 1158
环境：测试DB:Oracle 11.2.0.4.0OS:Oracle Linux Server release 6.3 on Oracle VM VirtualBoxnode:rac1,rac2instance:cjcdb1,cjcdb2问题二：DATA磁盘组损坏，导致数据库无法启动和使用问题原因： 测试RAC环境进行过多次增加节点、删除节点、删除实例等操作，导致DATA磁盘损坏解决方案：本次案例...
ORA-15032 ORA-15040 ORA-15042的错误处理
weixin_61212661的博客
06-30 385
客户反馈启动rac集群asm磁盘组无法正常挂载。1.在multipath.conf添加新增两块盘至白名单目录位置。查看udev文件及multipath配置文件。通过multipath -ll发现有两块未配置的磁盘信息。与客户确认后客户确定对datadg磁盘组新增过两块磁盘。2.在udev规则文件添加新增两块磁盘的信息。通过在alert查找其他线索。
asm 查看 数据文件 修改 时间_ASM磁盘组ORA15042故障处理案例一：NORMAL磁盘组下失败组离线后ORA15042报错的处理...
weixin_39816946的博客
12-01 273
点击上方蓝字关注我们～我们的文章会在微信公众号“Oracle恢复实录”和博客网站“rescureora.com” 同步更新，欢迎关注收藏，也欢迎大家转载，但是请在文章开始地方标注文章出处，谢谢！今天跟大家分享一个ASM磁盘组损坏的案例，此案例来自于一个网友。由于是保密客户，不能拿到数据，所以这里只是在自己的环境中模拟此现象并给出解决方案。从Oracle 10g中，Oracle推出ASM...
PRCR-1079 : Failed to start resource ora.asm CRS-5017: The resource action "ora.asm start" encountered the
04-03
You may also need to check the disk space and ensure that there is enough space available for the ASM instance to operate. If the issue persists, you may need to recreate the ASM parameter file and ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值