Re: DBA_TEMP_FILES.MAXBYTES is wrong

From: Connor McDonald <mcdonald.connor_at_gmail.com>
Date: Fri, 3 Jun 2005 08:16:06 +0800
Message-ID: <5e3048620506021716dcff645@mail.gmail.com>

We're on Solaris 9205 and have "0" for dba_temp_files.maxbytes no matter how much sorting is occurring.

We just regularly keep an eye on v$sort_usage.

hth
connor

On 5/30/05, Herring Dave - dherri <Dave.Herring_at_acxiom.com> wrote:
> Has anyone had an issue with MAX* columns within DBA_TEMP_FILES being
> wrong?

>=20
>=20

> I've got one temp tablespace, type temporary, defined for all users and
> the default at the database level (9.2.0.4 on Tru64). This temp
> tablespace has 6 tempfiles defined, each created with a maxsize of
> 40,001M (see results of an 'ls -l' below):
>=20
>=20

--=20
Connor McDonald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D
email: connor_mcdonald_at_yahoo.com
web: http://www.oracledba.co.uk

"Semper in excremento, sole profundum qui variat"

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

Received on Thu Jun 02 2005 - 20:21:25 CDT