Re: Oracle Import: Behaviour on Table Initial Extent

From: Ronald <ronr_at_wxs.nl>
Date: Tue, 22 Jun 1999 6:37:32 +0200
Message-ID: <01HW.B394DFAC00020AB0123E5040@news.wxs.nl>

On Tue, 22 Jun 1999 5:46:30 +0200, Jonathan Gennick wrote (in message <378206fe.13670036_at_netnews.worldnet.att.net>):
>
> On Sun, 20 Jun 1999 20:51:27 +0800, "Yat-Fan" <fan.ho_at_alumni.ust.hk> wrote:
>

>> Here comes the problem when I have a large table with a large extent, 
>> imported to a "empty" database since the each datafile is smaller than 
>> the size of this extent. 

>
> If you hear of a solution, let me know too. I ran into this problem once,
> and never solved it.
>
> Jonathan
>
>

exp compress=n

prevents collections of all extents into one BIG extent. You can also get the ddl, edit it by hand run it through sql*plus and run imp ignore=y.

--

Ronald - certified Oracle DBA http://home.wxs.nl/~ronr/professional.html

       - unix/sa              http://www.tresco.nl/dcl.html

       - Middleware programmer/
                      designer    mailto:R.Rood_at_tresco.nl
 

Received on Mon Jun 21 1999 - 23:37:32 CDT