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 : 17-08-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-01491 : CASCADE option not valid
  • ora-15083 : failed to communicate with ASMB background process
  • ora-01453 : SET TRANSACTION must be first statement of transaction
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-23446 : duplicate template site
  • ora-13911 : Threshold not found
  • ora-07639 : smscre: SGA pad area not large enough (string bytes required)
  • ora-28292 : No Domain Policy registered for Kerberos based authentication
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-23431 : wrong state: string
  • ora-14265 : data type or length of a table subpartitioning column may not be changed
  • ora-29886 : feature not supported for domain indexes
  • ora-12810 : PARALLEL_MAX_SERVERS must be less than or equal to string
  • ora-24415 : Missing or null username.
  • ora-40211 : algorithm name string is invalid
  • ora-36810 : (XSTBLFUNC05) Analytic workspace object number does not exist.
  • ora-26020 : index string.string loaded successfully with string keys
  • ora-26097 : unsupported conversion for column string (from type number to type number)
  • ora-38456 : The attribute set "string" is in an inconsistent state.
  • ora-19104 : invalid XQueryX: missing attribute string
  • ora-26082 : load of overlapping segments on table string.string is not allowed
  • ora-02784 : Invalid shared memory ID specified
  • ora-01201 : file string header failed to write correctly
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-23444 : duplicate template parameter
  • ora-13213 : failed to generate spatial index for window object
  • ora-12592 : TNS:bad packet
  • ora-16178 : Cannot specify remote destinations in archivelog manual mode
  • ora-19652 : cannot apply offline-range record to datafile string: file is fuzzy
  • ora-38201 : assert if pin during flush
  • 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.