国产 无码 综合区,色欲AV无码国产永久播放,无码天堂亚洲国产AV,国产日韩欧美女同一区二区

Exadata磁盤損壞導致磁盤組無法mount恢復(oracle一體機磁盤組異常恢復)---惜分飛

這篇具有很好參考價值的文章主要介紹了Exadata磁盤損壞導致磁盤組無法mount恢復(oracle一體機磁盤組異常恢復)---惜分飛。希望對大家有所幫助。如果存在錯誤或未考慮完全的地方,請大家不吝賜教,您也可以點擊"舉報違法"按鈕提交疑問。

Oracle Exadata客戶,在換盤過程中,cell節(jié)點又一塊磁盤損壞,導致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還已經(jīng)損壞在換盤過程中(數(shù)據(jù)沒有reblance完成),又損壞了asm disk 39,而這兩份磁盤中有數(shù)據(jù)互為鏡像,因此磁盤組無法正常mount起來.

檢查cell節(jié)點celldisk和griddisk情況,確認底層磁盤損壞
?

Exadata磁盤損壞導致磁盤組無法mount恢復(oracle一體機磁盤組異常恢復)---惜分飛,oracle


對于這種情況,因為normal冗余的兩份數(shù)據(jù)都有部分丟失,無法直接恢復數(shù)據(jù),通過底層磁盤級別恢復(參考以前一次的Oracle exadata故障恢復:Oracle Exadata壞盤導致磁盤組無法mount恢復),然后比較順利恢復數(shù)據(jù),實現(xiàn)業(yè)務數(shù)據(jù)0丟失

SQL> alter datac1 mount;

Diskgroup altered.

SQL> alter diskgroup datac1 check all;

Diskgroup altered.

多套庫順利open成功
?

