Re: Weird extent sizes in locally managed tablespace

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Mon, 15 Aug 2005 06:51:45 +0000 (UTC)
Message-ID: <ddpe21$sns$1@nwrdmz03.dmz.ncs.ea.ibs-infra.bt.com>

Was this a parallel create as select, or have you done a parallel insert append ?

If so, the strange sizes could be the result of each parallel slave trimming its final extent.

-- 
Regards

Jonathan Lewis

Now waiting on the publishers:    Cost Based Oracle - Volume 1

http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users' FAQ

http://www.jlcomp.demon.co.uk/appearances.html
Public Appearances - schedule updated 8th July 2005







"rjlolli" <rjlolli_at_sbcglobal.net> wrote in message 
news:1123092037.555860.321690_at_g44g2000cwa.googlegroups.com...


>I created a tablespace with the following parameters.

>

> extent management local autoallocate

> segment space management auto

>

> Under this setting Oracle will extend in increments of 64k, 1m, 8m, and

> finally 64m based on the size of the segment.  I'm seeing a table that

> was extending 8m at a time, but Oracle threw in a 3m extent and a 5m

> extent.  Can anyone explain this weird behavior?

>

> The tablespace only has 1 datafile and the datafile has never been

> extended.

>

> extent_id    bytes            blocks

>

>  97.00     8388608.00        1024.00

>  98.00     8388608.00        1024.00

>  99.00     8388608.00        1024.00

> 100.00     8388608.00        1024.00

> 101.00     5242880.00         640.00

> 102.00     8388608.00        1024.00

> 103.00     5242880.00         640.00

> 104.00     8388608.00        1024.00

> 105.00     3145728.00         384.00

> 106.00     8388608.00        1024.00

> 107.00     8388608.00        1024.00

>

Received on Mon Aug 15 2005 - 01:51:45 CDT