Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!attbi_feed3!attbi.com!attbi_s03.POSTED!not-for-mail
Reply-To: "Daniel Trickett" <drtrickett@yahoo.com>
From: "Daniel Trickett" <Daniel.Trickett@oracle.com>
Newsgroups: comp.databases.oracle.server
Subject: Tablespace Fragmentation during a rebuild
Lines: 19
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <FeoCb.517426$Tr4.1438947@attbi_s03>
NNTP-Posting-Host: 24.147.34.186
X-Complaints-To: abuse@comcast.net
X-Trace: attbi_s03 1071255589 24.147.34.186 (Fri, 12 Dec 2003 18:59:49 GMT)
NNTP-Posting-Date: Fri, 12 Dec 2003 18:59:49 GMT
Organization: Comcast Online
Date: Fri, 12 Dec 2003 18:59:49 GMT
Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:250008

Hi,

I have a 5g tbs containing just indexes. I am moving these indexes to a
different
tablespace that is currently empty. I generated a script to do an alter
rebuild,
where I compress to single extent, and use parallel option of 8 and
nologging.
The target tbs grows to 15g during the rebuild and upon examination, I find
that the indexes where not built using contiguous space. I thought that I
had
done this before and they were contiguous. Is the parallel option the
culprit ?

Thanks for any feedback.

Dan