ORA-29853: keyword UNIQUE may not be used in creating domain indexes

Cause : An attempt was made to create a domain index with the UNIQUE attribute.

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

Remove UNIQUE from the CREATE INDEX statement.

update : 26-05-2017
ORA-29853

ORA-29853 - keyword UNIQUE may not be used in creating domain indexes
ORA-29853 - keyword UNIQUE may not be used in creating domain indexes

  • ora-12062 : transaction string received out of sequence from site string
  • ora-16185 : REMOTE_ARCHIVE_ENABLE and LOG_ARCHIVE_CONFIG mutually exclusive
  • ora-09265 : spwat: error temporarily suspending process
  • ora-23352 : duplicate destination for deferred transaction
  • ora-19700 : device type exceeds maximum length of string
  • ora-03263 : cannot drop the first file of tablespace string
  • ora-27503 : IPC error attempting to cancel request
  • ora-37015 : (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
  • ora-31492 : could not set session parameters for LogMiner session
  • ora-36978 : (XSRELGID01) workspace object must be a self-relation.
  • ora-14153 : only one of STORE IN or clause may be specified
  • ora-26507 : null master connection
  • ora-00110 : invalid value string for attribute string, must be between string and string
  • ora-38746 : error occurred while restoring data block (file# string, block# string)
  • ora-27093 : could not delete directory
  • ora-33052 : (XSAGDNGL25) AGGMAP workspace object is a dimensioned AGGMAP; it can only be used to aggregate like-dimensioned variables.
  • ora-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-23345 : table "string"."string" not registered to collect statistics
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-39038 : Object path "string" is not supported for string jobs.
  • ora-14645 : STORE IN clause cannot be specified for Range List objects
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-09828 : SCLFR: atomic latch return error.
  • ora-19726 : cannot plug data [string] at level string into database running at compatibility level string
  • ora-23420 : interval must evaluate to a time in the future
  • ora-31518 : change column string already exists in CDC change table string.string
  • ora-30023 : Duplicate undo tablespace specification
  • ora-07645 : sszfsl: $CHANGE_CLASS failure
  • ora-03292 : Table to be truncated is part of a cluster
  • ora-12851 : PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, 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.