Re: UNDO: 10g-style behaviour in

From: joel garry <>
Date: Wed, 8 Apr 2009 11:03:24 -0700 (PDT)
Message-ID: <>

On Apr 8, 2:30 am, Hemant K Chitale <> wrote:
> Yes, there is one significant difference (other than Retention
> Guarantee)
> It is called "Automatic Undo Retention"  .  Automatic Undo Management
> behaviour differs depending on whether the datafiles in the Undo
> tablespace are set to AutoExtend ON or AutoExtend OFF.
> In the AutoExtend ON case, the value you set for "undo_retention" is
> the floor value but Oracle automatically ajdusts the actual
> undo_retention it uses on the basis of query durations -- this you
> In the AutoExtend OFF case, Oracle will just grow undo usage till it
> uses the whole of the Undo Tablespace datafile even if the datafile
> size is excesively larger than required for either undo_retention or
> what would be the maxquerylen.
> This behaviour is controlled by the parameter "_undo_autotune"  which
> defaults to TRUE.
> IF you search for this, you will find a number of MetaLink Notes and
> bugs and suggeestions to set "_undo_autotune" to FALSE in pre
> (even in !)
> See MetaLink Notes 461480.1 and 420525.1
> Hemant K Chitale

Thanks for that, I had forgotten. Notes 7291739.8 and 742035.1for those wondering about, I take it? I have an undo nearly as big as my db data, from previous version testing of app upgrades. I hadn't acknowledged any problems, but now I have a clue of what to look for. I'm not autoextend, though I do have some nasty DSS query problems at times - I may have become complacent because of previous research convincing me it's just the way it is if users are going to do stuff like that.

One nugget like this can make all the online time worth it.


-- is bogus.
Received on Wed Apr 08 2009 - 13:03:24 CDT

Original text of this message