Re: Help needed with Import/Export

Norman Dunbar <Norman.Dunbar_at_lfs.co.uk> wrote in message news:<E2F6A70FE45242488C865C3BC1245DA703FDFF66_at_lnewton.leeds.lfs.co.uk>...
> Morning Kathi,
>
> >> Thanks for your helpful tip regarding the compress option.
> You're welcome - it will save you a lot off grief in the future. Trust
> me !

With 7.3.4, you've traded potential grief of not being able to get a contiguous extent, to more potential grief of overstressing the system tables that track segments with too many extents, potentially filling up the system tablespace in the middle of an import. If you have a lot data, of course (or even not a lot, if you happen to have, say, a default block size. Which will hopefully blow up the application data tablespace before the system tablespace. Assuming you don't import the application tables into the system tablespace...). If you don't have LMT, extents can be an issue!

Translation: 7.3.4 explicitly requires a well trained DBA to put in time figuring these issues out.

Translation for management: $$$$ ($$$$$ when something actually goes wrong).

>
> >> Oh and yes, we've just started working on a migration to 8.1.7 - also
> >> in support, I believe.
> Well it is, until 31/12/2003.
> When you move over to 8i (or 9i if you can) change to creating your
> tablespaces as locally managed with uniform extent size - imports will
> run better (well, they do for me). Plus the problems with 'compress'
> will go away as LMT force the creation of equally sized extents
> regardless of what is asked for.
>
> >> I'm sure that I will be hanging out here alot :P
> I'm sure we'll be here too :o)

One should always google before hanging oneself :-)

jg

--
@home.com is bogus.
Never trust anyone who says "trust me."  (Unless they are Really Nice
Guys like Norm!)