On Sep 5, 1:09 pm, Andrea <netsecur..._at_tiscali.it> wrote:
> Hi,
>
> i was reading some paper related on clustering factor, this column
> aimed to identified if the rows of a table are synchronized (ordered)
> with the index.
> If i don't mistake, the value of clustering_factor have to approached
> to number of blocks of the table and more far away from number of
> rows.
>
> So, if i have understood well, main indications on this column are:
>
> 1) if c factor is lower than blocks, maybe the table could have
> problems of fragmentation because of many DML statements (insert and
> delete)
>
> 2) if c factor is higher than blocks and it approach to num_rows, then
> the rows in the index are not ordered (not sync with the index).
>
> In first case: is SHRINK the table a method for resolve the problem?
> In second case: rebuild index resolve order of the rows ?
>
> Or, for both case the only best method is truncate and reinsert all
> rows?
>
> thanks for your advice and opinions.
> bye
> --
> Andrea
> ( a guy that tries to become to DBA)
The best method is to bother only when it will *resolve* anything.
Otherwise you are embarking on an exercise in futility and getting
paid for wasting your and your employers time.
--
Sybrand Bakker
Senior Oracle DBA
Received on Wed Sep 05 2007 - 06:58:45 CDT
