RE: ** chained rows fixing

Can someone let me know if there any downside to killing a 'ALTER TABLE move..' statement? Your help is appreciated. Thanks

A Joshi <ajoshi977_at_yahoo.com> wrote:Hi,

   I assume 'ALTER TABLE move ...' will fix it and will not affect ORacle Advanced replication or MV/MV logs etc. I read on asktom that all I need to do after 'ALTER TABLE.. ' is rebuild indexes. Thanks again for help.

A Joshi <ajoshi977_at_yahoo.com> wrote:
Thanks to Christian Antognini, Paul Drake, Mladen Gogala, Mark Fanham, Ric Van Dyke, Allen Brandon, David Sharples and everybody for your help.  

I assume a 'ALTER TABLE move should fix the current chained (migrated rows). For future prevention I have set the PCT_FREE higher. Thanks

Christian Antognini <Christian.Antognini_at_trivadis.com> wrote: Hi

>I need to get rid of chained rows for some tables.

As David told you, you have to find out if they are chained, migrated or both.

If they are chained only a larger block size can solve the problem without reviewing your database design. If you cannot solve the problem you may reduce its impact by placing infrequently accessed large columns "at the end" of the table, in fact only the needed row pieces are read.

HTH
Chris

New Features Oracle Database 10g Release 2 seminars @ www.trivadis.com Italiano: Lugano (24-Nov)
Français: Genève (17-Nov)
Deutsch: Zürich (11-Oct), Hamburg (13-Oct), München (20-Oct), Basel (25-Oct), Frankfurt (27-Oct), Bern (8-Nov), Düsseldorf (23-Nov), Stuttgart (13-Dec)

--
http://www.freelists.org/webpage/oracle-l


---------------------------------
Yahoo! for Good
Click here to donate to the Hurricane Katrina relief effort. 

---------------------------------
Yahoo! for Good
Click here to donate to the Hurricane Katrina relief effort. 

		
---------------------------------
Yahoo! for Good
 Click here to donate to the Hurricane Katrina relief effort. 
--
http://www.freelists.org/webpage/oracle-l