标签云
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 2131 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)
- 操作系统 (102)
- 数据库 (1,671)
- DB2 (22)
- MySQL (73)
- Oracle (1,533)
- Data Guard (52)
- EXADATA (8)
- GoldenGate (21)
- ORA-xxxxx (159)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (14)
- ORACLE 21C (3)
- Oracle 23ai (7)
- Oracle ASM (65)
- Oracle Bug (8)
- Oracle RAC (52)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (28)
- Oracle备份恢复 (560)
- Oracle安装升级 (92)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (78)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (37)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (20)
-
最近发表
- Kylin Linux 安装19c
- ORA-600 krse_arc_complete.4
- Oracle 19c 202410补丁(RUs+OJVM)
- ntfs MFT损坏(ntfs文件系统故障)导致oracle异常恢复
- .mkp扩展名oracle数据文件加密恢复
- 清空redo,导致ORA-27048: skgfifi: file header information is invalid
- A_H_README_TO_RECOVER勒索恢复
- 通过alert日志分析客户自行对一个数据库恢复的来龙去脉和点评
- ORA-12514: TNS: 监听进程不能解析在连接描述符中给出的SERVICE_NAME
- ORA-01092 ORA-00604 ORA-01558故障处理
- ORA-65088: database open should be retried
- Oracle 19c异常恢复—ORA-01209/ORA-65088
- ORA-600 16703故障再现
- 数据库启动报ORA-27102 OSD-00026 O/S-Error: (OS 1455)
- .[metro777@cock.li].Elbie勒索病毒加密数据库恢复
- 应用连接错误,初始化mysql数据库恢复
- RAC默认服务配置优先节点
- Oracle 19c RAC 替换私网操作
- 监听报TNS-12541 TNS-12560 TNS-00511错误
- drop tablespace xxx including contents恢复
标签归档:kcbz_check_objd_typ_1
ORA-600 kcbz_check_objd_typ_1 处理
客户数据库异常(ORA-600 kcbz_check_objd_typ_1),让我们远程给分析处理
ORA-600 kcbz_check_objd_typ_1异常
Mon Aug 8 12:19:28 2016 Completed: ALTER DATABASE OPEN Mon Aug 8 12:19:29 2016 db_recovery_file_dest_size of 20480 MB is 0.00% used. This is a user-specified limit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlying filesystem or ASM diskgroup. Mon Aug 8 12:19:33 2016 Errors in file /home/oracle/admin/RT/bdump/rt_smon_1514.trc: ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_1], [0], [0], [1], [], [], [], [] Mon Aug 8 12:20:21 2016 Shutting down archive processes Mon Aug 8 12:20:26 2016 ARCH shutting down ARC3: Archival stopped Mon Aug 8 13:12:25 2016 Thread 1 advanced to log sequence 13804 Current log# 3 seq# 13804 mem# 0: /home/oracle/product/10.2.0/oradata/RT/redo03a.log Mon Aug 8 14:01:37 2016 Thread 1 advanced to log sequence 13805 Current log# 2 seq# 13805 mem# 0: /home/oracle/product/10.2.0/oradata/RT/redo02a.log Mon Aug 8 14:20:51 2016 Errors in file /home/oracle/admin/RT/bdump/rt_smon_1514.trc: ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_1], [0], [0], [1], [], [], [], [] Mon Aug 8 15:54:47 2016 Thread 1 advanced to log sequence 13808 Current log# 2 seq# 13808 mem# 0: /home/oracle/product/10.2.0/oradata/RT/redo02a.log Mon Aug 8 16:21:48 2016 Errors in file /home/oracle/admin/RT/bdump/rt_smon_1514.trc: ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_1], [0], [0], [1], [], [], [], [] Mon Aug 8 16:22:05 2016 Errors in file /home/oracle/admin/RT/bdump/rt_pmon_1500.trc: ORA-00474: SMON process terminated with error
这里比较明显,数据库报大量ORA-600 kcbz_check_objd_typ_1错误之后,然后smon进程终止,实例crash.
smon trace文件
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production With the Partitioning, OLAP and Data Mining options ORACLE_HOME = /home/oracle/product/10.2.0/db_1 System name: SunOS Node name: st104 Release: 5.10 Version: Generic_141445-09 Machine: i86pc Instance name: RT Redo thread mounted by this instance: 1 Oracle process number: 12 Unix process pid: 1514, image: oracle@st104 (SMON) *** 2016-08-08 12:19:26.868 *** SERVICE NAME:() 2016-08-08 12:19:26.868 *** SESSION ID:(383.1) 2016-08-08 12:19:26.868 Dead transaction 0x003d.002.0000f964 recovered by SMON Dead transaction 0x0041.017.00004d55 recovered by SMON Dead transaction 0x0047.002.0000180c recovered by SMON Dead transaction 0x004c.01c.00001b57 recovered by SMON *** SESSION ID:(383.1) 2016-08-08 12:19:27.470 DATA seg.obj=0, on-disk obj=925949, dsflg=0, dsobj=923715, cls=4 Formatted dump of block: buffer tsn: 4 rdba: 0x0100336b (4/13163) scn: 0x09c6.b2c7f7a2 seq: 0x02 flg: 0x04 tail: 0xf7a20602 frmt: 0x02 chkval: 0x649b type: 0x06=trans data Hex dump of block: st=0, typ_found=1 *** SESSION ID:(383.1) 2016-08-08 12:19:34.244 DATA seg.obj=0, on-disk obj=925950, dsflg=0, dsobj=923671, cls=4 Formatted dump of block: buffer tsn: 4 rdba: 0x01003343 (4/13123) scn: 0x09c6.b2c7f7dc seq: 0x02 flg: 0x04 tail: 0xf7dc0602 frmt: 0x02 chkval: 0x8013 type: 0x06=trans data Hex dump of block: st=0, typ_found=1 *** SESSION ID:(383.1) 2016-08-08 12:19:35.197 DATA seg.obj=0, on-disk obj=925941, dsflg=0, dsobj=923657, cls=4 Formatted dump of block: buffer tsn: 7 rdba: 0x01c03d53 (7/15699) scn: 0x09c6.b2c7f570 seq: 0x02 flg: 0x04 tail: 0xf5700602 frmt: 0x02 chkval: 0xe5c5 type: 0x06=trans data Hex dump of block: st=0, typ_found=1 *** SESSION ID:(383.1) 2016-08-08 12:19:38.965 DATA seg.obj=0, on-disk obj=925948, dsflg=0, dsobj=923656, cls=4 Formatted dump of block: buffer tsn: 7 rdba: 0x01c03a6b (7/14955) scn: 0x09c6.b2c7f745 seq: 0x02 flg: 0x04 tail: 0xf7450602 frmt: 0x02 chkval: 0x58c5 type: 0x06=trans data Hex dump of block: st=0, typ_found=1
这里可以看出来有block中的obj和dataobj不匹配.
查询seg$.type=3
type=3为临时对象,由于异常原因导致smon在清理temp对象无法正常完成,从而使得smon终止,实例crash.
SQL> select file#, block#, ts# from seg$ where type# = 3; FILE# BLOCK# TS# ---------- ---------- ---------- 4 13163 4 4 13123 4 7 15699 7 7 14955 7
ORA-600 kcbz_check_objd_typ_1处理方法
1) Check tablespace bitmap SQL> oradebug setmypid SQL> exec dbms_space_admin.tablespace_verify('&TBSP_NAME') SQL> oradebug tracefile_name or if the tablespace involved is an ASSM tablespace: SQL> oradebug setmypid SQL> exec dbms_space_admin.assm_tablespace_verify ('&TBSP_NAME',dbms_space_admin.TS_VERIFY_BITMAPS) SQL> oradebug tracefile_name I am expecting to fail 2) Corrupt these temp segments SQL> exec dbms_space_admin.segment_corrupt('&TBSP_NAME', &FILE#, &BLOCK#) 3) Drop them SQL> exec dbms_space_admin.segment_drop_corrupt('&TBSP_NAME', &FILE#, &BLOCK#) 4) Rebuild tablespace bitmap exec DBMS_SPACE_ADMIN.TABLESPACE_REBUILD_BITMAPS('&TBSP_NAME') 5) Verify the tablespace again SQL> oradebug setmypid SQL> exec dbms_space_admin.tablespace_verify('&TBSP_NAME') SQL> oradebug tracefile_name or if the tablespace involved is an ASSM tablespace: SQL> oradebug setmypid SQL> exec dbms_space_admin.assm_tablespace_verify('&TBSP_NAME',dbms_space_admin.TS_VERIFY_BITMAPS) SQL> oradebug tracefile_name