RE: automatic extent allocation

  • From: "Powell, Mark D" <mark.powell@xxxxxxx>
  • To: "Oracle-L@Freelists. Org (E-mail)" <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 7 Jan 2005 16:09:45 -0500

From the version 9.2 Reference Manual:

 Default value
 Derived from tablespace default storage or DB_BLOCK_SIZE initialization
I was thinking that "Unlimited" actually corresponds to 2 billion.  In any
case it is a lot and probably more than enough for most shops.

HTH -- Mark D Powell --

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Roger Xu
Sent: Friday, January 07, 2005 3:53 PM
To: Jonathan Lewis; Oracle-L@Freelists. Org (E-mail)
Subject: RE: automatic extent allocation

So the suggestion would be to move it to its
own tablespace with uniform extent allocation?
What is Oracle 9i's limit as far as the number
of extents in a table? Thanks.
-----Original Message-----
From: Jonathan Lewis [ mailto:jonathan@xxxxxxxxxxxxxxxxxx]
Sent: Friday, January 07, 2005 2:33 AM
To: Roger Xu; Oracle-L@Freelists. Org (E-mail)
Subject: Re: automatic extent allocation

In the first place, I would consider moving the
object out of the current tablespace (or move
everything else out of the tablespace) because
it sounds like nothing else should be sharing that
tablespace.  (Consider the problem of recovering
the entire tablespace because one of the other tables
gets a corrupt block - if you can't take advantage
of rman block level recovery).

Secondly, at 3GB per month, I would consider
partitioning the table at something like one partition
per month - thus making your question moot.

It sounds like your object is still using 64MB
extents - it would be interesting to see if there
is another step size when you hit a total of 64GB,
or whether you keep going at 50 extents per month.

I suspect the problems you __might__ get from having
2,000 extents are much less significant than the problems
you __might__ get if you have a 100GB segment by the end
of next year.


Jonathan Lewis
The Co-operative Oracle Users' FAQ
Public Appearances - schedule updated Dec 23rd 2004

Other related posts: