Trace file /opt/oracle/app/oracle/diag/rdbms/suSEOra/suSEOra2/trace/suSEOra2_ora_36386.trc@H_502_1@

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

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

Data Mining and Real Application Testing options@H_502_1@

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

System name: Linux@H_502_1@

Node name: usdprac2@H_502_1@

Release: 2.6.32.12-0.7-default@H_502_1@

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

Machine: x86_64@H_502_1@

Instance name: suSEOra2@H_502_1@

Redo thread mounted by this instance: 2@H_502_1@

Oracle process number: 299@H_502_1@

Unix process pid: 36386,image: oracle@usdprac2@H_502_1@

@H_502_1@

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

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

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

*** SERVICE NAME:(suSEOra) 2017-05-08 15:39:49.842@H_502_1@

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

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

@H_502_1@

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

OBJD MISMATCH typ=35,seg.obj=-2,diskobj=8677570,dsflg=0,0);">dsobj=489719,tid=489719,cls=4@H_502_1@

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

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

Input data (nil),0@H_502_1@

Formatted dump of block:@H_502_1@

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

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

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

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

@H_502_1@

@H_502_1@

@H_502_1@

@H_502_1@

查询：@H_502_1@

@H_502_1@

1.查询相关段信息@H_502_1@

col owner format a10@H_502_1@

col object_name format a30@H_502_1@

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);@H_502_1@

2.查询段详细信息@H_502_1@

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

3.查询相关数据文件@H_502_1@

col name format a30@H_502_1@

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

4.查询表空间信息@H_502_1@

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

5.查询相关区信息@H_502_1@

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;@H_502_1@

select owner,block_id from dba_extents where block_id=;@H_502_1@

@H_502_1@

@H_502_1@

@H_502_1@

原因：@H_502_1@

经过MOS查询分析，该错误触发BUG：19689979。@H_502_1@

@H_502_1@

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

触发该BUG的对象为：@H_502_1@

@H_502_1@

解决方案：@H_502_1@

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

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

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

@H_502_1@

@H_502_1@

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