~沉%淀~

一切有为法,如梦幻泡影,如露亦如电,应作如是观

  博客园 :: 首页 :: 博问 :: 闪存 :: 新随笔 :: 联系 :: 订阅 订阅 :: 管理 ::
To BottomTo Bottom

In this Document

  Symptoms
  Cause
  Solution
  References

 

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.3 [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 17-Dec-2013***

SYMPTOMS

Running an application job, the following error is reported:

ORA-00600: internal error code, arguments: [kcbz_check_objd_typ_1], [0], [0], [1], [], [], [], []


In the trace file is reported:

DATA seg.obj=0, on-disk obj=4199817, dsflg=0, dsobj=4200201, cls=4 
Formatted dump of block: 
buffer tsn: 3 rdba: 0x00401709 (1/5897)


The Call Stack looks like:

... kcbz_check_objd_typ kcbzib kcbgtcr ktecgsc ktecgetsh ktecgshx kteinicnt1 qertbFetch qerjoFetch qerjotFetch qerjoFetch qerjoFetch ...


Sometimes, the trace file also reports DBMS_SPACE and PRVT_ADVISOR on the PL/SQL Call Stack.

CAUSE

The cause of this problem has been identified in 
Bug 7429941 - ORA-00600[KCBZ_CHECK_OBJD_TYP_1] SOMETIMES OCCURS 
closed as duplicate of unpublished Bug 4430244 and related to unpublished Bug 5218905.

Unpublished Bug 4430244 is caused by the Segment advisor code that can load blocks into the cache for DROPped objects as CURRENT leading to subsequent operations seeing an incorrect (old) version of a block.

Unpublished Bug 5218905 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.

Both unpublished base bug 4430244 and related unpublished Bug 5218905 are a.o. fixed in 11.1.0.6 (Base Release) and 10.2.0.4 (Server Patch Set).
Please refer to
Note 4430244.8 - Bug 4430244 - Segment advisor can load blocks of dropped objects into buffer cache (KCB OERI errors)
Note 5218905.8 - Bug 5218905 - OERI[kcbnew_3] when segment advisor has been used

SOLUTION

To solve the issue, use any of below alternatives:

1. Upgrade to 11g or higher

- OR -

2. Apply 10.2.0.4 patchset or higher where both Unpublished Bug 4430244 and Unpublished Bug 5218905 are fixed 

- OR -

3. Disable Segment Advisor, e.g.

SQL> connect / as sysdba; 
SQL> exec dbms_scheduler.disable('AUTO_SPACE_ADVISOR_JOB');


- OR -

4. request merge patch for Unpublished Bug 4430244 and Unpublished Bug 5218905 on your current 
    release and platform 

- OR -

5. Check for availability of merge Patch 6133264 for Unpublished Bugs 5218905, 5728380
    and 4430244 on your current release and platform 
    For your info this merge patch include the fix for Unpublished Bug 5728380 for a problem introduced 
    in 9.2.0.8 and 10.2.0.3 by the fix for Unpublished Bug 4188324.

Note:
To check for conflicting patches, please use the MOS Patch Planner Tool
Please refer to
Note 1317012.1 - How To Use MOS Patch Planner To Check And Request The Conflict Patches?

REFERENCES



BUG:7429941 - ORA-00600[KCBZ_CHECK_OBJD_TYP_1] SOMETIMES OCCURS


NOTE:4430244.8 - Bug 4430244 - Segment advisor can load blocks of dropped objects into buffer cache (KCB OERI errors)
NOTE:5218905.8 - Bug 5218905 - OERI[kcbnew_3] when segment advisor has been used
posted on 2019-01-25 13:04  ~沉%淀~  阅读(267)  评论(0编辑  收藏  举报