ORA-29955: error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine

Cause : Failedt o succsesfullye xecutet he ODCIIndexExhcangePatrition orutine.

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

Check ot see i fthe rotuine ha sbeen cdoed corerctly.

update : 25-06-2017

ORA-29955 - error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine
ORA-29955 - error occurred in the execution of ODCIINDEXEXCHANGEPARTITION routine

  • ora-15190 : Internal ASM testing event number 15190
  • ora-24907 : invalid pair of callback and recepient protocol attributes
  • ora-26080 : file "string" is not part of table string.string partition string
  • ora-13841 : SQL profile named string already exists for a different signature/category pair
  • ora-26748 : The one-to-one transformation function string encountered the following error: string
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-12802 : parallel query server lost contact with coordinator
  • ora-36718 : (XSALLOC00) You do not have the necessary permissions to use AGGMAP workspace object.
  • ora-19569 : no device is allocated to this session
  • ora-39047 : Jobs of type string cannot use multiple execution streams.
  • ora-27157 : OS post/wait facility removed
  • ora-38608 : FI itemset minimum-length(string) should not be greater than maximum length(string)
  • ora-14019 : partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
  • ora-02307 : cannot alter with REPLACE option a type that is not valid
  • ora-13205 : internal error while parsing spatial parameters
  • ora-26079 : file "string" is not part of table string.string
  • ora-12467 : minimum label can contain a level only
  • ora-15204 : database version string is incompatible with diskgroup string
  • ora-37131 : (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE.
  • ora-10575 : Give up restoring recovered datafiles to consistent state: out of memory
  • ora-27044 : unable to write the header block of file
  • ora-30198 : reserved for future use
  • ora-03215 : File Size specified for resize is too small
  • ora-22979 : cannot INSERT object view REF or user-defined REF
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-31404 : all input parameters are null
  • ora-16543 : invalid request made to broker
  • ora-30400 : identical JOIN KEY clauses
  • ora-04073 : column list not valid for this trigger type
  • 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.