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: Oracle Max # extents reached

Re: Oracle Max # extents reached

From: Jeremiah Wilton <jeremiah_at_wolfenet.com>
Date: Mon, 5 Oct 1998 08:54:57 -0700
Message-ID: <Pine.OSF.3.95.981005084933.23443A-100000@gonzo.wolfenet.com>


On Mon, 5 Oct 1998 adiska_at_my-dejanews.com wrote:
>
> Is it possible to update a single value, even if the table is already full?
> Does it matter, that the value I am trying to reset was initially set to an
> automatic default value when the row was created?

It sounds like the new value in the update requires slightly more storage than the previous value. Oracle is finding no free space in the block where the row resides, so it tries to create another row in a new block (called "row chaining"). Unfortnately, if the table is "full," a new extent must be allocated.

If you find this mechanism unacceptible, you can set a higher PCTFREE parameter when you create the table. This will force Oracle to leave a certain percent of each block free for future growth of the row, such as your update. This will reduce the possibility of chaining a row at update time.

--
Jeremiah Wilton http://www.wolfenet.com/~jeremiah Received on Mon Oct 05 1998 - 10:54:57 CDT

Original text of this message

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