Re: Storage parameters

OK, everybody re-read the compress= in the utilities manual. compress=n uses the current storage values, whatever they may be. Both may be far wrong if there have been many deletes, and if pctincrease <> 0, and especially if you later use the 9i exp option to select data.

Randy, this upgrade is an excellent opportunity for you to fix those strange values. When you do the import, you want to precreate the tables with the proper values. You can use exp/imp to create files with the commands to do that, then edit the files. You _don't_ care about trying to stuff everything into one extent. However, if you have large tables, it will help Oracle figure things out, if you use autoallocate - but Oracle will decide on a few sizes, not what you tell it. Whether you should use autoallocate depends on how many tables you have of varying sizes (as Mark pointed out, often most useful for vendor supplied tables).

Here is some more explanation:
http://www.dizwell.com/html/fragmentation.html

jg

-- 
@home.com is bogus.
http://www.orablogs.com/orablogs/