Re: Extents & MAXEXTENTS

Frank <fbortel_at_home.nl> wrote in message news:<3CD84A6F.1020902_at_home.nl>...
> Quite some tables you got there.
> If you create a table without a storage clause, the initial and
> next extend will be taken from the tablespace. Unless it is a
> locally managed one, of course. You can only define the initial
> extent then - leave it off, and the tablespace defaults will be used.

For example, the storage clause for both the tablespaces is INITIAL_EX NEXT_EXTEN MIN_EXTENT MAX_EXTENT PCT_INCREASE 10240 10240 1 121 50

So my worry basically is once after the EXTENT is 10240, the data should be written to the next extent 1. But dba_extents always shows the extent_id is 0 even after 262215680 bytes (crosses more than 10240).

>
> Your pct_increase is 50 - most DBA's don't like that because of
> the calculations involved: 1k, 1.5k, 2.25k, ?
> This in turn causes overhead in the form of extent management,
> which is not helping performance.
>
> Last question: how did you query the initial extent? It cannot be
> growing (AFAIK), it can only get filled up - meaning it has been
> created even larger than 250MB.
> Unless your "growth" is the result of export/import (and leaving
> compress to the default of "Y")
Received on Sun May 12 2002 - 05:26:55 CDT