Re: Moving a table

I think this is what your looking for... alter fragment on table <mytable> init in <newdbspace>

MIKE MAGIE Remember, if the table has too many lines, maybe you'll receive the message "no more locks" .... The good thing is disable logging for the database , move the table to new dbspace using the statement above from "dgriffen" and after that enable logging as you're using early ... Best Regards Roberto FERRONATO > To: ids@iiug.org > From: dgriffen@finishline.com > Subject: Re: Moving a table [12022] > Date: Wed, 7 May 2008 17:13:56 -0400 > > I think this is what your looking for... > > alter fragment on table <mytable> init in <newdbspace>> > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > _________________________________________________________________ Connect to the next generation of MSN Messenger http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmai ltagline

Roberto, I've moved a 76 million row, 5.5 million page table with this command on an instance configured with 2 million locks. I've never had a problem with "no more locks". The command looks to be grabbing an exclusive table lock. However, I have run into long transaction abort with this command. If your able to safely switch the logging status as you suggest, I'm sure that would be a good solution. If you can't afford to turn of logging, you need to make sure you have room to insert all records into the new dbspace, delete all records from the old dbspace, and handle all your other activity within your LTXHWM % of Logical Logs. Regards, Dave Griffen