Exp/imp and storage clause

Question

Is it possible to make an export of the database with the exp tool, but without the storage clause for tables and indexes?
My develop database is 2GB big, and when i make an export without data and import it in a clean production environment without data, the datafiles are also 2GB big.
The export parameter compress=Y/N doesn't matter.
Thanks

Answer 1

gert-jan, your post is unclear on by 2G big you mean the physical datafile size or the amount of space allocated within the tablespaces?
If you are allowing the import to create the tablespaces then they are going to have the same size as defined in test.
The compress=y/n option should make a difference in that the default compress=y would cause a larger value be written to the export file for the initial extent.
But an important question is how were the import database target tablespaces defined: dictionary or locally managed, uniform or auto-allocate.
If the tables were created with too large of allocations I would generate alter table move commands with storage clauses to resize the objects on the target. Then I would rebuild the indexes with storage clauses to do the same. You can change the initial extent size on a move/rebuild operation.
The version of Oracle is always important because Oracle has been known to change feature behavior and parameter default values with release changes.
HTH -- Mark D Powell --