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

Sujata, 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. Onload does not work very well for the full database. It is effective for databases if the full database is in a single dbspace. There is no control of specifying which table needs to go to which dbspace. dbexport/dbimport may be used for this. Dilip Kikla ssoman@omm.com wrote: > > Hi all, > In my efforts to de-fragment my biggest tables, I have come up with a > problem. I "onunload" - ed my table to tape, created new dbspaces to hold the > new table. The next step therefore is to drop my old table, and "onload" the > table back into the new dbspaces. But, HOW do I specify the first and next > extent sizes, since onload creates the table as opposed to loading the data into > a created table ? I do not see a parameter for first and next extent sizes on > the "onload" syntax, so how then does "onload" work ? Also, how can I specify > multiple dbspaces for "onload" to load data ?? > Secondly, how do I verify that my "onunload" is good ? I have taken an > ontape level 0 backup also. Is there any other backup method that I should use, > incase onunload fails ?? My table is quite large - about 8 Gig. > Thanks for the help > > Sujata > ***************************************** > Sujata Soman > > > E-Mail: ssoman@omm.com > > O'Melveny & Myers, Los Angeles > > ******************************************