Oracle 11.2.0.4.4 ADG 備庫資料檔案壞塊處理
【 alert 日誌報錯資訊】
Thu Jul 02 01:53:28 2015
RFS[3]: Assigned to RFS process 37758
RFS[3]: Selected log 220 for thread 2 sequence 13279 dbid 2048376234 branch 878583729
Archived Log entry 16066 added for thread 2 sequence 13279 ID 0x7bd065cf dest 1:
Media Recovery Log /oradata/archive/1_16612_878583729.dbf
Media Recovery Log /oradata/archive/2_13278_878583729.dbf
Thu Jul 02 01:53:31 2015
RFS[4]: Assigned to RFS process 37764
RFS[4]: Selected log 201 for thread 1 sequence 16613 dbid 2048376234 branch 878583729
Thu Jul 02 01:53:58 2015
Media Recovery Waiting for thread 1 sequence 16613 (in transit)
Media Recovery of Online Log [Thread=1, Seq=16613]
Recovery of Online Redo Log: Thread 1 Group 201 Seq 16613 Reading mem 0
Mem# 0: /oradata/redo/IRRACD/onlinelog/o1_mf_201_1j-X4kRbS_.log
Thu Jul 02 01:54:24 2015
Hex dump of (file 52, block 720409) in trace file /opt/oradiag/diag/rdbms/irracd/irracd1/trace/irracd1_dbw1_37675.trc
Corrupt block relative dba: 0x0d0afe19 (file 52, block 720409)
Bad header found during preparing block for write
Data in bad block:
type: 67 format: 7 rdba: 0x37223a22
last change scn: 0x0acb.8b347985 seq: 0x1 flg: 0x34
spare1: 0x64 spare2: 0x65 spare3: 0x3434
consistency value in tail: 0x79854301
check value in block header: 0xdf5e
computed block checksum: 0x0
Errors in file /opt/oradiag/diag/rdbms/irracd/irracd1/trace/irracd1_dbw1_37675.trc (incident=1536347):
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
Incident details in: /opt/oradiag/diag/rdbms/irracd/irracd1/incident/incdir_1536347/irracd1_dbw1_37675_i1536347.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Errors in file /opt/oradiag/diag/rdbms/irracd/irracd1/trace/irracd1_dbw1_37675.trc:
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
DBW1 (ospid: 37675): terminating the instance due to error 471
Thu Jul 02 01:54:27 2015
System state dump requested by (instance=1, osid=37675 (DBW1)), summary=[abnormal instance termination].
System State dumped to trace file /opt/oradiag/diag/rdbms/irracd/irracd1/trace/irracd1_diag_37641_20150702015427.trc
Dumping diagnostic data in directory=[cdmp_20150702015427], requested by (instance=1, osid=37675 (DBW1)), summary=[abnormal instance termination].
Instance terminated by DBW1, pid = 37675
【irracd1_dbw1_37675.trc 檔案資訊】
Corrupt block relative dba: 0x0d0afe19 (file 52, block 720409)
Bad header found during preparing block for write
Data in bad block:
type: 67 format: 7 rdba: 0x37223a22
last change scn: 0x0acb.8b347985 seq: 0x1 flg: 0x34
spare1: 0x64 spare2: 0x65 spare3: 0x3434
consistency value in tail: 0x79854301
check value in block header: 0xdf5e
computed block checksum: 0x0
kcra_dump_redo_internal: skipped for critical process
kcbz_try_block_recovery <63, 218824217>: tries=0 max=5 cur=1435773263 last=0
BH (0x9ded71238) file#: 52 rdba: 0x0d0afe19 (52/720409) class: 0 ba: 0x9d3d2c000
set: 110 pool: 3 bsz: 8192 bsi: 0 sflg: 2 pwc: 0,0
dbwrid: 1 obj: 607845 objn: -1 tsn: 63 afn: 52 hint: f
hash: [0x12b5437140,0x12b5437140] lru: [0x9ded714c8,0x9ded71188]
ckptq: [0x9ef3a4c38,0x9ded71098] fileq: [0x9dedb01c8,0x9eecf1ae8] objq: [NULL] objaq: [NULL]
st: MEDIA_RCV md: NULL rsop: 0x12c89eeaf0 tch: 1 le: (nil) rlscn: 0x0acb.8b347985
flags: buffer_dirty being_written only_sequential_access block_written_once
kcra_dump_redo_internal: skipped for critical process
Incident 1536347 created, dump file: /opt/oradiag/diag/rdbms/irracd/irracd1/incident/incdir_1536347/irracd1_dbw1_37675_i1536347.trc
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
error 471 detected in background process
ORA-00600: internal error code, arguments: [kcbzpbuf_1], [4], [1], [], [], [], [], [], [], [], [], []
kjzduptcctx: Notifying DIAG for crash event
----- Abridged Call Stack Trace -----
ksedsts()+465<-kjzdssdmp()+267<-kjzduptcctx()+232<-kjzdicrshnfy()+63<-ksuitm()+5570<-ksbrdp()+3507<-opirip()+623<-opidrv()+603<-sou2o()+103<-opimai_real()+250<-ssthrdmain()+265<-main()+201<-__libc_start_main()+253
----- End of Abridged Call Stack Trace -----
*** 2015-07-02 01:54:27.110
DBW1 (ospid: 37675): terminating the instance due to error 471
ksuitm: waiting up to [5] seconds before killing DIAG(37641)
[oracle@irora01 ~]$
【dbv 檢查結果】
[oracle@irora01 ~]$ dbv file=/orassd/data3/order_dat10.dbf
DBVERIFY: Release 11.2.0.4.0 - Production on Thu Jul 2 09:14:05 2015
Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.
DBVERIFY - Verification starting : FILE = /orassd/data3/order_dat10.dbf
kdrchk: row is marked as both F and P
prow=0x7fdc174fb493 flag=0x2e
Block Checking: DBA = 218824217, Block Type = KTB-managed data block
data header at 0x7fdc174fb064
kdbchk: bad row tab 0, slot 7
Page 720409 failed with check code 6252
DBVERIFY - Verification complete
Total Pages Examined : 2048000
Total Pages Processed (Data) : 2040956
Total Pages Failing (Data) : 1
Total Pages Processed (Index): 388
Total Pages Failing (Index): 0
Total Pages Processed (Other): 6655
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 1
Total Pages Marked Corrupt : 0
Total Pages Influx : 0
Total Pages Encrypted : 0
Highest block SCN : 2335867086 (2763.2335867086)
[oracle@irora01 ~]$
【處理方法】
1, 關閉備庫所有例項。
2, 啟動日誌接收節點資料庫例項到 mount 狀態。
3, 透過以下 RMAN 命令,從主庫備份出現壞塊的資料檔案到備庫。
rman target sys/"xxxxx"@bj_irracdstb auxiliary sys/"xxxx"@sd_irracdstb
run {
allocate channel d1 type disk ;
allocate channel d2 type disk ;
backup as copy reuse
datafile 52 auxiliary format '/orassd/data3/order_dat10.dbf';
}
4, 啟動日誌應用程式,追日誌。
sqlplus 下執行:
5, 追平日誌後,取消日誌應用程式,把資料庫更改到 open 狀態。
sqlplus 下執行:
alter database open;
6,再次開啟日誌應用程式,進行資料同步。
sqlplus 下執行:
【處理方法】
1, 關閉備庫所有例項。
2, 啟動日誌接收節點資料庫例項到 mount 狀態。
3, 透過以下 RMAN 命令,從主庫備份出現壞塊的資料檔案到備庫。
rman target sys/"xxxxx"@bj_irracdstb auxiliary sys/"xxxx"@sd_irracdstb
run {
allocate channel d1 type disk ;
allocate channel d2 type disk ;
backup as copy reuse
datafile 52 auxiliary format '/orassd/data3/order_dat10.dbf';
}
4, 啟動日誌應用程式,追日誌。
sqlplus 下執行:
ALTER DATABASE RECOVER managed standby database using current logfile disconnect;
5, 追平日誌後,取消日誌應用程式,把資料庫更改到 open 狀態。
sqlplus 下執行:
ALTER DATABASE RECOVER managed standby database cancel;
alter database open;
6,再次開啟日誌應用程式,進行資料同步。
sqlplus 下執行:
ALTER DATABASE RECOVER managed standby database using current logfile disconnect;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/66634/viewspace-1743778/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 一次ORACLE資料庫undo壞塊處理Oracle資料庫
- Oracle壞塊處理Oracle
- Oracle資料庫處理壞塊問題常用命令Oracle資料庫
- 如何處理Oracle資料庫中的壞塊問題(轉)Oracle資料庫
- Oracle 無備份情況下undo檔案損壞處理Oracle
- Oracle ADG 備庫新增備庫Oracle
- oracle 普通表空間資料檔案壞塊Oracle
- Oracle RAC+ADG新增資料檔案失敗處理(db_create_file_dest)Oracle
- Oracle資料庫出現ORA-19566 LOB壞塊的處理記錄Oracle資料庫
- oracle uncatalog資料庫備份檔案Oracle資料庫
- Oracle資料庫壞塊典型案例分析Oracle資料庫
- 【資料庫資料恢復】Oracle資料庫檔案出現壞塊報錯的資料恢復案例資料庫資料恢復Oracle
- oracle adg備庫歸檔滿了無法同步Oracle
- 【BLOCK】Oracle壞塊處理命令參考BloCOracle
- 一個簡單易用的資料庫壞塊處理方案資料庫
- Oracle資料庫壞塊典型案例擴充Oracle資料庫
- 控制檔案損壞處理
- Oracle Adg 備庫 ORA-10458 ORA-01196 ORA-01110: ORA-10458 故障處理Oracle
- Oracle DG備庫手動管理新增資料檔案Oracle
- 學習這篇Oracle資料庫檔案壞塊損壞的恢復方法,擴充你的知識面Oracle資料庫
- MySQL資料庫InnoDB壞頁處理修復MySql資料庫
- Oracle 19c adg全庫遷移資料Oracle
- oracle資料庫的配置檔案Oracle資料庫
- 織夢資料庫配置檔案資料庫損壞:嘗試修復資料庫資料庫
- Oracle 之利用BBED修改資料塊SCN----沒有備份資料檔案的資料恢復Oracle資料恢復
- InterBase資料庫檔案損壞的修復方法資料庫
- 【資料庫資料恢復】MongoDB資料庫檔案損壞的資料恢復案例資料庫資料恢復MongoDB
- RMAN備份恢復典型案例——資料檔案存在壞快
- oracle dg庫資料檔案空間不足Oracle
- oracle rac+adg調整redo日誌組導致adg備庫ogg抽取程式abendOracle
- 使用資料流的思想處理檔案
- oracle壞塊(二)Oracle
- oracle 備份資料庫,匯出資料庫Oracle資料庫
- Oracle資料庫中的逐行處理問題NEOracle資料庫
- 「Oracle」Oracle 資料庫備份還原Oracle資料庫
- MySQL資料庫INNODB表損壞修復處理過程分享MySql資料庫
- Dedecms備份的資料檔案位置及備份資料庫的方法資料庫
- 分析Oracle資料庫日誌檔案(三)EPOracle資料庫
- 分析Oracle資料庫日誌檔案(二)DOOracle資料庫