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 : 26-04-2017
ORA-29954

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

  • ora-31000 : Resource 'string' is not an XDB schema document
  • ora-39764 : specified stream is not in the specified direct path context
  • ora-23364 : Feature not enabled: Advanced replication
  • ora-02801 : Operations timed out
  • ora-25151 : Rollback Segment cannot be created in this tablespace
  • ora-23376 : node string is not compatible with replication version "string"
  • ora-37143 : (XSSQLMDQ03) string is not a valid analytic workspace name.
  • ora-10575 : Give up restoring recovered datafiles to consistent state: out of memory
  • ora-14293 : Number of partitioning columns does not match number of subpartitioning columns
  • ora-08116 : can not acquire dml enough lock(S mode) for online index build
  • ora-30377 : table string.MV_CAPABILITIES_TABLE not found
  • ora-16532 : Data Guard broker configuration does not exist
  • ora-13609 : The specified task string must be executing to be cancelled or interrupted.
  • ora-14626 : values being added already exist in DEFAULT subpartition
  • ora-13753 : "SQL Tuning Set" "string" already exists for user "string".
  • ora-26717 : SCN limit reached
  • ora-09946 : File name too long for buffer
  • ora-21500 : internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-10618 : Operation not allowed on this segment
  • ora-36883 : (XSSRF02) The first parameter of an AW single row function cannot be NULL.
  • ora-16192 : Primary and standby network integrity mismatch
  • ora-39173 : Encrypted data has been stored unencrypted in dump file set.
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • ora-07844 : sllfop: LIB$GET_VM failure
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-12514 : TNS:listener does not currently know of service requested in connect descriptor
  • ora-13437 : GeoRaster metadata blocking error
  • ora-39219 : directory object name is too long
  • ora-06929 : CMX: error when sending ORACLE_SID
  • ora-06912 : CMX: write error in datarq
  • 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.