Thank you very much Tanel. I don't have privileges to run dtrace on the servers, I will have SA to run it. Upgrade to latest version is a good suggestion:) On Mon, Feb 25, 2013 at 12:07 PM, Tanel Poder <tanel@xxxxxxxxxxxxxx> wrote: > Long story short - memory leaks are hard to diagnose, but at least you > have dtrace. Nevertheless, it might be just easier to patch the OS to the > latest version first and hope the problem goes away. > > -- > *Tanel Poder* > Enkitec (The Exadata Experts) > Training <http://blog.tanelpoder.com/seminar/> | > Troubleshooting<http://blog.tanelpoder.com/> > | Exadata<http://www.amazon.com/Expert-Oracle-Exadata-Apress/dp/1430233923> > | Voicee App <http://voic.ee/> > > > > On Mon, Feb 25, 2013 at 6:05 AM, Tanel Poder <tanel@xxxxxxxxxxxxxx> wrote: > >> As your memory allocation seems to be increasing, then taking strack >> traces when kmem_alloc function is called would help to pinpoint who & when >> is allocating the memory. >> >> For example, something like this (although you may want to modify it to >> kick in for any process): >> >> #!/usr/sbin/dtrace -qs >> >> #pragma D option quiet >> >> fbt::kmem_*alloc:entry, >> fbt::bkmem_alloc:entry >> /execname == "oracle" && curpsinfo->pr_psargs == "oracleSOL102 >> (LOCAL=NO)" / >> { >> @kmem[probefunc,stack()] = sum(arg0) >> } >> >> >> -- Eagle Fan (www.dbafan.com) -- //www.freelists.org/webpage/oracle-l