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-05-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-25452 : duplicate attribute value for variable: string, attribute: string
  • ora-09931 : Unable to open ORACLE password file for reading
  • ora-19806 : cannot make duplex backups in recovery area
  • ora-29293 : A stream error occurred during compression or uncompression.
  • ora-37082 : Invalid percent
  • ora-13055 : Oracle object string does not exist in specified table
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-32409 : materialized view log on "string"."string" already excludes new values
  • ora-30191 : missing argument list
  • ora-35019 : (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions.
  • ora-30752 : column or table string is not substitutable
  • ora-25209 : invalid value string, EXPIRATION should be non-negative or NEVER
  • ora-01564 : rollback segment is not PUBLIC
  • ora-23327 : imported deferred rpc data does not match string of importing db
  • ora-16212 : number processes specified for APPLY is too great
  • ora-10651 : incorrect file number block number specified
  • ora-13835 : invalid attribute name specified
  • ora-01982 : invalid auditing option for tables
  • ora-22977 : missing or invalid attribute
  • ora-12221 : TNS:illegal ADDRESS parameters
  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-08274 : Out of memory for environment variable
  • ora-19597 : file string blocksize string does not match set blocksize of string
  • ora-19335 : Invalid format type object
  • ora-25201 : invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
  • ora-25222 : enqueue failed, complete sender info. not provided for a queue supporting non-repudiation
  • ora-25268 : didnt dequeue in browse mode with get signature option
  • ora-00438 : %s Option not installed
  • ora-16814 : incorrect redo transport setting for AlternateLocation for standby database
  • ora-10662 : Segment has long columns
  • 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.