Re: Problem Importing data

If your initial and next extents are not same as that of Original tablespace , then , the space required for the import can vary a lot , because if you initial extent is lets say, 10 in Original tablespace and 20 in the import tablespace then the then there could be a lot of difference in extent allocation and so ultimately on blocks, even if the pctincrease is same.
To my understanding is that allocation of extent do affect the number of blocks consumed.

So make sure that your initial extent and next are excatly the same as that of the original tablesapce.

Faheem,

In article <3a1b141c$0$19423$7f31c96c_at_news01.syd.optusnet.com.au>,   "Kevin" <kevin_at_pacificdbms.com.au> wrote:
> I have exported 2 schemas proddta (1.6 Gb) and prodctl (40 Mb) with
> compress=n. I truncate testdta and testctl schemas which have all same
> tables as prod schemas. When I attempt to import the data using
> fromuser=proddta touser=testdta, the tablespace blows out at 2.5 Gb
 and most
> of the large tables fail to import. This means that the total import
 would
> exceed approx double that of the source schema size. I have checked
> pctincrease and pctfree on a selection of the tables, particularly the
> larger tables. They appear to be the same as for the production
 schema. The
> only difference I can detect is that the initial and next are
 different but
> I would think that that would only change the number of extents and
 not the
> number of data blocks.
>
> How can I get this import to resemble the prod data?
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Tue Nov 21 2000 - 19:06:10 CST