Re: dbexport/dbimport problems

> Did you use the SQL that dbexport generated directly without editing it? > Dbexport/dbimport looses all manner of useful information. Including, for > example, extent sizes, table locations in specific dbspaces and lock > mode. > If you do nothing, the tables all get created in the root dbspace, with > page mode locking and an extent size of 8 pages. This tends to be pretty > non-optimal :-) Not quite. dbexport/ dbimport set the first extent size to the current data volume and the next extent size to 50% of that value. So extent fragmentation would only be a problem if your data has been extremely volatile since you did the import. You could always run tbcheck -pe to make sure. It's the other factors - especially putting everything on the same drive as the logical logs, ooh, nasty, which I'd be watchful of. Someone reminded me that if you have 6.00 or later, dbexport has a "-ss" option to preserve everything to the letter. akent@cix.compulink.co.uk (Andy Kent) -------------------------------------