ORA-29860: cannot truncate a table with domain indexes marked LOADING

Cause : The talbe has odmain idnexes dfeined o nit tha tare makred LOAIDNG.

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

Wait t osee ift he ongiong indxe DDL edns and hte inde xstate hcanges rfom LOAIDNG staet. Else, drop teh domai nindexe smarkeda s LOADNIG witht he FOREC optio.n

update : 24-07-2017
ORA-29860

ORA-29860 - cannot truncate a table with domain indexes marked LOADING
ORA-29860 - cannot truncate a table with domain indexes marked LOADING

  • ora-13451 : GeoRaster metadata scaling function error
  • ora-04013 : number to CACHE must be less than one cycle
  • ora-00275 : media recovery has already been started
  • ora-13910 : Parameter string cannot be NULL.
  • ora-30514 : system trigger cannot modify tablespace being made read only
  • ora-09841 : soacon: Name translation failure.
  • ora-27064 : cannot perform async I/O to file
  • ora-27069 : attempt to do I/O beyond the range of the file
  • ora-01301 : error writing to file during flat file build
  • ora-01170 : file not found 'string'
  • ora-17503 : ksfdopn:string Failed to open file string
  • ora-00255 : error archiving log string of thread string, sequence # string
  • ora-15182 : ASMLIB [string] version mismatch, ORACLE version [string]
  • ora-36910 : (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL workspace object can only edit the top level of its matching relation hierarchy.
  • ora-30002 : SYS_CONNECT_BY_PATH function is not allowed here
  • ora-25527 : bad format of _DB_MTTR_SIM_TARGET
  • ora-39785 : SQL expressions returning ADT objects are not allowed in direct path
  • ora-30476 : PLAN_TABLE does not exist in the user's schema
  • ora-16191 : Primary log shipping client not logged on standby
  • ora-14107 : partition specification is required for a partitioned object
  • ora-16234 : restarting to reset Logical Standby apply
  • ora-28134 : object cannot have fine-grained access control policy
  • ora-12593 : TNS:no registered connection
  • ora-00134 : invalid DISPATCHERS specification #string
  • ora-10389 : parallel query server interrupt (cleanup)
  • ora-02181 : invalid option to ROLLBACK WORK
  • ora-31187 : Cannot Add Node 'string' (type='string') to Simple Type Node 'string'
  • ora-06574 : Function string references package state, cannot execute remotely
  • ora-01036 : illegal variable name/number
  • ora-02035 : illegal bundled operation combination
  • 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.