This has nothing to do with autoextend, I think you misunderstood the
problem.
Anyway they are set aside for just oracle datafiles. The point is that
'df .' ignores the sparse files 'reported' size and goes on 'real' size
(i.e. much smaller),
and hence gives you a false impression of the real amount of 'free' disk
space in a filesystem.
Hence the amount of real disk space Oracle requires when it uses the TEMP
datafile grows by
someone just running a query, with NO autoextend etc. enabled.
If you see 1Gb free in a filesystem, you assume you can use all of that.
Otherwise it becomes a manageability problem.
Alun
"Niall Litchfield" <niall.litchfield_at_dial.pipex.com> wrote in message
news:3d234f7d$0$8505$cc9e4d1f_at_news.dial.pipex.com...
> "Liggs" <liggs_at_hotmail.com> wrote in message
> news:afv89t$cl3$1_at_helle.btinternet.com...
> > Anybody else notice that Oracle 8i+ creates TEMP files as sparse files
> > ?
>
> Yes. though not apparently on NT4.
>
> > It also adds it very quickly and oracle sees it as, eg 500mb, the
'ls -l'
> > Unix command sees it as 500Mb,
> > but the 'ls -s' doesn't, possibly saying 10Mb instead.
> >
> > When someone does a query that needs all the TEMP tablespace, it expands
> it,
> > possibly to the full 500Mb.
> > Which is fine, unless you've filled the filesystem up in the meantime.
> >
> > an OS 'cp' to 'cp' changes it to a normal file, but its still a bit naff
> and
> > dangerous.
>
> Not at all. It makes a great deal of sense from a backup and recovery
point
> of view. don't backup the temp ts and recreate it is quick and easy.
>
> as for filling up the filesystem putting non-oracle stuff on the same
> filesystem as oracle datafiles is the naff and bad bit surely.
>
> what about autoextend datafiles (with a limit of course). what about io
> contention. in short don't do it. set aside a file system for yor
datafiles.
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
>
>
Received on Thu Jul 04 2002 - 07:45:56 CDT
