ORA-29951: warning in the execution of ODCIINDEXSPLITPARTITION routine

Cause : Aawnrni gaw serutnrdef or mht eDOICnIedSxlptiaPtrtioi nortuni.e

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

hCce kots eei fht eortuni eah sebnec dodec roertcylC ehkcu es rpscefiei dol gatlbsef rog ertared teia.l

update : 25-09-2017

ORA-29951 - warning in the execution of ODCIINDEXSPLITPARTITION routine
ORA-29951 - warning in the execution of ODCIINDEXSPLITPARTITION routine

  • ora-19278 : Invalid value: (string) for type: (string)
  • ora-19371 : invalid update option
  • ora-25101 : duplicate REBUILD option specification
  • ora-16417 : Activation occurred after recovery from standby redo log files; a full database backup is required
  • ora-12583 : TNS:no reader
  • ora-24061 : cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero
  • ora-29872 : parameters clause cannot be combined with the specified options
  • ora-01124 : cannot recover data file string - file is in use or recovery
  • ora-19599 : block number string is corrupt in string string
  • ora-16133 : Datafile string has incorrect terminal recovery stamp.
  • ora-31515 : CDC change source string already exists
  • ora-38311 : cannot purge objects owned by other users
  • ora-12818 : invalid option in PARALLEL clause
  • ora-37012 : (XSACQUIRE_TIMEOUT) Object workspace object is locked by another user and the WAIT timed out.
  • ora-40002 : wordsize must be string or greater
  • ora-29873 : warning in the execution of ODCIINDEXDROP routine
  • ora-24348 : Update or Delete without Where
  • ora-13765 : Value "string" is illegal for a result limit.
  • ora-01091 : failure during startup force
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-06912 : CMX: write error in datarq
  • ora-25116 : invalid block number specified in the DUMP DATAFILE/TEMPFILE command
  • ora-07753 : slemcf: fseek before write failure
  • ora-02080 : database link is in use
  • ora-24159 : invalid variable definiton
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-01155 : the database is being opened, closed, mounted or dismounted
  • ora-25261 : JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
  • ora-36808 : (XSTBLFUNC04) The OLAP_TABLE function LEVELREL clause cannot declare number ADT fields from number AW fields.
  • ora-06800 : TLI Driver: SQL*Net SPX client went away during reconnect
  • 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.