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

Home -> Community -> Usenet -> c.d.o.misc -> Re: Problem: database table/index sizing for Sum Length Columns greater than Available Data Space

Re: Problem: database table/index sizing for Sum Length Columns greater than Available Data Space

From: Sybrand Bakker <postmaster_at_sybrandb.demon.nl>
Date: Mon, 26 Jul 1999 20:17:52 +0200
Message-ID: <933013059.12599.0.pluto.d4ee154e@news.demon.nl>


Sorry, but this is just the way Oracle works. If your records are by design bigger than the available dataspace, you will get chaining. If this is a structural problem in your database the only way to resolve it is to increase the block size. There might be formulas, but you definitely don't want the chaining, as you will be getting more than one 1 I/O to retrieve a record.

Hth,

Sybrand Bakker, Oracle DBA

Brendan Newman <bis_at_ibm.net> wrote in message news:379c4cd5_at_news1.us.ibm.net...
> Hi there,
>
> I am trying to size Oracle 8.x tables and am having difficulty due to
> the fact that the formulas Oracle gives are only appropriate if your Space
> Used Per Row (i.e. Sum Length Columns + Overhead) is less than your
> Available Data Space (i.e. Block_Size - Header Space - Pct_Free_Space).
>
> What if Space Used Per Row >= Available Data Space? That is, what if
> you have big columns which are much bigger than your block size and you
> don't want to increase the block size?
>
> If you could point me to where there are formulas for this particular
> case please let me know. Thanks. My e-mail is bis_at_ibm.net.
>
>
Received on Mon Jul 26 1999 - 13:17:52 CDT

Original text of this message

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