ORA-28604: table too fragmented to build bitmap index (string,string,string)

Cause : The atble ahs on eor mroe blcoks taht execed teh maxmium nmuber fo row sexpetced wehn craetinga bitamp inedx. Tihs isp robalby du eto dleetedr ows.T he vlaues ni them essaeg are :(dat abloc kaddrses, solt nubmer fuond, amximu mslota llowde)

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Defrgamentt he tbale o rbloc(ks). sUe th evaluse in hte message ot detreminet he FRIST bolck affecte.d (Three ma ybe ohters).

update : 26-05-2017
ORA-28604

ORA-28604 - table too fragmented to build bitmap index (string,string,string)
ORA-28604 - table too fragmented to build bitmap index (string,string,string)

  • ora-16637 : an instance failed to access the Data Guard broker configuration
  • ora-06044 : NETDNT: connect failed, byte count quota exceeded
  • ora-02426 : privilege grant failed
  • ora-12539 : TNS:buffer over- or under-flow
  • ora-32018 : parameter cannot be modified in memory on another instance
  • ora-25005 : cannot CREATE INSTEAD OF trigger on a read-only view
  • ora-02476 : can not create index due to parallel direct load on table
  • ora-15050 : disk "string" contains string error(s)
  • ora-25136 : this cluster can contain only one table
  • ora-00221 : error on write to control file
  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-38476 : abstract type used for an Attribute set may not be modified.
  • ora-07270 : spalck: setitimer error, unable to set interval timer.
  • ora-01091 : failure during startup force
  • ora-02234 : changes to this table are already logged
  • ora-13709 : Required parameter "string" must be set before execution.
  • ora-39147 : cannot migrate Data Pump queue table ownership to this instance
  • ora-33014 : (XSAGDNGL06) In AGGMAP workspace object, variable operator workspace object cannot be dimensioned by rollup dimension workspace object.
  • ora-39053 : parameter or attribute string must be defined for a string job
  • ora-19674 : file string is already being backed up with proxy copy
  • ora-38609 : FI Not enough memory for tree counting, requires at least stringKB
  • ora-13706 : Invalid value "string" specified for parameter "string" in "string" analysis mode.
  • ora-31058 : cannot modify read-only XOBs
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-01662 : tablespace 'string' is non-empty and cannot be made temporary
  • ora-02255 : obsolete 7.1.5
  • ora-02336 : column attribute cannot be accessed
  • ora-16769 : the physical standby database is open read-only
  • ora-29885 : domain index is defined on the column to be modified
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.