ora-00600

Trace file /opt/oracle/app/oracle/diag/rdbms/suseora/suseora2/trace/suseora2_ora_36386.trc

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP,

Data Mining and Real Application Testing options

ORACLE_HOME = /opt/oracle/app/oracle/product/11.2.0/db

System name:    Linux

Node name:      usdprac2

Release:        2.6.32.12-0.7-default

Version:        #1 SMP 2010-05-20 11:14:20 +0200

Machine:        x86_64

Instance name: suseora2

Redo thread mounted by this instance: 2

Oracle process number: 299

Unix process pid: 36386, image: [email protected]

*** 2017-05-08 15:39:49.842

*** SESSION ID:(2080.60679) 2017-05-08 15:39:49.842

*** CLIENT ID:() 2017-05-08 15:39:49.842

*** SERVICE NAME:(suseora) 2017-05-08 15:39:49.842

*** MODULE NAME:(JDBC Thin Client) 2017-05-08 15:39:49.842

*** ACTION NAME:() 2017-05-08 15:39:49.842

*** SESSION ID:(2080.60679) 2017-05-08 15:39:49.842

OBJD MISMATCH typ=35, seg.obj=-2, diskobj=8677570, dsflg=0, dsobj=489719, tid=489719, cls=4

DDE: Problem Key ‘ORA 600 [ktecgsc:kcbz_objdchk]‘ was flood controlled (0x2) (incident: 227593)

ORA-00600: 内部错误代码, 参数: [ktecgsc:kcbz_objdchk], [0], [0], [1], [], [], [], [], [], [], [], []

Input data (nil), 0, 0

Formatted dump of block:

buffer tsn: 7 rdba: 0x0826fc91 (32/2555025)

scn: 0x00a2.032d48c7 seq: 0x02 flg: 0x04 tail: 0x48c72302

frmt: 0x02 chkval: 0xc05e type: 0x23=PAGETABLE SEGMENT HEADER

Hex dump of block: st=0, typ_found=1

查询:

1.查询相关段信息

col owner format a10

col object_name format a30

select object_id, data_object_id, owner, object_name, object_type from dba_objects where data_object_id in (8677570, 489718) or object_id in (8677570, 489718);

2.查询段详细信息

select * from seg$ where file#=32 and block#=2555025;

3.查询相关数据文件

col name format a30

select name from v$datafile where file#=32;

4.查询表空间信息

select * from v$tablespace where ts#=7;

5.查询相关区信息

select owner,segment_name,partition_name,segment_type,block_id from dba_extents where relative_fno=32 and 2555025 between block_id and block_id+blocks;

select owner,segment_name,partition_name,segment_type,block_id from dba_extents where block_id=;

原因:

经过MOS查询分析,该错误触发BUG:19689979 。

该BUG是由于truncate或者drop一个正在被访问的表分区导致。

触发该BUG的对象为:

[email protected]> select OWNER,SEGMENT_NAME,PARTITION_NAME,SEGMENT_TYPE,BLOCK_ID from DBA_EXTENTS where RELATIVE_FNO=9 and 424849 between BLOCK_ID and BLOCK_ID+BLOCKS;
       
OWNER                          SEGMENT_NAME                                                                      PARTITION_NAME                 SEGMENT_TYPE         BLOCK_ID
------------------------------ --------------------------------------------------------------------------------- ------------------------------ ------------------ ----------
USDPCENTER                     T_PERSONALLIB                                                                     P42                            TABLE PARTITION        424832

解决方案:

1.当出现问题时flush共享池。

2.修改隐含参数_part_access_version_by_number为false。(RAC需要将各个节点同时重启以修改该参数)

目前已经将flush共享池。flush之后没有发现该报错。

http://t.askmaclean.com/thread-3747-1-1.html

时间: 2024-10-16 09:03:41

ora-00600的相关文章

ora 00600 [kcratr_nab_less_than_odr] [4194]错误

