Re: memory leak and event 10262

Clueless-

Memory leaks happen for a variety of reasons. Minor bug, typically. Probably nothing to worry about. But, even a small leak of just a few bytes per transaction can add up for a persistent connection.

What is being reported here is a difference in memory allocation between logon and logoff for the session's process memory. Some small chunk of memory allocated for some operation simply did not get released to the operating system properly. At session logoff, all the memory for the process gets released, so a small "leak" is no big deal. The event setting just suppresses the error message for small amounts of memory.

1. How long was this session connected? It leaked a total of 688 bytes for that period. If it was an app server connected for a week or so, then this is definitely no big deal.
2. What version of Oracle is this? Might be a known bug for which a patch exists.
3. Go ahead and set the event parameter. If you have a bigger leak than 4k, it will then get reported and you can log a tar, investigate further.
   • ricky

clueless wrote:
>
> 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 - 14:42:33 CDT