Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Extent Management 101
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
Received on Mon Aug 09 2004 - 20:00:14 CDT
![]() |
![]() |