ORA-00600 [KCBNEW_3] 分析

最新推荐文章于 2020-03-17 15:31:32 发布

转载最新推荐文章于 2020-03-17 15:31:32 发布 · 294 阅读

本文详细介绍了ORA-00600[KCBNEW_3]错误的原因及常见解决方案，包括缓存区清理与应用补丁等，并列举了相关错误案例。

系统：AIX
数据库版本：10.2.0.3

报错如下：
Tue Jan 15 04:08:18 2013
Errors in file /oracle/admin/RASDB/udump/rasdb_ora_766202.trc:
ORA-00600: internal error code, arguments: [kcbnew_3], [0], [8], [1639086], [], [], [], []

查看官方说明：
Summary of Bugs Containing ORA - 00600 [KCBNEW_3] [ID 428568.1]

Applies to:

Oracle Server - Enterprise Edition - Version: 8.1.7.4 to 11.1.0.6
Information in this document applies to any platform.

Purpose

This article is intended to

1. Help the reader to understand ORA-00600 [KCBNEW_3] error and how is this caused.

2. List the most common bugs of the aforesaid error and their fixes.

Scope

This is a consolidated article based upon various bugs logged for the error ORA-00600 [KCBNEW_3] and gives the reader an overview about the most frequent bugs which the customers are affected with.

The error ORA-00600 [KCBNEW_3] is raised due to the following reason.

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.

Summary of Bugs Containing ORA - 00600 [KCBNEW_3]

Bug 4430244 ( Unpublished )

Abstract : ORA-600: INTERNAL ERROR CODE, ARGUMENTS: [KCBNEW_3]

Versions affected : 10.2

Fixed releases : 10.2.0.4, 11.0.0.0

Details : Segment advisor code (eg: DBMS_SPACE.OBJECT_GROWTH_TREND)

can load blocks into the cache for DROPped objects as CURRENT leading

to subsequent operations seeing an incorrect (old) version of a block.

This can lead to various internal buffer cache related errors such as

ORA-600 [kcbnew_3] / ORA-600 [kcbz_check_objd_typ_3].

The exact error depends on which code sees the block.

Backportable : yes to 10.2

Symptoms :

1. ORA-600 [kcbnew_3] internal error reported in the alert.log

2. May occur if segment advisor and DROP operation are being run
concurrently on the same object.

Workaround :

sql>alter system flush buffer cache' to flush the buufer in the cache.

Patch Details:

Check Metalink for Patch 4430244 availability.