业务场景:公司电缆被挖断,突然断电导致的宕机. [[email protected] ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.1.0 Production on Mon Apr 17 11:09:59 2017 Copyright (c) 1982, 2009, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release

Oracle 通过ADR工具 收集ORA-600错误信息

 问题描述: 2014-06-10 在点检数据库预警文件时,出现Ora -00600 错误,并且Rman L1 备份失败,查询相关资料,得知是Bug:9835218.于是,提SR寻求Oracle 官方技术支持. Oracle回复如下: Your Service Request has been submitted as anORA-600/ORA-7445 issue based on the problem type you chose when logging the SR. Additio

[Oracle]如何获得出现故障时,客户端的详细连接信息

客户坚持说 只是在 每天早上5点才运行下面的语句: select / * + FULL (TAB001_TT01) * / 'TAB001_TT01', count (*) from u01.TAB001_TT01 group by 'TAB001_TT01' 但是根据 Incident 文件的记载,发生时间是在 2017-09-26 10: 44: 50.166 , 客户怀疑 Oracle的数据库出现了其他的问题. 这样调查就跑偏方向了. (因为总所周知的原因,修改了敏感信息) 从下面这句“M

[Oracle]ORA-600[kdBlkCheckError]LOB坏块处理

客户环境报如下错误: ORA - 00600: Internal error code, arguments: [kdBlkCheckError], [2], [10388], [63068], [], [], [], [], [], [], [], [] alert log 中有这样的信息: Thu Sep 07 19:14:00 2017Corrupt Block Found        CONT = 0, TSN = 1, TSNAME = SYSAUX        RFN = 2,

讨厌麻烦的ora 01722无效数字

webservice开发过程中,数据库由原来的oracle改为现在的sql server.然后重新调试,结果报出ora 01722无效数字的错误. 由于连接oracle数据库的时候并没有问题,所以一开始我以为是数据库不同,导致部分数据类型差异,(但又觉得有点离谱,切换数据库,不至于会导致这种错误吧) 经过排查,总结得出如下: 1.对于两个类型不匹配(一个数字类型,一个非数字类型,同下)的值进行赋值操作;2.两个类型不匹配的值进行比较操作(例如,"=");3.to_number函数中的值

ORACLE RAC 下非缺省端口监听配置(listener.ora tnsnames.ora)

不论是单实例还是RAC,对于非缺省端口下(1521)的监听器,pmon进程不会将service/instance注册到监听器,即不会实现动态注册.与单实例相同,RAC非缺省端口的监听器也是通过设置参数local_listener来达到目的.除此之外,还可以对实例进行远程注册,以达到负载均衡的目的.这是通过一个参数remote_listener来实现. 有关Oracle 网络配置相关基础以及概念性的问题请参考:      配置ORACLE 客户端连接到数据库   配置非默认端口的动态服务注册   

oerr ora 000845解决方法是扩大/dev/shm空间

打开虚拟机发现实例起不来 [[email protected] ~]# su - oraclesq[[email protected] ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Tue Aug 2 14:59:54 2016 Copyright (c) 1982, 2013, Oracle.  All rights reserved. Connected to an idle instance. [ema

tnsnames.ora文件说明

目录位置 unix:$ORACLE_HOME/network/admin WINDOW:%ORACLE_HOME%\network\admin 设置相应的环境变量:TNS_ADMIN tnsname.ora文件内容例子 --负载均衡,故障转移 sample2= (DESCRIPTION= (LOAD_BALANCE=on) (FAILOVER=on) (ADDRESS_LIST= (SOURCE_ROUTE=yes) (ADDRESS=(PROTOCOL=tcp)(HOST=host1)(POR

在TNSNAMES.ORA文件中配置本机装的oracle

首先,感谢这两位网友:http://zhidao.baidu.com/link?url=eGYeoEa-EhQdVitSGqjE36uNfVmEsryXH1WUjPue6YvArDSx-Y1N9_rd9Hx6vh-NklyevkcCtAMh1X28fI1Hoq 引子: 我在Oracle SQL Developer工具中创建了一个名为"oa"的连接,然后登陆PLSQL Developer,从本地导入一张表"T_DEPT",打开Oracle SQL Developer,

ALERT.LOG for ASM Shows "WARNING: failed to online diskgroup resource ora.GI.dg (unable to communica

APPLIES TO: OracleDatabase - Enterprise Edition - Version 11.2.0.1 to 12.1.0.1 [Release 11.2 to12.1] Informationin this document applies to any platform. ***Checked for relevance on 03-Jul-2013*** SYMPTOMS If OCR is located on ASM diskgroup, followin