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 : 27-06-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-37114 : OLAP API bootstrap error: (string)
  • ora-24080 : unschedule_propagation pending for QUEUE string and DESTINATION string
  • ora-19106 : invalid XQueryX: expected string - got string
  • ora-00258 : manual archiving in NOARCHIVELOG mode must identify log
  • ora-23387 : replication parallel push dequeue error
  • ora-31476 : a change table data column is missing from the source table
  • ora-25454 : error during evaluation of rule set: string.string for iterator: string
  • ora-07569 : slspool: $CLOSE failure
  • ora-02155 : invalid DEFAULT tablespace identifier
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-31666 : Master process string had an unhandled exception.
  • ora-29321 : too many datafiles added since the point-in-time
  • ora-25296 : Queue Table string has a buffered queue string
  • ora-01704 : string literal too long
  • ora-36922 : (XSVPMVTOPART03) workspace object is the target of an external partition of a partitioned variable.
  • ora-02081 : database link is not open
  • ora-04097 : DDL conflict while trying to drop or alter a trigger
  • ora-22889 : REF value does not point to scoped table
  • ora-22981 : must specify a table/view having system generated OID
  • ora-01636 : rollback segment 'string' is already online
  • ora-24070 : cannot upgrade queue table string while it is being downgraded
  • ora-28024 : must revoke grants of external roles to this role/user
  • ora-28027 : privileged database links may be used by global users
  • ora-31230 : DBMS_LDAP: unable to dynamically allocate additional memory
  • ora-02421 : missing or invalid schema authorization identifier
  • ora-33450 : (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.
  • ora-01412 : zero length not allowed for this datatype
  • ora-09853 : snyRemovePort: bad return code from request.
  • ora-01093 : ALTER DATABASE CLOSE only permitted with no sessions connected
  • ora-10841 : Default un-inintialized charact set form to SQLCS_IMPLICIT
  • 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.