Re: dba_extents slow workaround
From: Michael Austin <maustin_at_firstdbasource.com>
Date: Mon, 04 May 2009 16:39:04 -0500
Message-ID: <t7JLl.17803$D32.1011_at_flpi146.ffdc.sbc.com>
HansPeter wrote:
>> Mladen Gogala wrote:
>>> On Wed, 29 Apr 2009 19:06:15 -0500, Michael Austin wrote:
>>>> Are you using DMT or LMT?
>>>> ASM? Raw? Cooked?
>>> Probably not DMT in 10.2.
>> Ya never know... I had systems at my previous gig that were upgraded
>> from 8i->9i->10.2.0.4 and was still using DMT even though I all but beat
>> them up to get it updated.
>>
>>
>>
>> - Tekst uit oorspronkelijk bericht niet weergeven -
>>
>> - Tekst uit oorspronkelijk bericht weergeven -
>
> All tablespaces are locally managed on ASM.
Date: Mon, 04 May 2009 16:39:04 -0500
Message-ID: <t7JLl.17803$D32.1011_at_flpi146.ffdc.sbc.com>
HansPeter wrote:
> On 1 mei, 17:40, Michael Austin <maus..._at_firstdbasource.com> wrote:
>> Mladen Gogala wrote:
>>> On Wed, 29 Apr 2009 19:06:15 -0500, Michael Austin wrote:
>>>> Are you using DMT or LMT?
>>>> ASM? Raw? Cooked?
>>> Probably not DMT in 10.2.
>> Ya never know... I had systems at my previous gig that were upgraded
>> from 8i->9i->10.2.0.4 and was still using DMT even though I all but beat
>> them up to get it updated.
>>
>>
>>
>> - Tekst uit oorspronkelijk bericht niet weergeven -
>>
>> - Tekst uit oorspronkelijk bericht weergeven -
>
> All tablespaces are locally managed on ASM.
This is the real question I should have asked... what problem are you really trying to solve because while LMT uses an "extent" term, its definition and usage is very different from that of the traditional Oracle definition. The way the Area BitMap and SPAceManagement pages work, worrying about extent coalescing is a moot point. Which is one reason why some of those traditional tablespace qualifiers are ignored. Received on Mon May 04 2009 - 16:39:04 CDT