Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> Re: ORA-600

Re: ORA-600

From: Hemant K Chitale <hkchital_at_singnet.com.sg>
Date: Tue, 16 Sep 2003 08:44:37 -0800
Message-ID: <F001.005D00F8.20030916084437@fatcity.com>


Doc ID: 
         Note:34782.1
 Subject:
         ORA-600 [17114] "KGH Bad magic
         number in header"
 Type:
         REFERENCE
 Status:
         PUBLISHED

                                       Content Type:
                                                         TEXT/PLAIN
                                       Creation Date:
                                                         29-FEB-1996
                                       Last Revision Date:
                                                         29-OCT-2002



 Note: For additional ORA-600 related information please read [NOTE:146580.1]
 
 PURPOSE:            
   This article discusses the internal error "ORA-600 [17114]", what 
   it means and possible actions. The information here is only applicable 
   to the versions listed and is provided only for guidance.
  
 ERROR:              
   ORA-600 [17114][a][b][c][d][e]
  
 VERSIONS:           
   versions 7.X to 8.X
  
 DESCRIPTION:        
 
   Oracle has detected that the magic number in a memory chunk header has been 
   overwritten.
 
   This is a heap (in memory) corruption and there is no underlying data 
   corruption.
 
   The error may occur in the one of the process specific heaps  
   (the Call heap, PGA heap, or session heap) or in the shared heap (SGA).
  
  
 FUNCTIONALITY:      
   HEAP MANAGEMENT
  
 IMPACT:             
   PROCESS FAILURE
   MEMORY CORRUPTION, POSSIBLE INSTANCE FAILURE
   NON DATA CORRUPTIVE - No underlying data corruption.
  
 SUGGESTIONS:        
 
   If you think you are not hitting any of the known issues shown below, 
   then you need to set event 10235 in your init.ora file :-
 
      event="10235 trace name context forever, level 1"
      
   While the event is set, the next time you get the error a trace
   file will be generated in your USER_DUMP_DEST directory.
   Contact Oracle Support Services and supply the trace file.
  
   Known Issues:
   Bug 898074: PRIVATE MEM CORR ON PARTITION TABLE & NON-PARTITION-KEY PREDICATE
   fixed in 8.0.6.1 and 8.1.6.0 releases
   Bug 573746: --
     DBMS_SQL DEFINE_ARRAY / ARRAY FETCH TO LARGE ARRAY MAY CAUSE ORA-600[17114]
   fixed in 8.0.4.4, 8.0.5.0 and 8.1.5.0 releases
   Bug 1280983: ORA-600 [17114]/ORA-600 [17112] USING STAR_TRANSFORMATION
   fixed in 8.1.7.0

Hemant

At 08:14 AM 16-09-03 -0800, you wrote:
This is on an old 7.3.4 database.  I can't find the same error on Metalink.  Anybody have any ideas what might be the cause?
 
 ORA-00600: internal error code, arguments: [17114], [1074346728], [], [], [], [], [], []
 
Ron Smith

Hemant K Chitale
Oracle 9i Database Administrator Certified Professional
My personal web site is :  http://hkchital.tripod.com

-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Hemant K Chitale INET: hkchital@singnet.com.sg Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Tue Sep 16 2003 - 11:44:37 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US