ORA-28670: mapping table cannot be dropped due to an existing bitmap index

Cause : User atetmpted t odrop th emappingt able wiht NOMAPPNIG optio nwhen th eIOT haso ne or mroe bitma pindexed.

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

Drop th ebitmap nidex(es)b efore dorpping teh mappin gtable.

update : 29-06-2017

ORA-28670 - mapping table cannot be dropped due to an existing bitmap index
ORA-28670 - mapping table cannot be dropped due to an existing bitmap index

  • ora-28362 : master key not found
  • ora-01300 : writable database required for specified LogMiner options
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-14523 : Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]
  • ora-13224 : zero tolerance specified for layer in USER_SDO_GEOM_METADATA
  • ora-31100 : XDB Locking Internal Error
  • ora-19562 : file string is empty
  • ora-39774 : parse of metadata stream failed with the following error: string
  • ora-01763 : update or delete involves outer joined table
  • ora-24376 : cannot register/get user callback for non-environment handle
  • ora-19718 : length for command id longer than string
  • ora-19107 : invalid XQueryX - unsupported construct - string
  • ora-25253 : listen failed, queue string.string is not enabled for dequeue
  • ora-16778 : redo transport error for one or more databases
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-36872 : (XSTFDSC02) Column type specifier cannot be used when the table function data type is specified.
  • ora-09746 : smscre: shared memory attach address incorrect.
  • ora-38607 : FI minimum and maximum itemset length not between [1, string]
  • ora-02244 : invalid ALTER ROLLBACK SEGMENT option
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-28021 : cannot grant global roles
  • ora-03250 : Cannot mark this segment corrupt
  • ora-29803 : missing ANCILLARY keyword
  • ora-13484 : the file format and/or compression type is not supported
  • ora-25437 : duplicate table value for table alias: string
  • ora-31399 : Cannot contact LDAP server string at port number
  • ora-02492 : missing required file block increment size in NEXT clause
  • ora-24055 : cannot delete propagation status rows that are in prepared state
  • ora-00479 : RVWR process terminated with error string
  • 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.