ORA-14032: partition bound of partition number string is too high

Cause : High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal.

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

Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition.

update : 23-08-2017

ORA-14032 - partition bound of partition number string is too high
ORA-14032 - partition bound of partition number string is too high

  • ora-31417 : column list contains control column string
  • ora-09273 : szrfc: error verifying role name
  • ora-31016 : Attempted to delete entry without name
  • ora-24390 : Unsupported scrollable cursor operation
  • ora-02058 : no prepared transaction found with ID string
  • ora-37175 : column string is not a column of source data
  • ora-13333 : invalid LRS measure
  • ora-26023 : index string.string partition string was made unusable due to:
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-19656 : cannot backup, copy, or delete online log string
  • ora-38484 : FUNCTION/PACKAGE/TYPE string does not exist
  • ora-39026 : master table is inconsistent on validation string
  • ora-22153 : source variable-length array is not initialized
  • ora-02229 : invalid SIZE option value
  • ora-27162 : thread creation failed
  • ora-34357 : (MXDSS10) string is not an alias of analytic workspace string.
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • ora-24780 : cannot recover a transaction while in an existing transaction
  • ora-24384 : Application context size is not initialized
  • ora-02457 : The HASH IS option must specify a valid column
  • ora-24018 : STOP_QUEUE on string failed, outstanding transactions found
  • ora-38719 : Invalid DUMP FLASHBACK object.
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-24328 : illegal attribute value
  • ora-15190 : Internal ASM testing event number 15190
  • ora-36165 : (XSAGGCNTPROP) Variable workspace object cannot have both an AGGCOUNT and the $COUNTVAR property.
  • ora-24307 : invalid length for piece
  • ora-10561 : block type 'string', data object# string
  • ora-28004 : invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
  • ora-39751 : partitioned table on both sides of PARTITIONED OUTER JOIN is not supported
  • 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.