ORA-600 [17113] "error getting an extent for a heap"

ORA-600 [17113] "error getting an extent for a heap"
	:	39453.1	型別:	REFERENCE
	上次修訂日期:	16-APR-2009	狀態:	PUBLISHED

Note: For additional ORA-600 related information please read 

PURPOSE:
  This article discusses the internal error "ORA-600 [17113]", 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 [17113] [a]

VERSIONS:
  versions 7.0 to 10.1

DESCRIPTION:

  An error occurred when getting a new extent while adding to a heap.

  The heap descriptor is uninitialized.

ARGUMENTS:
  Arg [a] Always 0

FUNCTIONALITY:
  HEAP MANAGER

IMPACT:
  PROCESS FAILURE
  MEMORY CORRUPTION
  NON DATA CORRUPTIVE - No underlying data corruption.

SUGGESTIONS:

  These errors can occur after the actual Oracle in-memory corruption
  has taken place.

  Hence the processes that report the error may not be the ones that 
  caused it.

  Check for third party software being used to access the database.
  This error can be reported when there are compatibility issues
  between third party software and the database.

  Check for other messages preceeding this message.

  Check if the problem is reproducable.

  Run memory diagnostics on all system hardware.

  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:
  Bug# 3488371   See 
      OERI[17113] can occur during import of materialized views
      Fixed: 10.1.0.4, 10.2.0.1
 
  Bug# 3066549   See 
      OERI[17113] / memory corruption can occur selecting from a view
      Fixed: 9.2.0.5, 10.1.0.2
 
  Bug# 2298968 +  See 
      Client side memory leak for 3264 bit SELECTs
      Fixed: 9.0.1.4, 9.2.0.1
 
  Bug# 2248904   See 
      Memory corrupt possible during optimization of distributed query
      Fixed: 8.1.7.4, 9.0.1.4, 9.2.0.1
 
  Bug# 1964934   See 
      Memory corruption possible using INSERT /*+ APPEND */ over DBLINK
      Fixed: 8.1.7.4, 9.0.1.3, 9.2.0.1
 
  Bug# 1460657   See 
      OERI:17113 creating partitioned OBJECT MVIEW with LOB column
      Fixed: 9.0.1.0