ORA-14080: partition cannot be split along the specified high bound

Cause : User attempted to split a partition along a bound which either collates higher than that of the partition to be split or lower than that of a partition immediately preceding the one to be split

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

Ensure that the bound along which a partition is to be split collates lower than that of the partition to be split and higher that that of a partition immediately preceding the one to be split

update : 29-06-2017

ORA-14080 - partition cannot be split along the specified high bound
ORA-14080 - partition cannot be split along the specified high bound

  • ora-12854 : Parallel query is not supported on temporary LOBs
  • ora-13015 : the window definition is not valid
  • ora-30179 : invalid argument index used in a format code
  • ora-24005 : must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-09218 : sfrfs: failed to refresh file size
  • ora-24850 : failed to startup shared subsystem
  • ora-25255 : incorrect subscription string string
  • ora-12003 : materialized view "string"."string" does not exist
  • ora-00308 : cannot open archived log 'string'
  • ora-02239 : there are objects which reference this sequence
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-19622 : archivelog thread string sequence string not restored due to string
  • ora-02487 : Error in converting trace data
  • ora-32339 : cannot alter materialized view with the PMOP
  • ora-34296 : (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
  • ora-32333 : disable table scn update for Materialized view
  • ora-09285 : sllfop: unrecognizable processing option, incorrect format
  • ora-01127 : database name 'string' exceeds size limit of string characters
  • ora-23613 : Script string already exists
  • ora-16177 : media recovery is not required
  • ora-36314 : (PHYS01) workspace object must be a dimension, relation or variable.
  • ora-22826 : cannot construct an instance of a non instantiable type
  • ora-19211 : column 'string', specified as key using DBMS_XMLSTORE.setKeyColumn() , must be of scalar type
  • ora-19012 : Cannot convert XML fragment to the required datatype
  • ora-26575 : remote database does not support replication parallel propagation
  • ora-13348 : polygon boundary is not closed
  • ora-30439 : refresh of 'string.string' failed because of string
  • ora-30767 : OID type mismatch
  • ora-23483 : object "string"."string" not allowed in this operation.
  • 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.