Exadata磁盤損壞導致磁盤組無法mount恢復(oracle一體機磁盤組異?;謴停?--惜分飛,oracle


在實際恢復過程中由于客戶進行了各種嘗試,直接新鏡像盤然后插入新盤,強制拉磁盤組drop異常disk操作等,導致第一現(xiàn)場發(fā)生一些破壞,增加了恢復難道,但是最終通過各種方法彌補,實現(xiàn)了預期的恢復效果(業(yè)務數(shù)據(jù)0丟失)文章來源地址http://www.zghlxwxcb.cn/news/detail-612683.html

到了這里,關于Exadata磁盤損壞導致磁盤組無法mount恢復(oracle一體機磁盤組異?;謴停?--惜分飛的文章就介紹完了。如果您還想了解更多內容,請在右上角搜索TOY模板網(wǎng)以前的文章或繼續(xù)瀏覽下面的相關文章,希望大家以后多多支持TOY模板網(wǎng)!

本文來自互聯(lián)網(wǎng)用戶投稿,該文觀點僅代表作者本人,不代表本站立場。本站僅提供信息存儲空間服務,不擁有所有權,不承擔相關法律責任。如若轉載,請注明出處: 如若內容造成侵權/違法違規(guī)/事實不符,請點擊違法舉報進行投訴反饋,一經(jīng)查實,立即刪除!

領支付寶紅包贊助服務器費用

相關文章

  • 損壞的二進制文件會導致“程序太大而無法放入內存”

    損壞的二進制文件會導致“程序太大而無法放入內存”

    不知道你是否做過這樣的小實驗:將一個可執(zhí)行文件的頭部寫入一些無效的數(shù)據(jù),或者將一個根本不是可執(zhí)行文件的大型文件的擴展名改為”.exe”,然后執(zhí)行它(警告,請記得先保存好工作文件)。 文件不會如預期般那樣執(zhí)行,你會得到一個提示:”程序太大而無法裝入到內存

    2024年02月09日
    瀏覽(22)
  • 服務器數(shù)據(jù)恢復-EVA存儲磁盤故障導致存儲崩潰的數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復-EVA存儲磁盤故障導致存儲崩潰的數(shù)據(jù)恢復案例

    EVA系列存儲是一款以虛擬化存儲為實現(xiàn)目的的中高端存儲設備。EVA存儲中的數(shù)據(jù)在EVA存儲設備工作過程中會不斷進行遷移,如果運行的任務比較復雜,EVA存儲磁盤負載加重,很容易出現(xiàn)故障的。EVA存儲通過大量磁盤的冗余空間和故障后rss冗余磁盤動態(tài)遷移來保護存儲中的數(shù)據(jù)

    2024年02月11日
    瀏覽(21)
  • 服務器數(shù)據(jù)恢復—服務器進水導致陣列中磁盤同時掉線的數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復—服務器進水導致陣列中磁盤同時掉線的數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復環(huán)境: 數(shù)臺服務器+數(shù)臺存儲陣列柜,共上百塊硬盤,劃分了數(shù)十組lun。 服務器故障檢測: 外部因素導致服務器進水,進水服務器中一組陣列內的所有硬盤同時掉線。 北亞數(shù)據(jù)恢復工程師到達現(xiàn)場后發(fā)現(xiàn)機房內有一臺存儲柜中的機器都沒有開機。和用戶方溝

    2024年01月23日
    瀏覽(21)
  • 【服務器數(shù)據(jù)恢復】raid離線磁盤上線失敗導致分區(qū)不識別的數(shù)據(jù)恢復

    【服務器數(shù)據(jù)恢復】raid離線磁盤上線失敗導致分區(qū)不識別的數(shù)據(jù)恢復

    服務器數(shù)據(jù)恢復環(huán)境: HP ProLiant DL某系列服務器,三塊SAS硬盤組建raid陣列。 上層系統(tǒng)部署有數(shù)據(jù)庫,數(shù)據(jù)庫存放在D分區(qū),備份存放在E分區(qū)。 服務器故障: 磁盤故障導致RAID癱瘓,其中一塊硬盤狀態(tài)燈顯示紅色。存放數(shù)據(jù)庫文件的D分區(qū)無法識別;E分區(qū)可識別,但是拷貝備份

    2024年02月06日
    瀏覽(27)
  • 服務器數(shù)據(jù)恢復-RAID5多塊磁盤離線導致崩潰的數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復-RAID5多塊磁盤離線導致崩潰的數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復環(huán)境: DELL POWEREDGE某型號服務器中有一組由6塊SCSI硬盤組建的RAID5陣列,LINUX REDHAT操作系統(tǒng),EXT3文件系統(tǒng),存放圖片文件。 ? 服務器故障分析: 服務器raid5陣列中有一塊硬盤離線,管理員沒有及時發(fā)現(xiàn),直到服務器raid5陣列中的另一塊硬盤掉線,raid5陣列癱瘓,

    2024年02月12日
    瀏覽(31)
  • 【北亞企安數(shù)據(jù)恢復】RAIDZ多塊磁盤離線導致服務器崩潰的數(shù)據(jù)恢復案例

    【北亞企安數(shù)據(jù)恢復】RAIDZ多塊磁盤離線導致服務器崩潰的數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復環(huán)境: ORACLE SUN ZFS某型號存儲,共40塊磁盤組建存儲池,其中的36塊磁盤分為三組,每組12塊,單個組使用ZFS特有的RAIDZ管理所有磁盤,RAIDZ級別為2;另外的4塊磁盤作為全局熱備。存儲池內劃分出若干空間映射到服務器使用。 服務器故障: 服務器正常運行過程

    2024年01月18日
    瀏覽(24)
  • raid5兩塊磁盤掉線導致陣列崩潰的服務器數(shù)據(jù)恢復案例

    raid5兩塊磁盤掉線導致陣列崩潰的服務器數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復環(huán)境: DELL PowerVault系列某型號存儲,15塊硬盤搭建了一組RAID5磁盤陣列。 ? 服務器故障檢測: 存儲設備raid5陣列中一塊磁盤由于未知原因離線,管理員對該磁盤陣列進行了同步操作。在同步的過程中又有一塊磁盤指示燈報警,磁盤離線,磁盤陣列同步失敗,

    2024年02月13日
    瀏覽(27)
  • 服務器數(shù)據(jù)恢復—raid5熱備盤未激活崩潰導致上層oracle數(shù)據(jù)丟失的數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復—raid5熱備盤未激活崩潰導致上層oracle數(shù)據(jù)丟失的數(shù)據(jù)恢復案例

    服務器數(shù)據(jù)恢復環(huán)境: 某品牌X系列服務器,4塊SAS硬盤組建了一組RAID5陣列,還有1塊磁盤作為熱備盤使用。服務器上層安裝的linux操作系統(tǒng),操作系統(tǒng)上部署了一個基于oracle數(shù)據(jù)庫的OA(oracle已經(jīng)不再為該OA系統(tǒng)提供后續(xù)服務支持)。 服務器故障: raid5中一塊磁盤離線,熱備盤

    2024年02月05日
    瀏覽(25)
  • 因磁盤空間不足導致MacBook Pro無法啟動(反復重啟)的解決過程

    我的電腦是2017版的15寸MacBook Pro,SSD空間512G,因為裝了windows和Linux虛擬機,再加上微信、QQ都是吃磁盤大戶,剩余空間僅剩11G左右。 最近啟動一直很慢,昨天一早干脆反復啟動,出現(xiàn)一個多語言版的提示:“電腦因出現(xiàn)問題而重新啟動,請按一下按鍵,或等幾秒鐘以繼續(xù)啟動

    2024年02月15日
    瀏覽(30)
  • 華為手機不開機怎么辦華為恢復出廠開機激活設備啟動不了.提示您的設備芯片已損壞,無法正常使用維修相關服務解決方法

    華為手機不開機怎么辦華為恢復出廠開機激活設備啟動不了.提示您的設備芯片已損壞,無法正常使用維修相關服務解決方法

    您的設備芯片已損壞,無法正常使用.請前往華為官方服務門店獲取維修相關服務恢復了出廠后,沒手機驗證進不了系統(tǒng)手機激活鎖怎么注銷.手機號不用了,華為手機恢復出廠設置,需要華為賬號密碼,怎么辦.教你刷機解鎖學會忘記密碼后解鎖成功開機用.芯片損壞怎么弄好恢復

    2024年02月04日
    瀏覽(31)

覺得文章有用就打賞一下文章作者

支付寶掃一掃打賞

博客贊助

微信掃一掃打賞

請作者喝杯咖啡吧~博客贊助

支付寶掃一掃領取紅包,優(yōu)惠每天領

二維碼1

領取紅包

二維碼2

領紅包