AMDU 從頭部損壞的磁碟中提取檔案
記錄一下
amdu -dis='/dev/sd*' -ba DATAVG ausize=1048576 blksize=4096 -external -extract=DATAVG.260
外部冗餘的需要指定 -external
blksize 是後設資料AU的大小
ba/ddisks Include disks with bad headers
-baddisks: Normally disks with bad disk headers, or that
look like they were never part of a disk group, will not be
scanned. This option forces them to be scanned anyway and to be
considered part of the given diskgroup. This is most useful when
a disk header has been damaged. The disk will still need to have
a valid allocation table to drive the scan unless -fullscan is
used. In any case at least one block in the first two AUs must be
valid so that the disk number can be determined. The options
-ausize and -blksize are required since these values are normally
fetched from the disk header. If the diskgroup uses external
redundancy then -external should be specified. These values will
be compared against any valid disks found in the diskgroup and
they must be the same.
bl/ksize ASM block size for corrupt disks
-blksize: This option must be set when -baddisks is set. It
must be a power of 2. This size is required to scan a disk looking
for metadata, and it is normally read from the disk header. The
value applies to all disks that do not have a valid header. The
value from the disk header will be used if a valid header is
found.
磁碟組的名稱如果都不知道,可以一個磁碟一個磁碟的strings,只需要看前50個塊就OK,找到FILEDIR就找到了磁碟組名
如果沒有以前資料檔案的列表,那麼ASM檔案號可以去嘗試UNLOAD 256號檔案,這個檔案一般是控制檔案
amdu -dis='/dev/sd*' -ba DATAVG ausize=1048576 blksize=4096 -external -extract=DATAVG.260
外部冗餘的需要指定 -external
blksize 是後設資料AU的大小
ba/ddisks Include disks with bad headers
-baddisks
look like they were never part of a disk group, will not be
scanned. This option forces them to be scanned anyway and to be
considered part of the given diskgroup. This is most useful when
a disk header has been damaged. The disk will still need to have
a valid allocation table to drive the scan unless -fullscan is
used. In any case at least one block in the first two AUs must be
valid so that the disk number can be determined. The options
-ausize and -blksize are required since these values are normally
fetched from the disk header. If the diskgroup uses external
redundancy then -external should be specified. These values will
be compared against any valid disks found in the diskgroup and
they must be the same.
bl/ksize ASM block size for corrupt disks
-blksize
must be a power of 2. This size is required to scan a disk looking
for metadata, and it is normally read from the disk header. The
value applies to all disks that do not have a valid header. The
value from the disk header will be used if a valid header is
found.
磁碟組的名稱如果都不知道,可以一個磁碟一個磁碟的strings,只需要看前50個塊就OK,找到FILEDIR就找到了磁碟組名
如果沒有以前資料檔案的列表,那麼ASM檔案號可以去嘗試UNLOAD 256號檔案,這個檔案一般是控制檔案
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/8242091/viewspace-680180/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 11gASM磁碟頭大量損壞?ASM
- 【BBED】 SYSTEM檔案頭損壞的恢復(4)
- RAC磁碟頭損壞問題處理
- system資料檔案頭損壞修復
- 磁碟損壞造成RMAN備份檔案有壞塊的恢復案例
- 磁碟損壞,system及部分資料檔案丟失
- 磁碟損壞導致資料檔案丟失的恢復
- undo 檔案損壞
- ASM磁碟頭資訊損壞和修復(kfed/dd)ASM
- 陣列櫃故障造成控制檔案損壞,資料檔案損壞陣列
- 用oracle amdu 抽取asm磁碟組的資料檔案OracleASM
- 一個控制檔案損壞
- 損壞控制檔案的恢復方法
- 段頭損壞的處理
- undo檔案丟失或損壞
- 資料檔案損壞、丟失
- 單個控制檔案損壞的恢復
- pg 檔案塊損壞的修復措施。
- linux下修復磁碟損壞Linux
- Oracle 控制檔案損壞解決方案Oracle
- 重做日誌檔案損壞測試
- RMAN學習-資料檔案損壞
- SQL Server ldf 檔案損壞恢復SQLServer
- 控制檔案損壞重建實驗(上)
- 控制檔案損壞重建實驗(下)
- 資料檔案丟失損壞的恢復--
- 某個控制檔案損壞的恢復案例
- REDO檔案丟失或者損壞的恢復
- UNDO 表空間檔案損壞的恢復
- 單個控制檔案損壞的解決方法
- 一次控制檔案損壞的恢復
- 【LINUX】Oracle資料庫 linux磁碟頭資料損壞修復LinuxOracle資料庫
- Java解析ELF檔案:使用Java讀取檔案頭部、節區頭部表、程式頭部表Java
- 從配置檔案中提取IP
- System File1 File Header(資料庫System檔案1檔案頭)損壞情況的恢復Header資料庫
- 從ASM磁碟中還原出檔案(二)ASM
- 從ASM磁碟中還原出檔案(一)ASM
- 從ASM磁碟中複製檔案到本地檔案系統ASM