Re: FYI - 10gR2 automatic memory management bugs

  • From: "Jared Still" <jkstill@xxxxxxxxx>
  • To: sac@xxxxxxxxxxxxx
  • Date: Thu, 4 May 2006 09:57:05 -0700

Interesting, as none of those bug numbers appear on MetaLink.
(Advanced search, bug id)

Can you provide more detail as to what these bugs involve?

I've run into a couple issues on that are ASSM related.


On 5/4/06, Schultz, Charles <sac@xxxxxxxxxxxxx> wrote:

In hopes that nobody else suffers critical slowdowns in their production database in the middle of the day or night, I am sharing what we have recently learned about some of the automatic memory management "features" (aka, bugs).

Apparently, the algorithms that decide when and how fast to grow the
shared pool are a bit less than ideal. I do not know all the details yet,
but we have stumbled upon the following bugs in

4472338 (duplicate of the above 4466399)
4507532 (turned out to be a bad diagnosis, but the bug is real)

It is my understanding that only 4507532 is fixed in - too bad we
did not hit that bug. =) 4920199 is currently being worked on, and I was
told that 4466399 was only available in v11. And since there is an ingenious
work-around, no one-off patch is planned. What is this work-around? Simple,
turn off the automatic tuning features by setting sga_target = 0.

-- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist

Other related posts: