Exadata磁盘损坏导致磁盘组无法mount恢复(oracle一体机磁盘组异常恢复)---惜分飞

这篇具有很好参考价值的文章主要介绍了Exadata磁盘损坏导致磁盘组无法mount恢复(oracle一体机磁盘组异常恢复)---惜分飞。希望对大家有所帮助。如果存在错误或未考虑完全的地方,请大家不吝赐教,您也可以点击"举报违法"按钮提交疑问。

Oracle Exadata客户,在换盘过程中,cell节点又一块磁盘损坏,导致datac1磁盘组(该磁盘组是normal方式冗余)无法mount

Thu Jul 20 22:01:21 2023

SQL> alter diskgroup datac1 mount force

NOTE: cache registered group DATAC1 number=1 incarn=0x0728ad12

NOTE: cache began mount (first) of group DATAC1 number=1 incarn=0x0728ad12

NOTE: Assigning number (1,35) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_11_dm01celadm03)

NOTE: Assigning number (1,31) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_07_dm01celadm03)

NOTE: Assigning number (1,24) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_00_dm01celadm03)

NOTE: Assigning number (1,25) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_01_dm01celadm03)

NOTE: Assigning number (1,27) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_03_dm01celadm03)

NOTE: Assigning number (1,33) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_09_dm01celadm03)

NOTE: Assigning number (1,30) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_06_dm01celadm03)

NOTE: Assigning number (1,28) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_04_dm01celadm03)

NOTE: Assigning number (1,26) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_02_dm01celadm03)

NOTE: Assigning number (1,1) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_08_dm01celadm03)

NOTE: Assigning number (1,34) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_10_dm01celadm03)

NOTE: Assigning number (1,29) to disk (o/192.168.10.9;192.168.10.10/DATAC1_CD_05_dm01celadm03)

NOTE: Assigning number (1,3) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_07_dm01celadm02)

NOTE: Assigning number (1,4) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_06_dm01celadm02)

NOTE: Assigning number (1,5) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_00_dm01celadm02)

NOTE: Assigning number (1,6) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_10_dm01celadm02)

NOTE: Assigning number (1,7) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_08_dm01celadm02)

NOTE: Assigning number (1,8) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_03_dm01celadm02)

NOTE: Assigning number (1,9) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_11_dm01celadm02)

NOTE: Assigning number (1,10) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_01_dm01celadm02)

NOTE: Assigning number (1,11) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_04_dm01celadm02)

NOTE: Assigning number (1,21) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_05_dm01celadm02)

NOTE: Assigning number (1,43) to disk (o/192.168.10.7;192.168.10.8/DATAC1_CD_02_dm01celadm02)

NOTE: Assigning number (1,36) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_07_dm01celadm01)

NOTE: Assigning number (1,37) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_09_dm01celadm01)

NOTE: Assigning number (1,38) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_11_dm01celadm01)

NOTE: Assigning number (1,0) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_08_dm01celadm01)

NOTE: Assigning number (1,40) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_00_dm01celadm01)

NOTE: Assigning number (1,41) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_03_dm01celadm01)

NOTE: Assigning number (1,42) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_06_dm01celadm01)

NOTE: Assigning number (1,44) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_05_dm01celadm01)

NOTE: Assigning number (1,45) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_01_dm01celadm01)

NOTE: Assigning number (1,46) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_02_dm01celadm01)

NOTE: Assigning number (1,47) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_10_dm01celadm01)

NOTE: Assigning number (1,2) to disk (o/192.168.10.5;192.168.10.6/DATAC1_CD_04_dm01celadm01)

Thu Jul 20 22:01:28 2023

NOTE: GMON heartbeating for grp 1

GMON querying group 1 at 450 for pid 30, osid 171838

NOTE: Assigning number (1,32) to disk ()

NOTE: Assigning number (1,39) to disk ()

GMON querying group 1 at 451 for pid 30, osid 171838

NOTE: cache closing disk 32 of grp 1: (not open)

NOTE: process _user171838_+asm1 (171838)

     initiating offline of disk 39.3915945266 () with mask 0x7e[0x7f] in group 1

NOTE: initiating PST update: grp = 1, dsk = 39/0xe9689532, mask = 0x6a, op = clear

GMON updating disk modes for group 1 at 452 for pid 30, osid 171838

NOTE: cache closing disk 32 of grp 1: (not open)

ERROR: Disk 39 cannot be offlined, since all the disks [39, 32] with mirrored data would be offline.

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

WARNING: Offline for disk  in mode 0x7f failed.

