From: Fred Puhan <f_puhan@precise.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: maximum size of an extent
Organization: Precise Software Solutions
References: <3cff2d51$1_1@news.vo.lu>
User-Agent: MT-NewsWatcher/3.2 (PPC Mac OS X)
Date: Thu, 06 Jun 2002 16:03:12 -0400
Message-ID: <f_puhan-E1B714.16031206062002@vienna7.his.com>
NNTP-Posting-Host: pcp02139607pcs.reston01.va.comcast.net
X-Trace: vienna7.his.com 1023393792 pcp02139607pcs.reston01.va.comcast.net (6 Jun 2002 16:03:12 -0400)
Lines: 20
X-Authenticated-User: fjp
Path: news.easynews.com!easynews!priapus.visi.com!news-out.visi.com!hermes.visi.com!nntp1.roc.gblx.net!nntp.gblx.net!nntp.gblx.net!vienna7.his.com!f_puhan
Xref: easynews comp.databases.oracle.server:149787
X-Received-Date: Thu, 06 Jun 2002 13:00:43 MST (news.easynews.com)

In article <3cff2d51$1_1@news.vo.lu>, "GR" <guy.rodesch@cie.etat.lu> 
wrote:

> Hello,
> We use Oracle 8.1.7.2 as the database of our SAP R/3 46C system. Could we
> limit the maximum size of an extent in the init<SID>.ora configuration file?

Extent growth is controlled by the values specified in the CREATE 
statement in a cascading hierarchy:  first at the table/object level, 
then at the tablespace level, and finally using Oracle defaults.

If you want to limit the maximum size of a single extent, use a 
combination of NEXT and PCTINCREASE 0 values in the CREATE statement.  
This will tell Oracle to use the value of NEXT, if at all possible when 
extending a segment.  Doing so, however, may cause another value to come 
into play, and that's the MAXEXTENTS value set at the tablespace, if not 
UNLIMITED.

-- 
The underscore character does not belong in my address. You know the drill...
