RE: ORA 28604 - table is too fragmented

I'm glat that helped. I'm curious now as to what would happen if you changed the pctfree on the existing table to a lower value (which would allow more records per block in new blocks allocated to one of the extents of the table) - would you eventually get an error on an insert because the bitmap index would think the table is too "fragmented"? Or would the bitmap index become invalid? I guess I could try it myself but I've never seen this ORA-28604 error. I will try to see if I can make it happen on one of my databases.

-----Message d'origine-----
De : oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] De la part de genegurevich_at_discoverfinancial.com Envoyé : mardi, 22. mai 2007 09:16
À : Jacques Kilchoer
Cc : oracle-l_at_freelists.org
Objet : RE: ORA 28604 - table is too fragmented

This seems to work. Thank you very much ! I have been able to build all indices without problems and run exchange with a partitioned table with no issues (so far) after increasing the pctfree parameter

             "Jacques                                                      
             Kilchoer"                                                     
             <Jacques.Kilchoer                                          To 
             @quest.com>               <genegurevich_at_discoverfinancial.com 


                                       >                                   

Yes, I understood that, but if one way to allow the creation of the bitmap index is having less records per block (wasn't that the whole point of resetting the hakan factor?), you can accomplish that goal with pctfree.

--
http://www.freelists.org/webpage/oracle-l