Re: x$ksmlru question

Hi,

x$ksmlru keeps the *top* allocations in it since last querying, thus you don't really need to sample it too often. You should keep an eye on rows with highest ksmlrnum values (the number of chunks flushed due this allocation), ksmlrsiz (chunk allocation size) has a secondary importance....

also one potential strategy to catch 4031 causes would be to do set event 4031 trace name heapdump level 2, that way you get an overview of your shared pool contents on error occurrence.

Tanel.

• Original Message ----- From: "rjamya" <rjamya_at_gmail.com> To: "Oracle Discussion List" <oracle-l_at_freelists.org> Sent: Monday, March 14, 2005 6:29 PM Subject: x$ksmlru question

> To all those x$gurus,
>
> I am investigating ora-4031 errors, and I need to monitor x$ksmlru as
> well. Would it be a terrible bad thing to scan this periodically? I
> love my database.
>
> Please note that I haven't defined a timeframe to quantify
> periodically. Does anyone have suggestions for timeframe? it is a 24x7

--
http://www.freelists.org/webpage/oracle-l