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 : 28-07-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-19907 : recovery time or SCN does not belong to recovered incarnation
  • ora-02718 : osnprs: reset protocol error
  • ora-36162 : (XSMXAGGR05) COUNTVAR variable workspace object must be of type INTEGER, not string.
  • ora-03263 : cannot drop the first file of tablespace string
  • ora-31493 : could not prepare session for LogMiner session
  • ora-31517 : CDC change table string.string already exists
  • ora-39501 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-19569 : no device is allocated to this session
  • ora-29905 : method string does not exist in type string.string
  • ora-32771 : cannot add file to bigfile tablespace
  • ora-25449 : invalid variable name: string
  • ora-02404 : specified plan table not found
  • ora-36884 : (XSSRF03) The value of the first parameter of the AW single row function is incorrect.
  • ora-08108 : may not build or rebuild this type of index online
  • ora-32761 : Turn off Temp LOB Ref Count Feature
  • ora-25269 : cant specify sognature with get signature option
  • ora-36836 : (XSLMGEN06) Dimension string.string!string hierarchy string level string is missing a PHYSICALNAME property value
  • ora-02158 : invalid CREATE INDEX option
  • ora-23501 : refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
  • ora-24128 : partition name specified for a non-partitioned object
  • ora-22898 : existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
  • ora-19587 : error occurred reading string bytes at block number string
  • ora-30103 : 'string' contains an illegal integer radix for 'string'
  • ora-31033 : Requested number of XML children string exceeds maximum string
  • ora-09982 : skxfqddrg: Error Removing a page from the SDI buffer pool
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-15052 : ASM file name 'string' is not in diskgroup "string"
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-31505 : cannot alter or drop predefined change set
  • ora-02368 : file string is not valid for this load operation
  • 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.