Hi all,
thanks you all for your answer (sorry my reply is not very quick, I'm afraid
we're in different
time zones !).
Well my question actually was about monitoring left blocks on rollback
segments. As we're
going to build a very large queue of transaction in our application I'd like
to see if (and how)
we're close to exhaust rollback segments.
I'll read carefully your answers and try which solution suits better. By the
way I'm using Oracle 9i
but it would be fine to know something that's portable also on earlier
releases.....
Thanks a lot
Francesco
"Tanel Poder" <tanel@@peldik.com> ha scritto nel messaggio
news:3f2ee0da$1_1_at_news.estpak.ee...
> I hit send too early:
>
> > And v$undostat doesn't actually give us directly any information how
much
> > the automatically managed undo segments could grow, or how much free
space
> > they got in them. Instead, they provide us even more valuable
information
> > such:
> > * SSOLDERRCNT (how many times ORA-1555 has occurred)
> > * NOSPACEERRCNT (how many times no free space at all was possible to
> > allocate in undo seg)
> > And three UNXP% parameters. SSOLDERRCNT and NOSPACEERRCNT should always
be
> > zero in normally working system and UNXP parameters (number of unexpired
> > undo blocks/extents which have actually been allocated to another
> > transaction before undo_retention should allow).
>
> ...the UNXP *columns* values in v$undostat should be low as well,
otherwise
> undo_retention could be compromized..
>
> Tanel.
>
>
Received on Tue Aug 05 2003 - 01:37:35 CDT
