Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: migrated and chained row in a table

Re: migrated and chained row in a table

From: Allan Kelly <ac_kelly_at_bellsouth.net>
Date: Sun, 21 Mar 1999 17:14:19 GMT
Message-ID: <LN9J2.12634$Ek.12968004@news1.mia>


Well, let's say it's not good (maybe). For the table in question, compare ROWSIZE to DB_BLOCK_SIZE. If ROWSIZE is smaller than DB_BLOCK_SIZE you're OK. You just need to re-size the EXTENT parameters to more closely fit multiples of ROWSIZE. If your rows have LONG RAWS, you're outta luck. They are variable in size.

Usually, 10% will not produce a significant performance problem, but there are good third-party tools out there to alleviate the situation if it does. Platinum's "TsReorg" (http://www.platinum.com) or Quest's "Space Manager" (http://www.quests.com) are two good examples. Of course, you can also run the occasional EXPORT, TRUNCATE, IMPORT "drill" to accomplish the same thing.

Allan

Jean-François Vincent wrote in message <36F398F0.7F8642E9_at_platinum.com>...
>Hi
>
>I've got more than 10% of migrated of chained rows in a table
>is it acceptable ?
>if not how to resolve the problem ?
>
>thanks.
>
>J-Fr.
>
Received on Sun Mar 21 1999 - 11:14:19 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US