Although I agree with Daniel a ORA-600 should be reported in a TAR the
ORA-600 [729] is the exception to the rule. It is reported so many times. In
our environments it did not happen on V8.1.7.0 (Sun, HP-UX) and now occurrs
a few times a day (totally over all databases) since we upgraded to
V8.1.7.3.
Setting the event just eliminates the alert.log message that can be very
annoying when using OEM or other monitor tools. As far as I have understood
from the bugs and notes on this one in Metalink it is harmless and setting
the event is the recommendation. It occurs on logoff so the session is not
influenced nor notices the error.
Have not heard about a fix but did not look for it lately.
clueless <ro_cright_at_hotmail.com> schreef in berichtnieuws
ANph9.12418$V21.286694_at_news...
| hi gang,
|
| I have the following recurring error in my trace file:
| "ORA-00600: internal error code, arguments: [729], [688], [space
leak],"
|
| Oracle states that this is a minor memory leak and that I should add the
| following param to the init.ora file to ignore memory leaks < 4k:
| "EVENT="10262 trace name context forever, level 4096" # ignore leaks <
| 4K "
|
| The question is why do I have a memory leak? Is there someone who can
| point me in the right direction?
|
| Cheers,
| Clueless
|
|
Received on Mon Sep 16 2002 - 16:09:35 CDT