NOTE: cache dismounting (not clean) group 1/0x0728AD12 (DATAC1)

NOTE: messaging CKPT to quiesce pins Unix process pid: 171838, image: oracle@dm01dbadm01.gyzq.cn (TNS V1-V3)

NOTE: dbwr not being msg'd to dismount

NOTE: lgwr not being msg'd to dismount

NOTE: cache dismounted group 1/0x0728AD12 (DATAC1)

NOTE: cache ending mount (fail) of group DATAC1 number=1 incarn=0x0728ad12

NOTE: cache deleting context for group DATAC1 1/0x0728ad12

NOTE: cache closing disk 32 of grp 1: (not open)

GMON dismounting group 1 at 453 for pid 30, osid 171838

NOTE: Disk DATAC1_CD_08_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_08_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_04_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_07_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_06_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_00_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_10_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_08_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_03_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_11_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_01_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_04_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_05_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_00_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_01_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_02_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_03_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_04_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_05_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_06_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_07_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk  in mode 0x1 marked for de-assignment

NOTE: Disk DATAC1_CD_09_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_10_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_11_DM01CELADM03 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_07_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_09_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_11_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk  in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_00_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_03_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_06_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_02_DM01CELADM02 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_05_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_01_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_02_DM01CELADM01 in mode 0x7f marked for de-assignment

NOTE: Disk DATAC1_CD_10_DM01CELADM01 in mode 0x7f marked for de-assignment

ERROR: diskgroup DATAC1 was not mounted

ORA-15032: not all alterations performed

ORA-15040: diskgroup is incomplete

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

ORA-15042: ASM disk "39" is missing from group number "1"

ORA-15042: ASM disk "32" is missing from group number "1"

ERROR: alter diskgroup datac1 mount force

故障原因是由于asm disk 32还已经损坏在换盘过程中(数据没有reblance完成),又损坏了asm disk 39,而这两份磁盘中有数据互为镜像,因此磁盘组无法正常mount起来.

检查cell节点celldisk和griddisk情况,确认底层磁盘损坏
 

Exadata磁盘损坏导致磁盘组无法mount恢复(oracle一体机磁盘组异常恢复)---惜分飞,oracle


对于这种情况,因为normal冗余的两份数据都有部分丢失,无法直接恢复数据,通过底层磁盘级别恢复(参考以前一次的Oracle exadata故障恢复:Oracle Exadata坏盘导致磁盘组无法mount恢复),然后比较顺利恢复数据,实现业务数据0丢失

SQL> alter datac1 mount;

Diskgroup altered.

SQL> alter diskgroup datac1 check all;

Diskgroup altered.

多套库顺利open成功
 

Exadata磁盘损坏导致磁盘组无法mount恢复(oracle一体机磁盘组异常恢复)---惜分飞,oracle


在实际恢复过程中由于客户进行了各种尝试,直接新镜像盘然后插入新盘,强制拉磁盘组drop异常disk操作等,导致第一现场发生一些破坏,增加了恢复难道,但是最终通过各种方法弥补,实现了预期的恢复效果(业务数据0丢失)文章来源地址https://www.toymoban.com/news/detail-612683.html

到了这里,关于Exadata磁盘损坏导致磁盘组无法mount恢复(oracle一体机磁盘组异常恢复)---惜分飞的文章就介绍完了。如果您还想了解更多内容,请在右上角搜索TOY模板网以前的文章或继续浏览下面的相关文章,希望大家以后多多支持TOY模板网!

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处: 如若内容造成侵权/违法违规/事实不符,请点击违法举报进行投诉反馈,一经查实,立即删除!

领支付宝红包 赞助服务器费用

