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 : 27-06-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-29661 : Unable to find the superclass of the defined in the EXTERNAL NAME
  • ora-13516 : AWR Operation failed: string
  • ora-19768 : USING clause only valid with ENABLE CHANGE TRACKING
  • ora-13776 : User "string" has not been granted the "SELECT" privilege on the "SQL tuning set" DBA views.
  • ora-13046 : invalid number of arguments
  • ora-13432 : GeoRaster metadata blankCellValue error
  • ora-12574 : TNS:redirection denied
  • ora-26055 : Invalid buffer specified for direct path unload
  • ora-13637 : Executing or modifying task string is disallowed until the task is reset to its initial state.
  • ora-24389 : Invalid scrollable fetch parameters
  • ora-02077 : selects of long columns must be from co-located tables
  • ora-07824 : sspain: $SETIMR failure
  • ora-27481 : "string.string" has an invalid schedule
  • ora-22343 : Compilation error for type invalidated by ALTER TYPE
  • ora-19043 : Multiply nested XMLROOT function disallowed
  • ora-07596 : sptpa: $GETJPIW failure
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-22860 : object type expected
  • ora-12711 : this CREATE CONTROLFILE character set is not allowed
  • ora-08186 : invalid timestamp specified
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-12616 : TNS:no event signals
  • ora-14171 : cannot specify clause in CREATE|ALTER TABLE
  • ora-30087 : Adding two datetime values is not allowed
  • ora-14257 : cannot move partition other than a Range or Hash partition
  • ora-29824 : operator is invalid
  • ora-12589 : TNS:connection not bequeathable
  • ora-12708 : error while loading create database NLS parameter string
  • ora-12336 : cannot login to database (link name string)
  • ora-25964 : column type incompatible with join column type
  • 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.