Re: TBUNLOAD/TBLOAD

In article 29m5jkINNqbl@emory.mathcs.emory.edu, GENED@FAB4.intel.com ("Gene Dershewitz X26216, AL3-59") writes: >I have a need to move a rather large table and it would be more convenient to >use the tbunload utility (judging from the documentation). The questions I have >regards the reloading of the unloaded table. > >1. If the table currently has multiple extents, will the newly load table >contain 1 extent which is the total of all the extents or will the individual >extents be retained? > >2. Will the NEXT SIZE be retained on load? > >3. Are there any gotchas I need to watch out for using these utilies? > From my experience using tbunload/tbload they do an image load and unload. I have only used it to unload/load a whole DB. Extent sizes and fragmentation seem to be saved along with the data. Because it seems to do an image unload/load the file it creates it much larger than the actual data. I have found that if you are doing a single table unload/load, just use SQL to unload to flat file, recreate your table with extent size you need (calculated by tbcheck -pe), re/create your table with proper extent sizes, and load. Informix is smart, if you load a table using the "load from" command it will initially read all your data into a single extent (as free space allows). It seems to leave some space for data growth, but I am not how much. --- Kurt Kessel American Automobile Association kurt@aaa.com