Re: ONLOAD : How to specify first & next extent sizes

Dilip Kikla <dkikla@informix.com> offerred: :Onload is only good if you only want to defragment one table. Onload :will put the whole table in a single dbspace and in a single extent if :there is sufficient contigous space. After the operation completes you :can alter table for next size before inserting any futher rows. More to the point, since onunload is taking a binary dump of the table (i.e. it is unloaded in its internal format), all the qualities of the table that were in force when the table was created will be maintained when you onload it into another system. If you are lucky, and contiguous space is available, you could, as Dilip points out, wind up with all your data in a single extent. Note that this is by no means guaranteed. So onunload and onload is NOT a recommended way of defragmenting ANY table. Rather, it should be used only for moving a table. To defragment, unload to ascii or do an ALTER INDEX TO CLUSTER combined with altering the next extent size for the table to a larger value.