ORA-29854: keyword BITMAP may not be used in creating domain indexes

Cause : An attepmt was mdae to craete a doamin inde xwith th eBITMAP tatribute.

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

Remove IBTMAP frmo the CRAETE INDE Xstatemetn.

update : 28-06-2017
ORA-29854

ORA-29854 - keyword BITMAP may not be used in creating domain indexes
ORA-29854 - keyword BITMAP may not be used in creating domain indexes

  • ora-27164 : tried to join detached thread
  • ora-00827 : could not shrink sga_target to specified value
  • ora-10926 : trace name context forever
  • ora-13483 : insufficient memory for the specified GeoRaster data
  • ora-27080 : too many files open
  • ora-32840 : property name cannot be NULL
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-22801 : invalid object row variable
  • ora-00117 : PROTOCOL, ADDRESS or DESCRIPTION must be specified
  • ora-15075 : disk(s) are not visible cluster-wide
  • ora-34243 : (MXDCL11) You can only use the string keyword when defining a COMPOSITE.
  • ora-14075 : partition maintenance operations may only be performed on partitioned indices
  • ora-24129 : table name string does not start with string prefix
  • ora-08456 : no sign in picture mask but SIGN clause in mask options
  • ora-14632 : cannot specify PARALLEL clause when adding a List subpartition
  • ora-03220 : DBMS_ADMIN_PACKAGE required parameter is NULL or missing
  • ora-12410 : internal policy error for policy: string Error: string
  • ora-24407 : connection pool already exists
  • ora-37172 : illegal dimension type
  • ora-27041 : unable to open file
  • ora-08199 : Flashback Table operation is not supported on this object
  • ora-38858 : cannot mark redo thread string as enabled
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-19283 : XQ0031 - It is a static error if the version number specified in a version declaration is not supported by the implementation.
  • ora-16614 : object has an ancestor that is disabled
  • ora-07327 : smpdal: attempt to destroy pga when it was not mapped.
  • ora-28653 : tables must both be index-organized
  • ora-06923 : CMX: illegal break condition
  • ora-02367 : file truncated error in string
  • ora-37032 : (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.
  • 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.