标签云
asm 恢复 asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (100)
- 数据库 (1,597)
- DB2 (22)
- MySQL (70)
- Oracle (1,463)
- Data Guard (49)
- EXADATA (7)
- GoldenGate (21)
- ORA-xxxxx (158)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (13)
- ORACLE 21C (3)
- Oracle ASM (65)
- Oracle Bug (7)
- Oracle RAC (47)
- Oracle 安全 (6)
- Oracle 开发 (27)
- Oracle 监听 (27)
- Oracle备份恢复 (530)
- Oracle安装升级 (84)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (75)
- PostgreSQL (17)
- PostgreSQL恢复 (5)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (36)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (19)
-
最近发表
- Oracle 19c/21c最新patch信息-202404
- PostgreSQL恢复系列:pg_filedump批量处理
- PostgreSQL部分主要字典信息
- PostgreSQL恢复系列:pg_filedump恢复字典构造
- PostgreSQL 16 源码安装
- ORA-00742 ORA-00312 恢复
- 数据库open成功后报ORA-00353 ORA-00354错误引起的一系列问题(本质ntfs文件系统异常)
- ORA-600 ktsiseginfo1故障
- ORA-00600: internal error code, arguments: [16703], [1403], [4] 原因
- 最近遇到几起ORA-600 16703故障(tab$被清空),请引起重视
- ORA-600 2662快速恢复之Patch scn工具
- TNS-12518: TNS:listener could not hand off client connection
- ora.storage无法启动报ORA-12514故障处理
- 断电引起文件scn异常数据库恢复
- ORA-16188: LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
- .[hudsonL@cock.li].mkp勒索加密数据库完美恢复
- 模拟带库实现rman远程备份
- 又一例:ORA-600 kclchkblk_4和2662故障
- Oracle误删除数据文件恢复
- Oracle 19C 备库DML重定向—DML Redirection
月归档:二月 2013
创建控制文件遭遇ORA-600 kccscf_1
数据库版本10.2.0.1创建控制文件出现ORA-00600[kccscf_1]错误
SQL> CREATE CONTROLFILE REUSE DATABASE "ITPLUSDW" RESETLOGS ARCHIVELOG 2 MAXLOGFILES 16 3 MAXLOGMEMBERS 3 4 MAXDATAFILES 100 5 MAXINSTANCES 8 6 MAXLOGHISTORY 292000 7 LOGFILE 8 GROUP 1 '/backup/oracle/oradata/redo01.log' SIZE 50M, 9 GROUP 2 '/backup/oracle/oradata/redo02.log' SIZE 50M, 10 GROUP 3 '/backup/oracle/oradata/redo03.log' SIZE 50M 11 -- STANDBY LOGFILE 12 DATAFILE 13 '/backup/oracle/oradata/system01.dbf', 14 '/backup/oracle/oradata/undotbs01.dbf', 15 '/backup/oracle/oradata/sysaux01.dbf', 16 '/backup/oracle/oradata/users01.dbf', 17 '/backup/oracle/oradata/itplus_data', 18 '/backup/oracle/oradata/invertories_data', 19 '/backup/oracle/oradata/inventories_data01', 20 '/backup/oracle/oradata/itplus_discover', 21 '/backup/oracle/oradata/inventories_data02', 22 '/backup/oracle/oradata/inventories_data03', 23 '/backup/oracle/oradata/inventories_data05', 24 '/backup/oracle/oradata/inventories_data04' 25 CHARACTER SET ZHS16CGB231280 26 ; CREATE CONTROLFILE REUSE DATABASE "ITPLUSDW" RESETLOGS ARCHIVELOG * ERROR at line 1: ORA-01503: CREATE CONTROLFILE failed ORA-00600: internal error code, arguments: [kccscf_1], [9], [292000], [65535],[], [], [], []
alert日志错误
Default Temporary Tablespace will be necessary for a locally managed database in future release Tue Feb 26 15:49:36 2013 Errors in file /backup/oracle/admin/udump/itplustest_ora_25001.trc: ORA-00600: internal error code, arguments: [kccscf_1], [9], [292000], [65535], [], [], [], [] Tue Feb 26 15:49:36 2013 Errors in file /backup/oracle/admin/udump/itplustest_ora_25001.trc: ORA-00600: internal error code, arguments: [kccscf_1], [9], [292000], [65535], [], [], [], [] ORA-1503 signalled during: CREATE CONTROLFILE REUSE DATABASE "ITPLUSDW" NORESETLOGS ARCHIVELOG
查询mos发现Create Control File fails with ORA-600 [kccscf_1] [ID 387210.1],中有描述,该bug在10.2.0.1到11.1.0.6版本中,如果MAXLOGHISTORY超过了65535均有可能出现,在10.2.0.4和11.1.0.6中修复,部分版本有Patch 4877360修复该问题。在不能升级或者没有patch的情况下,解决该问题的思路是设置MAXLOGHISTORY为65535或者更小值,重建控制文件
rman制造坏块,bbed修复坏块
在rman中有隐藏的命令clear,可以标记数据块为corrupt,从而实现数据库坏块试验,本篇blog通过dbv,bbed,table select来验证坏块的出现和修复
创建测试表
SQL> create table t_xifenfei as 2 select object_id,object_name from dba_objects where rownum<10; Table created. SQL> select rowid, 2 dbms_rowid.rowid_relative_fno(rowid) rel_fno, 3 dbms_rowid.rowid_block_number(rowid) block 4 from chf.t_xifenfei; ROWID REL_FNO BLOCK ------------------ ---------- ---------- AAAStAAAEAAAACrAAA 4 171 AAAStAAAEAAAACrAAB 4 171 AAAStAAAEAAAACrAAC 4 171 AAAStAAAEAAAACrAAD 4 171 AAAStAAAEAAAACrAAE 4 171 AAAStAAAEAAAACrAAF 4 171 AAAStAAAEAAAACrAAG 4 171 AAAStAAAEAAAACrAAH 4 171 AAAStAAAEAAAACrAAI 4 171 9 rows selected. SQL> alter system checkpoint; System altered.
dbv验证坏块
[oracle@xifenfei ~]$ dbv file=/u01/oracle/oradata/ora11g/users01.dbf DBVERIFY: Release 11.2.0.3.0 - Production on Sun Jan 20 09:12:16 2013 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. DBVERIFY - Verification starting : FILE = /u01/oracle/oradata/ora11g/users01.dbf DBVERIFY - Verification complete Total Pages Examined : 7680 Total Pages Processed (Data) : 3776 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 167 Total Pages Failing (Index): 0 Total Pages Processed (Other): 744 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 2993 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Total Pages Encrypted : 0 Highest block SCN : 1006717955 (2956.1006717955)
这里创建了t_xifenfei表,数据存储在file 4 block 171中,现在该block一切正常,本试验就是要通过rman来使得该block corrupt,然后通过bbed来修复
bbed查看kcbh
BBED> set block 171 BLOCK# 171 BBED> p kcbh struct kcbh, 20 bytes @0 ub1 type_kcbh @0 0x06 ub1 frmt_kcbh @1 0xa2 ub1 spare1_kcbh @2 0x00 ub1 spare2_kcbh @3 0x00 ub4 rdba_kcbh @4 0x010000ab ub4 bas_kcbh @8 0x3c014bfe ub2 wrp_kcbh @12 0x0b8c ub1 seq_kcbh @14 0x02 ub1 flg_kcbh @15 0x04 (KCBHFCKV) ub2 chkval_kcbh @16 0x6e0c <--重点关注 ub2 spare3_kcbh @18 0x0000
rman标记坏块
RMAN> BLOCKRECOVER DATAFILE 4 block 171 clear; Starting recover at 20-JAN-13 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=18 device type=DISK Finished recover at 20-JAN-13
dbv再次检查坏块
[oracle@xifenfei ~]$ dbv file=/u01/oracle/oradata/ora11g/users01.dbf DBVERIFY: Release 11.2.0.3.0 - Production on Sun Jan 20 09:53:16 2013 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. DBVERIFY - Verification starting : FILE = /u01/oracle/oradata/ora11g/users01.dbf Page 171 is marked corrupt Corrupt block relative dba: 0x010000ab (file 4, block 171) Bad check value found during dbv: Data in bad block: type: 6 format: 2 rdba: 0x010000ab last change scn: 0x0b8c.3c014bfe seq: 0x2 flg: 0x04 spare1: 0x0 spare2: 0x0 spare3: 0x0 consistency value in tail: 0x4bfe0602 check value in block header: 0x6e0c computed block checksum: 0xb5bc DBVERIFY - Verification complete Total Pages Examined : 7680 Total Pages Processed (Data) : 3775 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 167 Total Pages Failing (Index): 0 Total Pages Processed (Other): 744 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 2993 Total Pages Marked Corrupt : 1 Total Pages Influx : 1 Total Pages Encrypted : 0 Highest block SCN : 1006717955 (2956.1006717955)
尝试查询数据
SQL> select count(*) from t_xifenfei; select count(*) from t_xifenfei * ERROR at line 1: ORA-01578: ORACLE data block corrupted (file # 4, block # 171) ORA-01110: data file 4: '/u01/oracle/oradata/ora11g/users01.dbf'
bbed验证坏块
BBED> set block 171 BLOCK# 171 BBED> p kcbh struct kcbh, 20 bytes @0 ub1 type_kcbh @0 0x06 ub1 frmt_kcbh @1 0xa2 ub1 spare1_kcbh @2 0x00 ub1 spare2_kcbh @3 0x00 ub4 rdba_kcbh @4 0x010000ab ub4 bas_kcbh @8 0x3c014bfe ub2 wrp_kcbh @12 0x0b8c ub1 seq_kcbh @14 0x02 ub1 flg_kcbh @15 0x04 (KCBHFCKV) ub2 chkval_kcbh @16 0x6e0c <--注意该值未变化 ub2 spare3_kcbh @18 0x0000 BBED> verify DBVERIFY - Verification starting FILE = /u01/oracle/oradata/ora11g/users01.dbf BLOCK = 171 Block 171 is corrupt Corrupt block relative dba: 0x010000ab (file 0, block 171) Bad check value found during verification Data in bad block: type: 6 format: 2 rdba: 0x010000ab last change scn: 0x0b8c.3c014bfe seq: 0x2 flg: 0x04 spare1: 0x0 spare2: 0x0 spare3: 0x0 consistency value in tail: 0x4bfe0602 check value in block header: 0x6e0c computed block checksum: 0xb5bc DBVERIFY - Verification complete Total Blocks Examined : 1 Total Blocks Processed (Data) : 0 Total Blocks Failing (Data) : 0 Total Blocks Processed (Index): 0 Total Blocks Failing (Index): 0 Total Blocks Empty : 0 Total Blocks Marked Corrupt : 1 Total Blocks Influx : 0 Message 531 not found; product=RDBMS; facility=BBED
这里通过dbv,bbed,select table都证明rman能够标记block为Corrupt.
这里需要分析:block已经被标记,那证明该块肯定有修改,也就是说chkval_kcbh一定要变化,但是这里没有变化,证明该处异常
bbed修复rman生成坏块
BBED> sum apply Warning: contents of previous BIFILE will be lost. Proceed? (Y/N) y Check value for File 0, Block 171: current = 0xdbb0, required = 0xdbb0 BBED> verify DBVERIFY - Verification starting FILE = /u01/oracle/oradata/ora11g/users01.dbf BLOCK = 171 DBVERIFY - Verification complete Total Blocks Examined : 1 Total Blocks Processed (Data) : 1 Total Blocks Failing (Data) : 0 Total Blocks Processed (Index): 0 Total Blocks Failing (Index): 0 Total Blocks Empty : 0 Total Blocks Marked Corrupt : 0 Total Blocks Influx : 0 Message 531 not found; product=RDBMS; facility=BBED
bbed测试坏块已经修复
dbv验证坏块
[oracle@xifenfei ~]$ dbv file=/u01/oracle/oradata/ora11g/users01.dbf DBVERIFY: Release 11.2.0.3.0 - Production on Sun Jan 20 10:01:46 2013 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. DBVERIFY - Verification starting : FILE = /u01/oracle/oradata/ora11g/users01.dbf DBVERIFY - Verification complete Total Pages Examined : 7680 Total Pages Processed (Data) : 3776 Total Pages Failing (Data) : 0 Total Pages Processed (Index): 167 Total Pages Failing (Index): 0 Total Pages Processed (Other): 744 Total Pages Processed (Seg) : 0 Total Pages Failing (Seg) : 0 Total Pages Empty : 2993 Total Pages Marked Corrupt : 0 Total Pages Influx : 0 Total Pages Encrypted : 0 Highest block SCN : 1006717955 (2956.1006717955)
dbv测试坏块也被修复
查询表验证
SQL> select count(*) from t_xifenfei; COUNT(*) ---------- 9
数据也可以正常查询,证明rman的坏块问题通过bbed解决
总结说明
1.我们可以通过rman的clear命令来标记坏块(BLOCKRECOVER DATAFILE file# BLOCK block1#, block2#, block3#… CLEAR ;)
2.我们可以通过bbed的sum apply命令来修复该类型坏块
ORA-600 kghstack_free2异常恢复
今天接触一案例ORA-00600[kghstack_free2],恢复起来很简单,顺便记录下,供其他人遇到类似情况参考.
Wed Feb 20 15:05:04 2013 SMON: enabling cache recovery Wed Feb 20 15:05:05 2013 Successfully onlined Undo Tablespace 1. Wed Feb 20 15:05:05 2013 SMON: enabling tx recovery Wed Feb 20 15:05:06 2013 Errors in file f:\oracle\product\10.2.0\admin\cksoltp\bdump\cksoltp_smon_3556.trc: ORA-00600: internal error code, arguments: [kghstack_free2], [], [], [], [], [], [], [] Wed Feb 20 15:05:06 2013 Database Characterset is AL32UTF8 replication_dependency_tracking turned off (no async multimaster replication found) Wed Feb 20 15:05:08 2013 Errors in file f:\oracle\product\10.2.0\admin\cksoltp\bdump\cksoltp_smon_3556.trc: ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [_kghstack_err+101] [PC:0x603CC77F] [ADDR:0x59004E04] [UNABLE_TO_READ] [] ORA-00600: internal error code, arguments: [kghstack_free2], [], [], [], [], [], [], [] Starting background process QMNC QMNC started with pid=18, OS id=3504 Wed Feb 20 15:05:13 2013 Errors in file f:\oracle\product\10.2.0\admin\cksoltp\bdump\cksoltp_pmon_4064.trc: ORA-00474: SMON process terminated with error
这个错误很明显是因为smon在回滚事务的时候,遇到异常从而出现ORA-00600[kghstack_free2]错误,使得数据库不能被正常open,通过分析trace文件发现回滚段36中有事务未提交,需要回滚,针对这样的数据库恢复方法很简单:1.屏蔽事务回滚,2.屏蔽回滚段强制offline等
1) EVENT=”10513 trace name context forever”
2)_offline_rollback_segments= _SYSSMU36$
数据库启动后,通过分析trace文件,找出来异常对象,然后重建该对象,除掉event/_offline_rollback_segments即可