RMAN備份時候檔案壞塊的處理
http://www.itpub.net/showthread.php?threadid=727648&pagenumber=
***
Corrupt block relative dba: 0x0280cab8 (file 10, block 51896)
Fractured block found during datafile copy
Data in bad block -
type: 0 format: 2 rdba: 0x0000cab8
last change scn: 0x0000.00000000 seq: 0x1 flg: 0x05
consistency value in tail: 0x00000000
check value in block header: 0xcdb8, computed block checksum: 0x1
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
1. 開始報錯 /ocfs_data/intel/base_data01.dbf 有壞塊時候 , 根據 file#=10 , block=51896 找到有問題的
table: c_kanban_config_t 表, 重新建立這個table . 結果還是不報同樣的錯誤 .
2. 然後將 base_data01.dbf 從 /ocfs_data/intel 下轉移到 /ocfs_index/intel/ 下. 還是報同樣的錯誤 . 如上 .
3. 可以斷定不是物理磁碟上的壞塊, 而是在 base_data01.dbf 檔案上的壞塊 .
查詢壞塊:
dmdii-node1$dbv file=base_data01.dbf blocksize=8192
DBVERIFY: Release 9.2.0.4.0 - Production on Sat Mar 3 16:17:21 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
DBVERIFY - Verification starting : FILE = base_data01.dbf
Page 51896 is influx - most likely media corrupt
***
Corrupt block relative dba: 0x0280cab8 (file 10, block 51896)
Fractured block found during dbv:
Data in bad block -
type: 0 format: 2 rdba: 0x0000cab8
last change scn: 0x0000.00000000 seq: 0x1 flg: 0x05
consistency value in tail: 0x00000000
check value in block header: 0xcdb8, computed block checksum: 0x1
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
Page 51897 is marked corrupt
***
Corrupt block relative dba: 0x0280cab9 (file 10, block 51897)
Completely zero block found during dbv:
Page 51898 is marked corrupt
***
Corrupt block relative dba: 0x0280caba (file 10, block 51898)
Completely zero block found during dbv:
Page 51899 is marked corrupt
***
Corrupt block relative dba: 0x0280cabb (file 10, block 51899)
Completely zero block found during dbv:
Page 51900 is marked corrupt
***
Corrupt block relative dba: 0x0280cabc (file 10, block 51900)
Completely zero block found during dbv:
Page 51901 is marked corrupt
***
Corrupt block relative dba: 0x0280cabd (file 10, block 51901)
Completely zero block found during dbv:
Page 51902 is marked corrupt
***
Corrupt block relative dba: 0x0280cabe (file 10, block 51902)
Completely zero block found during dbv:
Page 51903 is marked corrupt
***
Corrupt block relative dba: 0x0280cabf (file 10, block 51903)
Completely zero block found during dbv:
Page 51904 is marked corrupt
***
Corrupt block relative dba: 0x0280cac0 (file 10, block 51904)
Completely zero block found during dbv:
Page 51905 is marked corrupt
***
Corrupt block relative dba: 0x0280cac1 (file 10, block 51905)
Completely zero block found during dbv:
Page 51906 is marked corrupt
***
Corrupt block relative dba: 0x0280cac2 (file 10, block 51906)
Completely zero block found during dbv:
Page 51907 is marked corrupt
***
Corrupt block relative dba: 0x0280cac3 (file 10, block 51907)
Completely zero block found during dbv:
Page 51908 is marked corrupt
***
Corrupt block relative dba: 0x0280cac4 (file 10, block 51908)
Completely zero block found during dbv:
Page 51909 is marked corrupt
***
Corrupt block relative dba: 0x0280cac5 (file 10, block 51909)
Completely zero block found during dbv:
Page 51910 is marked corrupt
***
Corrupt block relative dba: 0x0280cac6 (file 10, block 51910)
Completely zero block found during dbv:
Page 51911 is marked corrupt
***
Corrupt block relative dba: 0x0280cac7 (file 10, block 51911)
Completely zero block found during dbv:
Page 51912 is marked corrupt
***
Corrupt block relative dba: 0x0280cac8 (file 10, block 51912)
Completely zero block found during dbv:
Page 51913 is marked corrupt
***
Corrupt block relative dba: 0x0280cac9 (file 10, block 51913)
Completely zero block found during dbv:
Page 51914 is influx - most likely media corrupt
***
Corrupt block relative dba: 0x0280caca (file 10, block 51914)
Fractured block found during dbv:
Data in bad block -
type: 0 format: 0 rdba: 0x00000000
last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
consistency value in tail: 0x00000001
check value in block header: 0x0, block checksum disabled
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
DBVERIFY - Verification complete
Total Pages Examined : 256008
Total Pages Processed (Data) : 15320
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 1
Total Pages Failing (Index): 0
Total Pages Processed (Other): 223
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 240445
Total Pages Marked Corrupt : 19
Total Pages Influx : 2
dmdii-node1$
SELECT tablespace_name, segment_type, owner, segment_name, partition_name
FROM dba_extents WHERE file_id =
-----------------------------------------------------------------
沒有辦法 : 只有使用 maxcorrupt 引數設值rman備份允許略過壞塊 .
------------------------------------------------------------------
file#=10 , 100 表示略過的corrupt塊最大數量 .
RUN {
set maxcorrupt for datafile 10 to 100;
ALLOCATE CHANNEL dmd2 DEVICE TYPE DISK ;
COPY
datafile '/ocfs_data/intel/system01.dbf' to '/backup/ocfs_data/intel/system01.dbf',
datafile '/ocfs_data/intel/undotbs01.dbf' to '/backup/ocfs_data/intel/undotbs01.dbf',
datafile '/ocfs_data/intel/cwmlite01.dbf' to '/backup/ocfs_data/intel/cwmlite01.dbf',
datafile '/ocfs_data/intel/drsys01.dbf' to '/backup/ocfs_data/intel/drsys01.dbf',
datafile '/ocfs_data/intel/indx01.dbf' to '/backup/ocfs_data/intel/indx01.dbf',
datafile '/ocfs_data/intel/tools01.dbf' to '/backup/ocfs_data/intel/tools01.dbf',
datafile '/ocfs_data/intel/users01.dbf' to '/backup/ocfs_data/intel/users01.dbf',
datafile '/ocfs_data/intel/xdb01.dbf' to '/backup/ocfs_data/intel/xdb01.dbf',
datafile '/ocfs_data/intel/undotbs02.dbf' to '/backup/ocfs_data/intel/undotbs02.dbf',
datafile '/ocfs_data/intel/base_data01.dbf' to '/backup/ocfs_data/intel/base_data01.dbf',
datafile '/ocfs_data/intel/base_data02.dbf' to '/backup/ocfs_data/intel/base_data02.dbf',
.....
datafile '/ocfs_index/intel/sn_idx35.dbf' to '/backup/ocfs_index/intel/sn_idx35.dbf',
datafile '/ocfs_data/intel/sn_data28.dbf' to '/backup/ocfs_data/intel/sn_data28.dbf',
datafile '/ocfs_index/intel/wiplog_idx16.dbf' to '/backup/ocfs_index/intel/wiplog_idx16.dbf',
datafile '/ocfs_index/intel/track_index10.dbf' to '/backup/ocfs_index/intel/track_index10.dbf';
RELEASE CHANNEL dmd2 ;
}
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/35489/viewspace-84576/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- rman備份後發現壞塊的處理
- 【RMAN】“壞塊”導致RMAN備份不成功的RMAN處理方法
- Oracle RMAN備份中對壞塊(corrupt block)的處理OracleBloC
- 磁碟損壞造成RMAN備份檔案有壞塊的恢復案例
- Oracle 無備份情況下undo檔案損壞處理Oracle
- ReiserFS檔案系統壞塊的處理(轉)
- Oracle塊損壞恢復(有rman備份)Oracle
- RMAN備份時候記憶體區域的使用及split block處理問題記憶體BloC
- Oracle 11.2.0.4.4 ADG 備庫資料檔案壞塊處理Oracle
- rman備份檔案的格式
- RMAN說,我能備份(5)--RMAN備份歸檔檔案
- RMAN備份檔案格式
- 熱備份與RMAN備份中split block的處理BloC
- RMAN備份恢復典型案例——資料檔案存在壞快
- 非系統資料檔案損壞,rman備份恢復
- RMAN說,我能備份(4)--RMAN備份資料檔案和控制檔案
- rman全庫備份備份歸檔日誌檔案
- 用批處理檔案執行備份
- 檔案系統被破壞時的處理方法(轉)
- 利用RMAN修復資料檔案中的壞塊
- 處理過期的archivelog和rman備份Hive
- Oracle壞塊處理Oracle
- rootvg壞塊處理
- ORACLE 壞塊處理Oracle
- 處理塊損壞
- 請問RMAN備份異機還原,備份之後的歸檔日誌在RMAN中怎麼處理?
- 【備份】RMAN中對控制檔案的幾種備份方法
- 批處理檔備份oracleOracle
- 使用RMAN增量備份處理Dataguard因歸檔丟失造成的gap
- RMAN備份中Create catalog時候 ORA-00955及RMAN-06433,RMAN-06429,ORA-01658處理
- oracle實驗記錄 (恢復,備份-含壞塊資料檔案)Oracle
- Backup And Recovery User's Guide-RMAN備份概念-RMAN何時執行控制檔案自動備份GUIIDE
- 沒有備份的情況下處理undo損壞
- rman備份-(1) 利用備份級恢復資料檔案和控制檔案
- 【RMAN】Oracle中如何備份控制檔案?備份控制檔案的方式有哪幾種?Oracle
- RMAN相容性、控制檔案自動備份、儲存時間、備份策略、備份指令碼(二)指令碼
- Linux檔案系統被破壞時的處理方法(轉)Linux
- rman開始備份歸檔日誌的時候,是不是會自動切換redo?