ORA-600 [4553] Being Hit [ID 1243704.1]

renjixinchina發表於2012-08-01

In this Document

Applies to:

Oracle Server - Enterprise Edition - Version 8.1.7.4 and later
Information in this document applies to any platform.
Applies to 8.1.7.4 onwards.
Checked for relevance on 14-June-2012

Symptoms

ORA-600 [4553] reported in the alert.log or client application.

Other errors can be reported prior to this one: 

e.g.:  ORA-600: [KCLCHKBLK_3] 

Cause






Solution

Usually this is caused by OS or hardware errors and all previously reported issues to development have been closed as not a bug. e.g.:

Bug#FixedDescription
N/AClosed as not a bug. Issue related to an EMC process where they rediscovered and reinitialized one or more HBAs using emc tools  like emulex/emcpdiscover with lost writes.
N/AClosed as not a bug. Issue related to hardware errors.
N/AClosed as not a bug. Issue related to external mirroring.
unpublished 6963622N/AClosed as not a bug. Issue related to OS cache errors.
unpublished 5588056N/AClosed as duplicate of unpublished Bug 5586289 "RACDES: ORA-600: [KCLCHKBLK_3],[0]" (not a bug, issue related to disk cache)












                                                                              


Diagnosis: 

1. Get the full trace file


2. Determine which of the specific errors is being signalled.


3. Reproduce the error with the following events set in order to capture more information about the root cause:

_db_block_cache_protect = TRUE
_db_writer_verify_writes = TRUE
_db_block_check_for_debug = TRUE
db_block_checking = medium
db_block_checksum = TRUE
event="10708 trace name context forever, level 9"


Submit the trace files to the Oracle Support for investigation.

Note: Setting these events could cause significant (1-20%) performance degradation depending on application workload. Please test feasibility before setting these in a production system.


4. Perform. a hardware check and verify the OS error log for any possible external errors and fix them. 

5. If the error is still reported afterwards check for datafile corruption using DBV (Note 35512.1 "DBVERIFY - Database file Verification Utility (7.3.2 - 11.2)"). 

6.  If a corruption is found, follow the steps from Note 28814.1 Handling Oracle Block Corruptions in Oracle7/8/8i/9i/10g/11g.

 

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/15747463/viewspace-739535/，如需轉載，請註明出處，否則將追究法律責任。

相關文章