ORA-14646: Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes

Cause : The first time a table is altered to include compression, it cannot have a usable bitmap index (partition). Subsequent alter table statements involving compression do not have this same restriction.

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

A) Drop any bitmap indexes defined on the table, and re-create them once the operation is complete or, B) Mark all index fragments of all bitmap indexes defined on the table UNUSABLE and rebuild them once the operation is complete.

update : 24-04-2017
ORA-14646

ORA-14646 - Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
ORA-14646 - Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes

  • ora-06405 : NETCMN: reset protocol error
  • ora-13390 : error in spatial analysis and mining function: [string]
  • ora-13870 : Database-wide SQL tracing is not enabled
  • ora-12729 : invalid character class in regular expression
  • ora-13214 : failed to compute supercell for window object
  • ora-07562 : sldext: extension must be 3 characters
  • ora-00288 : to continue recovery type ALTER DATABASE RECOVER CONTINUE
  • ora-36628 : (XSAGMODLIST03) MODEL workspace object could not be added to AGGMAP workspace object.
  • ora-07236 : slemop: open error.
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-19601 : output file is string string (string)
  • ora-15012 : ASM file 'string' does not exist
  • ora-37178 : column string has no values
  • ora-28107 : policy was disabled
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-30976 : invalid Parent Order Key Index option for XML Index
  • ora-02439 : Unique index on a deferrable constraint is not allowed
  • ora-13835 : invalid attribute name specified
  • ora-13062 : topology IDs do not match in the feature table and the topology
  • ora-28236 : invalid Triple DES mode
  • ora-13916 : Invalid value "string" specified for parameter "string"
  • ora-12851 : PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, string
  • ora-13401 : duplicate entry for string in USER_SDO_GEOR_SYSDATA view
  • ora-24804 : Lob read/write functions called while another OCI LOB read/write streaming is in progress
  • ora-19654 : must use backup control file to switch file incarnations
  • ora-32311 : materialized view definition query selects an unsupported user-defined type
  • ora-31023 : Index size error
  • ora-02090 : network error: attempted callback+passthru
  • ora-29830 : operator does not exist
  • ora-23611 : tablespace "string" has more than one data file
  • 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.