Note: For additional ORA-600 related information please read Note:146580.1
PURPOSE: This article discusses the internal error "ORA-600 [729]", what it means and possible actions. The information here is only applicable to the versions listed and is provided only for guidance. ERROR:
Format: ORA-600 [729] [a] [b]
VERSIONS:
versions 7.0 and above
DESCRIPTION:
A space leak has been detected in the User Global Area (UGA).
There is NO data corruption as a result of this error.
It is an internal memory housekeeping problem.
ARGUMENTS:
Arg [a] This is the number of bytes leaked
Arg [b] "space leak"
FUNCTIONALITY:
MEMORY COMPONENT
IMPACT:
PROCESS FAILURE - But only during logoff so impact is minimal.
NON CORRUPTIVE - No underlying data corruption.
SUGGESTIONS:
Event 10262 can be set to safely ignore small memory leaks.
Set the following in init.ora for example to disable space
leaks less than 4000 bytes:
event = "10262 trace name context forever, level 4000"
and stop and restart the database.
Repeated errors or large memory leaks can be diagnosed further by
sending the alert.log and trace files to Oracle support.
Known Issues:
Related Articles
Note:403584.1 Understanding and Diagnosing ORA-600 [729] Space Leak Errors