ORA-00600: 内部错误代码, 参数: [kcbnew

ORA-00600: 内部错误代码, 参数: [kcbnew_3]

一：环境信息

DB：Oracle 11.2.0.3.0

OS：Windows Server 2008

二：问题现象

portal前台报错：

警告日志：

Wed Nov 15 09:08:45 2017

Errors in file D:\APP\ADMINISTRATOR\diag\rdbms\orcl\orcl\trace\orcl_ora_6324.trc (incident=63384):

ORA-00600: 内部错误代码, 参数: [kcbnew_3], [0], [76058], [4], [], [], [], [], [], [], [], []

Use ADRCI or Support Workbench to package the incident.

See Note 411.1 at My Oracle Support for error and packaging details.

跟踪日志orcl_ora_6324.trc：

DDE: Problem Key 'ORA 600 [kcbnew_3]' was flood controlled (0x6) (incident: 63384)

ORA-00600: 内部错误代码, 参数: [kcbnew_3], [0], [76058], [4], [], [], [], [], [], [], [], []

Dump of buffer cache at level 10 for tsn=6 rdba=29499424

BH (0x000000152FF4F868) file#: 7 rdba: 0x01c22020 (7/139296) class: 1 ba: 0x000000152EA10000

set: 78 pool: 3 bsz: 8192 bsi: 0 sflg: 1 pwc: 1646,28

dbwrid: 1 obj: 286891 objn: 286891 tsn: 6 afn: 7 hint: f

hash: [0x000000158F99A338,0x00000039D9FA7BA0] lru: [0x000000152FF4FBB0,0x000000152FF4F820]

ckptq: [NULL] fileq: [NULL] objq: [0x000000152FF4FBD8,0x000000152FF4F848] objaq: [0x000000152FF4FBE8,0x000000152FF4F858]

st: XCURRENT md: NULL fpin: 'kdswh11: kdst_fetch' tch: 1

flags: only_sequential_access

LRBA: [0x0.0.0] LSCN: [0x0.0] HSCN: [0xffff.ffffffff] HSUB: [65535]

buffer tsn: 6 rdba: 0x01c22020 (7/139296)

scn: 0x0000.0bc4eb5e seq: 0x01 flg: 0x06 tail: 0xeb5e0601

frmt: 0x02 chkval: 0x22e8 type: 0x06=trans data

......

三：解决方案

清空数据库缓存(正式环境需谨慎使用)

alter system flush buffer_cache;

ORA-600 [kcbnew_3] (文档 ID 204512.1)

转到底部

修改时间:

2017-10-26

类型:

REFERENCE

Note: For additional ORA-600 related information please read Note:146580.1

PURPOSE:

This article discusses the internal error "ORA-600 [kcbnew_3]", what

it means and possible actions. The information here is only applicable

to the versions listed and is provided only for guidance.

ERROR:

Format: ORA-600 [kcbnew_3] [a] [b] [c]

VERSIONS:

versions 9.2 and later

DESCRIPTION:

A cache buffer holding a database block is in the process of

being reused.

The buffer is in state "current" and may be reused only if the object

is of type temp or undo.

The consistency check comparing the block class in the buffer header

with the block class passed to the cache by the caller is failing.

ARGUMENTS:

The number of arguments and their meaning vary depending on the Oracle

Server release.

Oracle 11.1 and later:

Arg [a] Internal loop counter (number of blocks to new)

Arg [b] Object Id passed to the cache by the layer accessing the cache

Arg [c] Flags defining the characteristics of the use of the buffer

Oracle 10.1 and 10.2:

Arg [a] Internal loop counter (number of blocks to new)

Arg [b] Buffer class

Arg [c] Object Id passed to the cache by the layer accessing the cache

Oracle Release 9.2 and earlier:

Arg [a] Buffer class

FUNCTIONALITY:

Kernel Cache Buffer management Implementation

IMPACT:

PROCESS FAILURE

MEMORY CORRUPTION

NON CORRUPTIVE - No underlying data corruption.

SUGGESTIONS:

If the Known Issues section below does not help in terms of identifying

a solution, please submit the trace files and alert.log to Oracle

Support Services for further analysis.

Known Issues:

You can restrict the list below to issues likely to affect one of the following versions by clicking the relevant button:

NB	Prob	Bug	Fixed	Description
	III	10043021	11.2.0.4, 12.1.0.1	ORA-600 [kcbnew_3] after select / analyze on RECYCLEBIN object
	-	22116368	12.2.0.1	Assorted ORA-600 / ORA-700
	II	21037905	12.2.0.1	ORA-600 [kcbchg1_16] or similar in RAC - can trigger ORA-600 [1433] / instance crash
	III	12391183	11.2.0.3, 12.1.0.1	ORA-600 [kcbnew_3] with "_db_fast_obj_truncate"=false
	IIII	11902008	11.2.0.4, 12.1.0.1	SMON may crash with ORA-600 [kcbgcur_3] or ORA-600 [kcbnew_3] during Transaction recovery
	III	9275027	11.2.0.2, 12.1.0.1	ORA-600 [kcbnew_3] can occur after TRUNCATE / DROP
	III	9456964	11.2.0.2	OERI[kcbnew_3] after shrinking an IOT and reusing the blocks freed by shrink
	II	6970071	10.2.0.5, 11.2.0.1	ORA-600 [kcbnew_3] when recyclebin is active
	II	6730125	10.2.0.5, 11.1.0.7, 11.2.0.1	OERI[kcbnew_3] during instance recovery
	III	6079038	10.2.0.5, 11.2.0.1	Internal Errors from DML with error logging / batch errors against partitioned table
*	II	6017420	10.2.0.4, 11.1.0.6	OERI[kcbo_link_q_1] / crash with fix for bug 5454831 installed
	III	5558244	10.2.0.4, 11.1.0.6	OERI[kcbnew_3] can occur
	II	5303237	11.1.0.6	ORA-600 [kcbgtcr_5] during create queue table
	III	5218905	10.2.0.4, 11.1.0.6	OERI[kcbnew_3] when segment advisor has been used
+	III	4430244	10.2.0.4, 11.1.0.6	Segment advisor can load blocks of dropped objects into buffer cache (KCB OERI errors)
+	III	5523799		Various OERI (eg kcbgtcr_12) using ASSM managed segments - superceded
	I	5718371	10.1.0.2	OERI[kcbgtcr_12] / [kcbnew_3] from concurrent CTAS and DROP TABLE
*	I	3785200	10.1.0.2, 9.2.0.6	Corruption possible in automatic space managed segments
	-	3085651	9.2.0.5, 10.1.0.2	Table corruption / OERI after TRUNCATE on ASSM table with NESTED TABLE cols
	-	2768278	9.2.0.4, 10.1.0.2	OERI[KCBNEW_3] possible after DROP of 8i segment in locally managed tablespace
	II	2747978	9.2.0.4, 10.1.0.2	OERI[KCBNEW_3] after resize of locally managed tablespace
	-	2406802	9.2.0.2	OERI[kcbgtcr_3] / OERI[kcbcxx_1] after DROP TABLE in locally managed tablespace
	-	2414972	9.2.0.2	OERI:[kcbnew_3]/OERI:[kcbgtcr_3] after resize in LOCALLY MANAGED tablespace

· '*' indicates that an alert exists for that issue.

· '+' indicates a particularly notable issue / bug.

· See Note:1944526.1 for details of other symbols used

Bug 5218905 - OERI[kcbnew_3] when segment advisor has been used (文档 ID 5218905.8)

转到底部

修改时间:

2012-7-26

类型:

PATCH

Bug 5218905 OERI[kcbnew_3] when segment advisor has been used

This note gives a brief overview of bug 5218905.
The content was last updated on: 03-APR-2009
Click here for details of each of the sections below.

Affects:

*Product (Component)*	Oracle Server (Rdbms)
*Range of versions believed* to be affected**	Versions < 11
*Versions confirmed* as being affected**	10.2.0.1 10.2.0.2 10.2.0.3
Platforms affected	Generic (all / most platforms affected)

Fixed:

This issue is fixed in	10.2.0.3 Patch 28 on Windows Platforms 10.2.0.4 (Server Patch Set) 11.1.0.6 (Base Release)
Symptoms:		Related To:
Internal Error May Occur (ORA-600) ORA-600 [kcbnew_3]		(None Specified)

Description

ORA-600 [kcbnew_3] can occur when segment advisor

has been running on an instance as it can read blocks

into the cache as CURRENT when it should have read

them as CR.

Note: The presence of ORA-600 [kcbnew_3] does not mean

that you HAVE encountered this problem as there can

be other reasons for a wrong block in the cache.

Workaround

Do not use segment advisor.

eg: connect / as sysdba;

exec dbms_scheduler.disable('AUTO_SPACE_ADVISOR_JOB');

Use "alter system flush buffer_cache" to clear bad blocks

from the cache

Note:

Also see <Bug:4430244>

Please note: The above is a summary description only. Actual symptoms can vary. Matching to any symptoms here does not confirm that you are encountering this problem. Always consult with Oracle Support for advice.

References

Bug:5218905 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/29785807/viewspace-2147440/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/29785807/viewspace-2147440/