Reducing table initial extent size for subset of production

I inherited an export/import process to create a subset of production data for development and QA use. It's consistently running out of space.

The goal is to create a duplicate production database on a test platform, delete rows and/or truncate specific tables, export the tables and data, and import the reduced-volume tables.

In reviewing the MetaLink doc 61949.1 Export and Import Bulletin, it's saying COMPRESS will alter the initial size to be the currently allocated size, despite the contents or lack thereof. This explains why I'm running out of space, even after deleting a significant portion of the data.

To reach my goal of smaller tables, do I have to 1) export without compression, 2) preallocate all 200+ tables, and 3) import, or is there another way? If I have to preallocate the tables, does someone have SQL to generate the DDL statements, including the size math to recalucluate the tables smaller?

Any input is appreciated. Thanks.

Linda Hagedorn Received on Fri Jun 16 2000 - 12:17:03 CDT