Path: news.easynews.com!easynews!news.he.net!news-hog.berkeley.edu!ucberkeley!newsfeed.stanford.edu!postnews1.google.com!not-for-mail From: mark.powell@eds.com (Mark D Powell) Newsgroups: comp.databases.oracle.misc Subject: Re: maximum size of an extent Date: 6 Jun 2002 07:27:32 -0700 Organization: http://groups.google.com/ Lines: 29 Message-ID: <178d2795.0206060627.7f8eb2e4@posting.google.com> References: <3cff2644_2@news.vo.lu> NNTP-Posting-Host: 199.228.142.8 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1023373652 12619 127.0.0.1 (6 Jun 2002 14:27:32 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 6 Jun 2002 14:27:32 GMT Xref: easynews comp.databases.oracle.misc:82579 X-Received-Date: Thu, 06 Jun 2002 07:25:05 MST (news.easynews.com) "GR" wrote in message news:<3cff2644_2@news.vo.lu>... > 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.ora configuration file? > > > Thanks in advance, > Guy. There is no such init.ora parameter; however, if you create your tablespaces using local uniform extent management then you can make every extent in the tablespace one size. Storage clause parameters, if provided on the table or index create, are ignored in this case. If you go with autoallocate then the largest extent size I am sure Oracle will use is 64M, but it may well go larger as some posters think they have managed to produce 256M in testing (but did not have test results to check for verification). The current algorithm requires the object to take 200 extents before it switches to using 64M. If you are using dictionary managed space then I suggest you set pctincrease to 0 and use max_extents to limit the object size. You can monitor the extent count in dba_segments and manually allocate a large next extent that will fit in the target tablespace, while you consider conversion to local space management or just trying to standard the object extent sizes to minimize free space fragmentation under Dictionary management. HTH -- Mark D Powell --