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: Extent Management 101

Re: Extent Management 101

From: Anurag Varma <avdbi_at_hotmail.com>
Date: Tue, 10 Aug 2004 01:29:23 GMT
Message-ID: <TxVRc.128286$bp1.8156@twister.nyroc.rr.com>

"Howard J. Rogers" <hjr_at_dizwell.com> wrote in message news:opschrqocc3d8uqx_at_shostakovich.dizwell.com...
> On Tue, 10 Aug 2004 00:45:16 GMT, Anurag Varma <avdbi_at_hotmail.com> wrote:
>
> [snip]
>
> >
> > It seems that you remember the error incorrectly.
> > The closest match to what you say is:
> >
> > ORA-28604 "table too fragmented to build bitmap index (%s,%s,%s)"
> > // *Cause: The table has one or more blocks that exceed the maximum
> > number
> > // of rows expected when creating a bitmap index. This is
> > probably
> > // due to deleted rows. The values in the message are:
> > // (data block address, slot number found, maximum slot allowed)
> > // *Action: Defragment the table or block(s). Use the values in the
> > message
> > // to determine the FIRST block affected. (There may be others).
> >
> > This has nothing to do with tablespace fragmentation.
> > The solution to the above problem is to exp the table ... truncate it
> > ... create bitmap index and then import the table.
>
>
> Er, just a thought: he could simply 'alter table X move;' and that should
> fix up any table mess he has (assuming he has the space, of course). Then
> create the bitmap index.
>
> Of course, moving a table requires all existing indexes to be rebuilt too.
>
> Regards
> HJR
I agree ...
Alter table move should work too :)
I'm not entirely sure .. but even the alter table .. minimize records_per_block might fix the problem too..

Anurag Received on Mon Aug 09 2004 - 20:29:23 CDT

Original text of this message

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