Scaling down an Import

[Peer Jones]

Hi There,

I have to import a dumpfile with tables that are practically empty but have gigantic initial extents, therefore taking up loads of unnecessary disk space.

Does anyone know how to import this file while disrgarding the initial extent values so that it fits into a small DB instance?

Thanks
Peer

[anandkl]

Hi,
First you need to do an import which write all the DDL into a file, then edit the file to set small INITIAL and NEXT value and do the complete import. The import parameter used for this option in "indexfile"

imp username/password file=export.dmp fromuser= touser= indexfile=

regards
anandkl

[OracleDoc]

I would hope you're using LMT's

[slimdave]

You could just edit the fiule with a decent editor -- UltraEdit is good on Windows

[jmodic]

Originally posted by OracleDoc
I would hope you're using LMT's

This by itself will not make any difference regarding the space allocation for imported segments.

[Peer Jones]

Thanks for you help, Guys, but the problem has been solved, meaning the import request has been cancelled.

[OracleDoc]

Originally posted by jmodic
This by itself will not make any difference regarding the space allocation for imported segments.

It would if you didn't specify storage para'ms in the table create.

[jmodic]

Originally posted by OracleDoc
It would if you didn't specify storage para'ms in the table create.

No matter if you did/didn't specify it at table create time - when you exported the table the current setting of the INITIAL are written into that dump file. And regardless if you subsequently import that table into a LMT or DMT, the imp utility will creat that table by alocating (at least) as much space in the target tablespace as it is stated for the INITIAL in the exp dump file for that taable.

The only solution for the original problem is to precreate table before the import, regardles of wether LMT or DMT is used.