ORA-29954: domain index partition is marked LOADING/FAILED/UNUSABLE

Cause : An attempt has been made to access a domain index that is being built or is marked failed by an unsuccessful DDL or is marked unusable by a DDL operation.

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

Wait if the specified index partition is marked LOADING Rebuild the specified index partition if it is marked FAILED or UNUSABLE.

update : 27-05-2017
ORA-29954

ORA-29954 - domain index partition is marked LOADING/FAILED/UNUSABLE
ORA-29954 - domain index partition is marked LOADING/FAILED/UNUSABLE

  • ora-39111 : Dependent object type string skipped, base object type string already exists
  • ora-07425 : sdpri: error string in translating dump file location.
  • ora-24504 : data length larger than expected
  • ora-38310 : cannot purge tablespace for other users
  • ora-36258 : (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
  • ora-09710 : soarcv: buffer overflow.
  • ora-12803 : parallel query server lost contact with another server
  • ora-10852 : Enable tracing for Enqueue Dequeue Operations
  • ora-29853 : keyword UNIQUE may not be used in creating domain indexes
  • ora-24411 : Session pool already exists.
  • ora-16099 : internal error ORA-00600 occurred at standby database
  • ora-31462 : internal error while accessing metadata
  • ora-06720 : TLI Driver: SID lookup failure
  • ora-36681 : (XSDPART19) Partitions string and string are out of order.
  • ora-36982 : (XSRELGID03) The grouping variable/relation workspace object must be dimensioned by all dimensions of the source relation workspace object that have more than one value in status.
  • ora-12209 : TNS:encountered uninitialized global
  • ora-12333 : database (link name string) is not mounted
  • ora-00438 : %s Option not installed
  • ora-30683 : failure establishing connection to debugger
  • ora-30688 : maximum program calling depth exceeded
  • ora-27002 : function called with invalid device structure
  • ora-01668 : standby database requires DROP option for offline of data file
  • ora-16188 : LOG_ARCHIVE_CONFIG settings inconsistent with previously started instance
  • ora-16028 : new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
  • ora-00332 : archived log is too small - may be incompletely archived
  • ora-28274 : No ORACLE password attribute corresponding to user nickname exists.
  • ora-12728 : invalid range in regular expression
  • ora-07597 : spguns: $GETJPIW failure
  • ora-38454 : attribute set not defined for the column being indexed
  • ora-29285 : file write error
  • 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.