Re: Migrating from Oracle 7.3.4 to Oracle 9.2.0.6

Raj, Actually with locally managed tablespace, LMT, using auto-allocate or uniform extents the initial storeage value does affect the storage allocation used by Oracle. In the case of uniform extents Oracle will allocate as many uniform extents as necessary to hold the initial extent request. With auto-allocate the initial extent can affect the extent size chosen. So I suggest the use of compress=n on the export so that on import each object takes as few extents as will work to hold the data.

I strongly suggest you do some analysis of how the objects would look if you used uniform extent tablespaces. With a few object relocations generally two different extent size choices will handle all your objects with a managable number of extents. Then predicting when you need to add a file, relocate an object, or take other action to manage space becomes very simple.

Auto-allocate is great for housing vendor products that dump eveything into one tablespace, but free space fragmentation problems can still occur in auto-allocate tablespaces while in a uniform extent tablespace no such problem can exist.

HTH -- Mark D Powell -- Received on Mon Apr 18 2005 - 06:35:55 CDT