ORA-00600错误

随笔泼墨

alert日志里报告了一个600错误，但是信息太少，请各位帮忙分析下如何跟踪错误信息
Mon Apr  2 10:14:06 2012
Errors in file /oracle/admin/zypw/udump/zypw1_ora_17725.trc:
ORA-00600: internal error code, arguments: [733], [290424544], [top call heap], [], [], [], [], []
Mon Apr  2 10:14:07 2012
Trace dumping is performing id=[cdmp_20120402101407]

查看cdmp_2012402101407  目录有几十个trw文件。请问如何分析

回忆未来

先把 这个  /oracle/admin/zypw/udump/zypw1_ora_17725.trc  上传

ORA-600 [733] is a memory allocation error and the first arguments shows the minimum extent size requested, in bytes. ~1G is an abnormal large memory allocation request and is significant for hitting this problem.

Maclean Liu(刘相兵

ORA-00600: internal error code, arguments: [733], [290424544], [top call heap], [], [], [], [], []


700         vos         Memory



top call heap  argument 290424544 = 276MB

ORA-600 [733] "memory request size is too big for this port (o/s)"

ERROR:              

  Format: ORA-600 [733] [a]


VERSIONS:
  versions 7.0 to 9.2

DESCRIPTION:        

  When allocating an extent in the PGA, if the minimum size requested is
  greater than what is allowed for this port, ORA-600 [733] is reported.

  This is a Program Global Area (PGA) heap/memory allocation error.

ARGUMENTS:
  Arg a The minimum extent size requested, in bytes.
  Arg b comment supplied by the caller.

FUNCTIONALITY:      
  MEMORY IMPLEMENATION

IMPACT:            
  PROCESS FAILURE
  NON CORRUPTIVE - No corruption to underlying data.

SUGGESTIONS:        

  If receiving this during a query with complex JOIN, for example, consider
  lowering sort_area_size or hash_area_size (if hash_join_enabled = true)
  and rerun the query. This will reduce the PGA memory requirements and may
  clear the problem.



可能由Server Process分配大Extent的 PGA 内存引起， 建议你上传TRACE文件 "/oracle/admin/zypw/udump/zypw1_ora_17725.trc"

调整SQL语句对PGA的使用 如HASH JOIN、SORT，或调整 PGA/OS参数解决该问题

随笔泼墨

谢谢 回忆未来和maclean

犯了个低级错误，之前查看zypw1_ora_17725.trc 到ORA-00600: internal error code, arguments: [733], [290424544], [top call heap], [], [], [], [], []
Current SQL statement for this session:下面跟了
@
@
@
@
没仔细看  原来下面还有一个sql 语句，应该是这个sql引发的问题  

我在仔细分析一下