Space leaks = Oracle malloced memory and did not free it when done.
There is actually an init.ora event that can be set to ignore memory leaks so
you don't have to see them in your alert log.
10262, 00000, "Don't check for memory leaks"
// *Cause: Setting this event to level one causes memory leak checking to
// be disabled. Setting this event to any other non-zero number
// allows that number to be used as a threshold value when checking
// for memory leaks in the PGA, SGA, and UGA heaps.
Jared
On Wednesday 02 May 2001 07:19, Nuno Souto wrote:
> In the alert log?
> HP9K, HP-UX, Oracle 8.0.6.0.
> I'm getting about 6 a day.
> No apparent harm to the DB.
> Metalink as usual says: "can't reproduce
> problem" to most of these bugs.
> Couldn't find a concrete fix to this anywhere.
> Nope, I'm not using direct export.
>
> TIA for any feedback.
> Cheers
> Nuno Souto
> [EMAIL PROTECTED]
> http://www.users.bigpond.net.au/the_Den
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jared Still
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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).
