RE: DBA_TEMP_FILES.MAXBYTES is wrong

Is your database 64 K block size?


-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On
Behalf Of Herring Dave - dherri
Sent: Monday, May 30, 2005 10:27 PM
To: Oracle-L@Freelists. Org (E-mail)
Subject: DBA_TEMP_FILES.MAXBYTES is wrong

Has anyone had an issue with MAX* columns within DBA_TEMP_FILES being
wrong?


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):



-rw-rw----   1 oracle   dba      41944121344 May 29 20:43
/u01/oradata/sid1/temp02.dbf

-rw-rw----   1 oracle   dba      41944121344 May 29 21:41
/u02/oradata/sid1/temp03.dbf

-rw-rw----   1 oracle   dba      41944121344 May 29 20:56
/u03/oradata/sid1/temp04.dbf

-rw-rw----   1 oracle   dba      41944121344 May 29 21:42
/u04/oradata/sid1/temp05.dbf

-rw-rw----   1 oracle   dba      41944121344 May 29 21:01
/u05/oradata/sid1/temp06.dbf

-rw-rw----   1 oracle   dba      41944121344 May 29 21:42
/u06/oradata/sid1/temp01.dbf



Yet when I query DBA_TEMP_FILES I get the following:



column file_name format a40

SELECT file_name

     , bytes/1024/1024 mb

     , maxbytes/1024/1024 max_mb

  FROM dba_temp_files

 ORDER BY file_name;



FILE_NAME                                        MB     MAX_MB

---------------------------------------- ---------- ----------

/u01/oradata/gmdwit/temp_two02.dbf            40001      .0625

/u02/oradata/gmdwit/temp_two03.dbf            40001      .0625

/u03/oradata/gmdwit/temp_two04.dbf            40001      .0625

/u04/oradata/gmdwit/temp_two05.dbf            40001      .0625

/u05/oradata/gmdwit/temp_two06.dbf            40001      .0625

/u06/oradata/gmdwit/temp_two01.dbf            40001      .0625



I checked the view definition for DBA_TEMP_FILES and it appears that the
value for MAXBYTES is pulled from SYS.X$KTFTHC.KTFTHCUSZ, which is
apparently also wrong.



Has anyone else run into this?  It's sure hard to write a script to
detect a low temp space issue when I can't determine the max size of my
temp space.



Thanks.



Dave

-------------------------------------

Dave Herring, DBA

Acxiom Corporation

3333 Finley

Downers Grove, IL 60515

wk: 630.944.4762

<mailto:dherri@xxxxxxxxxx <mailto:dherri@xxxxxxxxxx> >

-------------------------------------





**********************************************************************
The information contained in this communication is
confidential, is intended only for the use of the recipient
named above, and may be legally privileged.
If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution, or copying of this communication is strictly
prohibited.
If you have received this communication in error,
please re-send this communication to the sender and
delete the original message or any copy of it from your
computer system. Thank You.


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


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

Other related posts: