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-05-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-07257 : spdcr: translation error expanding program name.
  • ora-01877 : string is too long for internal buffer
  • ora-01274 : cannot add datafile 'string' - file could not be created
  • ora-00369 : Current log of thread string not useable and other log being cleared
  • ora-14067 : duplicate TABLESPACE_NUMBER specification
  • ora-15037 : disk 'string' is smaller than mimimum of string MBs
  • ora-00342 : archived log does not have expected resetlogs SCN string
  • ora-12658 : ANO service required but TNS version is incompatible
  • ora-19595 : archivelog string already included in backup conversation
  • ora-24068 : cannot start queue string, queue table string is being migrated
  • ora-28353 : failed to open wallet
  • ora-00317 : file type string in header is not log file
  • ora-24202 : publisher does not exist for the queue
  • ora-37060 : (XSMCSESS08) number is not a valid custom member in dimension workspace object.
  • ora-02737 : osnpcl: cannot tell orapop to exit
  • ora-19553 : device name string is invalid
  • ora-12734 : Instant Client Light: unsupported client national character set string
  • ora-19678 : RMAN configuration value exceeds maximum length of string
  • ora-13485 : error occurred during compression or decompression: string
  • ora-32616 : missing DIMENSION BY keyword in MODEL clause
  • ora-26011 : Cannot load type string into column string in table string
  • ora-12668 : Dedicated server: outbound protocol does not support proxies
  • ora-26021 : index string.string partition string loaded successfully with string keys
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-16062 : DGID from standby not in Data Guard configuration
  • ora-39164 : Partition string was not found.
  • ora-38798 : Cannot perform partial database recovery
  • ora-13023 : interior element interacts with exterior element
  • ora-25002 : cannot create INSTEAD OF triggers on tables
  • ora-30978 : The XML Index is not locally partitioned.
  • 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.