Re: chained rows

Interesting:
a) How many columns in the table -

        add 5 bytes row overhead, plus 1 byte per column,
        3 bytes for any columns defined as more than 254 characters long
        still won't quite get you there.

b)    Are you using SQL*Load in direct mode to populate the table ?
        There is a bug in direct load which can make it waste space.

c)    Can you do block dumps to see if the rows are chained or migrated ?
        is it really EVERY row, or nearly every row ?

--
Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

I have a spelling chequer
It came with my pea sea
It plainly marques for my revue
Miss steaks eye cannot sea

I've run this poem threw it
I'm shore your pleased to no
Its letter perfect in it's weigh
My chequer tolled me so

chuckh_at_safeplace.net wrote in message <7bmh13$o7g$1_at_nnrp1.dejanews.com>...
>I have a table who's avg_row_len is 1718 bytes and who's percent free is
10%.
>According to Oracle's formula, with a 2k block size, I should have 1762
bytes
>available in each block. But every row in the table is chained! This is not
an
>issue where rows grew to that size. Every column is a CHAR and NOT NULL so
the
>row size is constant from the time the row is inserted, until the time it's
>deleted.
Received on Fri Mar 05 1999 - 15:32:18 CST