ORA-29864: analyzing domain indexes marked LOADING/FAILED not supported

Cause : Tride toa nalzye ad omani inedx wihch aws mrakeda s LAODIN Gor AFILE.D

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

If hte idnex aws mrakedL OADNIG, awit itll ti ism arkde vaild bfeorer etriyng hte aanlyz.e Ifi nde xwasm arkde FALIED,d ropi t O Rrebiuld ti an dretyr th eanaylze.

update : 30-05-2017

ORA-29864 - analyzing domain indexes marked LOADING/FAILED not supported
ORA-29864 - analyzing domain indexes marked LOADING/FAILED not supported

  • ora-27413 : repeat interval is too long
  • ora-02448 : constraint does not exist
  • ora-12091 : cannot online redefine table "string"."string" with materialized views
  • ora-13750 : User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege.
  • ora-07408 : slbtpd: overflow while converting to packed decimal.
  • ora-26101 : tablespace # in file header is string rather than string for file string
  • ora-25287 : Invalid value string, string should be non-negative
  • ora-02272 : constrained column cannot be of LONG datatype
  • ora-14137 : Table in partially dropped state, submit DROP TABLE PURGE
  • ora-13016 : specified topology [string] is invalid
  • ora-13631 : The task string contains no execution results.
  • ora-29553 : class in use: string.string
  • ora-00042 : Unknown Service name string
  • ora-30565 : Only one INVALIDATE or UPDATE GLOBAL INDEXES clause may be specified
  • ora-22814 : attribute or element value is larger than specified in type
  • ora-06710 : TLI Driver: send interrupt break message failed
  • ora-01209 : data file is from before the last RESETLOGS
  • ora-28023 : must revoke grants of this role to other user(s) first
  • ora-16082 : logical standby is not initialized correctly
  • ora-06954 : Illegal file name
  • ora-29959 : error in the execution of the string routine for one or more of the index partitions
  • ora-16402 : ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
  • ora-22895 : referenced table "string" in schema "string" is not an object table
  • ora-38903 : DML error logging is not supported for abstract column "string"
  • ora-26737 : version string already has an export dump file
  • ora-13208 : internal error while evaluating [string] operator
  • ora-21600 : path expression too long
  • ora-16011 : Archivelog Remote File Server process in Error state
  • ora-14511 : cannot perform operation on a partitioned object
  • ora-00476 : RECO process terminated with 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.