Re: Export - Import question

Actually, I believe that if you have two 1Gbyte datafiles in a tablespace, the
contiguous space = (2Gbyte - 2blocks). This is the entire point of the tablespace/
datafile conceptual split -- to insulate you from the physical datafiles.

I tend to use compress=Y, but I also tend to do full cold backups before attempting
any massive defragmentation.

And no, you cannot edit the export file.

Diana Duncan
art2mis_at_apk.net

Minh Giang <mpg_at_fast.net> wrote in article <01bc0802$ef8d4160$1dd993cd_at_mpg>...
>
>
> Strategic Data Systems <sds_at_dataplusnet.com> wrote in article
> <5blafq$742$1_at_news.inc.net>...
> > In article <32DB5E36.1006_at_mf.sigov.mail.si>,
 jurij.modic_at_mf.sigov.mail.si
 says...
> > >
> > >Priya Tantry wrote:
> > >>
> > >> I am trying to do a full export import of the database because te
> > >> tablespaces are highly fragmented
> > >>
> > >> Is it a good idea to have compress=N set or leave the default
 compress=Y
> > >> while doing a full export / import
> > >>
> > >> Thanks
> > >> Priya Tantry
> > >> University of Queensland
> > >
> >
> >
> > Beware that you will need to have contiguous tablespace to accomodate
 the
> > the largest table. If I recall, if you have 2 datafiles of 1 GByte/ea
 for a
> > tablespace, you only have 1 GByte of contiguous tablespace. So a
 2Gbyte
> > table that was exported with COMPRESS=Y, will fail on the initial
 create
> > table statement.
> >
> >
>
> What will you do in that situation if you can't make your largest
 datafile
> to fit the initial extent of the import?
> I know this situation might never happen, but just curious what other
> workaround is possible. Can you edit the export file?
>
> TIA
> --
> Minh Giang
> mpg_at_fast.net
>
>
Received on Fri Jan 24 1997 - 00:00:00 CST