You can also pre-create the objects on your side with the extent sizes you'd
like. Import with IGNORE=Y. You might have the client run a script to gen
dynamic sql for this, and have them send it w/the dmp file to pre-create the
objects. I've done this to increase extents on the import side of things.
"Susan Lam" <susana73_at_hotmail.com> wrote in message
news:7186ed56.0209301718.4fd7ca41_at_posting.google.com...
> I got a dmp file from a business partner and I need to import it to
> our database. The dmp file is only 1M but after I import it occupies
> 1GB! The reason is they set the initial extent of all tables, index
> to 20M even they don't have much data at all. I tried make the
> tablespace locally manage with "autoallocate" or "uniform size" before
> importing but it does not help.
>
> Is there any way to fix the initial extent size? The only way I know
> is edit/modify all the tables/indexes script to change the extent size
> before importing but I do not want to do it.
>
> Thanks,
> Susan
Received on Tue Oct 01 2002 - 09:46:14 CDT