相关文章

  • 损坏的二进制文件会导致“程序太大而无法放入内存”

    不知道你是否做过这样的小实验:将一个可执行文件的头部写入一些无效的数据,或者将一个根本不是可执行文件的大型文件的扩展名改为”.exe”,然后执行它(警告,请记得先保存好工作文件)。 文件不会如预期般那样执行,你会得到一个提示:”程序太大而无法装入到内存

    2024年02月09日
    浏览(48)
  • 服务器数据恢复-EVA存储磁盘故障导致存储崩溃的数据恢复案例

    EVA系列存储是一款以虚拟化存储为实现目的的中高端存储设备。EVA存储中的数据在EVA存储设备工作过程中会不断进行迁移,如果运行的任务比较复杂,EVA存储磁盘负载加重,很容易出现故障的。EVA存储通过大量磁盘的冗余空间和故障后rss冗余磁盘动态迁移来保护存储中的数据

    2024年02月11日
    浏览(48)
  • 服务器数据恢复—服务器进水导致阵列中磁盘同时掉线的数据恢复案例

    服务器数据恢复环境: 数台服务器+数台存储阵列柜,共上百块硬盘,划分了数十组lun。 服务器故障检测: 外部因素导致服务器进水,进水服务器中一组阵列内的所有硬盘同时掉线。 北亚数据恢复工程师到达现场后发现机房内有一台存储柜中的机器都没有开机。和用户方沟

    2024年01月23日
    浏览(51)
  • 【服务器数据恢复】raid离线磁盘上线失败导致分区不识别的数据恢复

    服务器数据恢复环境: HP ProLiant DL某系列服务器,三块SAS硬盘组建raid阵列。 上层系统部署有数据库,数据库存放在D分区,备份存放在E分区。 服务器故障: 磁盘故障导致RAID瘫痪,其中一块硬盘状态灯显示红色。存放数据库文件的D分区无法识别;E分区可识别,但是拷贝备份

    2024年02月06日
    浏览(44)
  • 服务器数据恢复-RAID5多块磁盘离线导致崩溃的数据恢复案例

    服务器数据恢复环境: DELL POWEREDGE某型号服务器中有一组由6块SCSI硬盘组建的RAID5阵列,LINUX REDHAT操作系统,EXT3文件系统,存放图片文件。   服务器故障分析: 服务器raid5阵列中有一块硬盘离线,管理员没有及时发现,直到服务器raid5阵列中的另一块硬盘掉线,raid5阵列瘫痪,

    2024年02月12日
    浏览(65)
  • 【北亚企安数据恢复】RAIDZ多块磁盘离线导致服务器崩溃的数据恢复案例

    服务器数据恢复环境: ORACLE SUN ZFS某型号存储,共40块磁盘组建存储池,其中的36块磁盘分为三组,每组12块,单个组使用ZFS特有的RAIDZ管理所有磁盘,RAIDZ级别为2;另外的4块磁盘作为全局热备。存储池内划分出若干空间映射到服务器使用。 服务器故障: 服务器正常运行过程

    2024年01月18日
    浏览(56)
  • raid5两块磁盘掉线导致阵列崩溃的服务器数据恢复案例

    服务器数据恢复环境: DELL PowerVault系列某型号存储,15块硬盘搭建了一组RAID5磁盘阵列。   服务器故障检测: 存储设备raid5阵列中一块磁盘由于未知原因离线,管理员对该磁盘阵列进行了同步操作。在同步的过程中又有一块磁盘指示灯报警,磁盘离线,磁盘阵列同步失败,

    2024年02月13日
    浏览(60)
  • 服务器数据恢复—raid5热备盘未激活崩溃导致上层oracle数据丢失的数据恢复案例

    服务器数据恢复环境: 某品牌X系列服务器,4块SAS硬盘组建了一组RAID5阵列,还有1块磁盘作为热备盘使用。服务器上层安装的linux操作系统,操作系统上部署了一个基于oracle数据库的OA(oracle已经不再为该OA系统提供后续服务支持)。 服务器故障: raid5中一块磁盘离线,热备盘

    2024年02月05日
    浏览(60)
  • 因磁盘空间不足导致MacBook Pro无法启动(反复重启)的解决过程

    我的电脑是2017版的15寸MacBook Pro,SSD空间512G,因为装了windows和Linux虚拟机,再加上微信、QQ都是吃磁盘大户,剩余空间仅剩11G左右。 最近启动一直很慢,昨天一早干脆反复启动,出现一个多语言版的提示:“电脑因出现问题而重新启动,请按一下按键,或等几秒钟以继续启动

    2024年02月15日
    浏览(65)
  • 华为手机不开机怎么办华为恢复出厂开机激活设备启动不了.提示您的设备芯片已损坏,无法正常使用维修相关服务解决方法

    您的设备芯片已损坏,无法正常使用.请前往华为官方服务门店获取维修相关服务恢复了出厂后,没手机验证进不了系统手机激活锁怎么注销.手机号不用了,华为手机恢复出厂设置,需要华为账号密码,怎么办.教你刷机解锁学会忘记密码后解锁成功开机用.芯片损坏怎么弄好恢复

    2024年02月04日
    浏览(203)

觉得文章有用就打赏一下文章作者

支付宝扫一扫打赏

博客赞助

微信扫一扫打赏

请作者喝杯咖啡吧~博客赞助

支付宝扫一扫领取红包,优惠每天领

二维码1

领取红包

二维码2

领红包