Re: Export/Import Effects of doing just one table???

diamonds2_at_aol.com (Diamonds2) wrote:
>We are running under O7.1.3 and have a table that has 7962 chained rows.
>What we decided to do is to export and import this one table. I need to
>know what are the problems we should look out for. Will the export
>util take care of the indices, and possible contraints of this table? Or
>is there
>another method to compress the extents on this one table without export
>and import. Will import destroy the old table?
>
>Thanks for you help
>Please email me at work: faha_at_eci-esyst.com
>Felicia A. Hemingway

There is another way to remove chained rows in a table. The Administrator's Guide provides good instructions on how to accomplish this in chapter 22, beginning on page 22-7 - at least in my copy of the manual.

Exporting and importing the table can work as well. Follow the guidelines in the utilities manual for exp and imp to make sure you keep your indexes and constraints. There are parms for just about everything you'd want. Also, I usually drop the table after a successful export so that I can import the table. So, I guess in a way import wipes out the old table.

I suppose the real issue here is, why are you getting so many chained rows. You should look at the PCTFREE on your table. If you're suffering a lot of updates, which may be causing your chaining, you should probably increase your PCTFREE parm. Otherwise, you'll just keep fixing it every now and again...

-Mark

-- 
***********************************************************************
* Pickwick Software Co., Portland, Oregon (USA), ORACLE Specialists   *
* Mark Fontenot (mark_at_pickwick.com) & Ally McEvoy (ally_at_pickwick.com) *
***********************************************************************