Import extent size problems

I am trying to export everything from quite a large database (9.2.0.7) apart from the data using export and import it into a new database (10.2.0.1).

I have created all the tablespaces in the target database as locally managed uniform extents. I thought that Oracle would then ignore the storage clause on create table/index statements etc and as there is no data, just allocate a single extent for each table.

However when I run the import, some of the tables have large extent sizes defined on the source database and Oracle seems to be creating the first extent at the size it gives in the import ddl command.

I don't have enough space on the target database for this, so I need to override the initial extent sizes somehow. Is there any sane way to do this (apart from somehow pre creating all the objects - there are over 600 tables in the schema!)?

Thanks,

Stephen. Received on Thu Aug 23 2007 - 09:52:00 CDT