Could the Pro*C be doing updates after initial insert?
Try putting percent free around 50 and lowering percent used to about 10 and
see what happens. If it is updates causing it, this would make your table
bigger, but not lots! bigger.
why317_at_my-deja.com wrote in message <833v72$vkv$1_at_nnrp1.deja.com>...
>(Oracle 7.3.4.4.1 on HP-UX v10.20)
>I have a table that continually fills up all available extents much too
>early. According to my calculations, the table should be holding 265
>records per block, but instead the average seems to be around 37. I
>would ordinarily question my sizing calculations, but when I create a
>duplicate table and use a string of inserts to copy the data from one to
>the other, and it fits in the initial extent. The code looks like this:
> insert into PM1_R2
> select * from PM1_R1 where TEST_DATE between
> to_date ('1999.0101.0000.00','YYYY.MMDD.HH24MI.SS') and
> to_date ('1999.0101.2359.59','YYYY.MMDD.HH24MI.SS');
>(...repeating for each day of the month.)
>
>The table is loaded using Pro*C (author is long gone). I have not had
>this problem with tables holding up to 12,000,000 rows under Oracle
>v7.3.3.5, but under this latest revision, the table fills up after less
>than 2,000,000 rows.
>
>I've tried decreasing PCTFREE from 10 to 5, but this seemed to make the
>problem worse.
>
>Any ideas, comments or war stories are welcome.
>
>
>Thanks,
>Bill
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
Received on Tue Dec 14 1999 - 22:27:41 CST
