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: Maxextents = 2 billion?

Re: Maxextents = 2 billion?

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Sat, 30 Jan 1999 08:34:35 -0000
Message-ID: <917685688.6238.0.nnrp-12.9e984b29@news.demon.co.uk>


This could be a compatibility issue.

It seems unlikely, but is it possible that someone managed to run the system temporarily with

    compatibility=7.3+
to create the unlimited extents, but the system is now running at a lower compatibility ? This does tend to result in the sort of behaviour you are seeing.

Jonathan Lewis
Yet another Oracle-related web site: www.jlcomp.demon.co.uk

Van Messner wrote in message ...
>Hello Andy:
>
> Thanks to you and the others who answered. I thought that maxextents
>had a limit
>which was platform dependedent - 121 or 249 or whatever. Is this not true?
>If it is true
>how does Oracle treat a limit of 2 billion?
> In terms of crashing the server. Each time I tried to rebuild an index
>with one of the
>enormous limits, it crashed. Every other index rebuilt without any
>problems - none of them
>had maxextents set larger than 249.
>
>Van
>
>
>Andy Johnson wrote in message <36B14FFA.A3933EB7_at_accesscom.net>...
>>Van Messner wrote:
>>
>>> I started work at a site with ten out of tune instances. I was
>looking
>>> for objects which had thrown extents and found more than a thousand with
>>> over 50 extents each.
>>> As I started to look at the worst of them I discovered ten had
>>> maxextents set to 2.nnnE+09. I was surprised that Oracle accepted a
>value
>>> this high. Can anyone explain why this is allowed?
>>> Trying to rebuild these indexes resulted in a server crash for each
>>> attempt. I ended up dropping them and making new ones.
>>> My guess is that someone was entering storage parameters for
>maxextents
>>> = 249 and hit the "e" key which is just below the "4" key.
>>>
>>> Thanks for any info
>>>
>>> Van
>>
>>When a table is created with maxextents unlimited, the number is actually
>set
>>to 2^31, so, no, it's not a mistake, just bad practice. I usually set
mine
>to
>>200, so at least if something breaks and starts using space like crazy it
>>won't use all of it before I can fix it. I have some automated apps
(third
>>party) that do this once a blue moon (actually, the next blue moon is this
>>weekend, so I have a lot to look forward to).
>>
>>Andy Johnson
>>
>>
>
>
Received on Sat Jan 30 1999 - 02:34:35 CST

Original text of this message

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