ORA-14628: specification of bounds is inconsistent with LIST method

Cause : An operation such as ALTER TABLE SPLIT|ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method

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

Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions

update : 25-04-2017
ORA-14628

ORA-14628 - specification of bounds is inconsistent with LIST method
ORA-14628 - specification of bounds is inconsistent with LIST method

  • ora-22993 : specified input amount is greater than actual source amount
  • ora-30367 : a JOIN KEY clause is required
  • ora-29519 : name string resolved via a synonym in schema string to a class with a different name
  • ora-01931 : cannot grant string to a role
  • ora-21523 : functionality not supported by the server (object mode only)
  • ora-15066 : offlining disk "string" may result in a data loss
  • ora-23413 : table "string"."string" does not have a materialized view log
  • ora-23452 : flavor string of object group "string"."string" is already published
  • ora-13752 : User "string" must be SYS or must have the "ADMINISTER ANY SQL TUNING SET" privilege.
  • ora-14062 : one or more of table's partitions reside in a read-only tablespace
  • ora-01002 : fetch out of sequence
  • ora-16139 : media recovery required
  • ora-38707 : Media recovery is not enabled.
  • ora-08463 : overflow converting decimal number to Oracle number
  • ora-17618 : Unable to update block 0 to version 10 format
  • ora-12441 : policy string already exists
  • ora-12841 : Cannot alter the session parallel DML state within a transaction
  • ora-08319 : sllfsk: Error reading file
  • ora-01629 : max # extents (string) reached saving undo for tablespace string
  • ora-33003 : (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP.
  • ora-30439 : refresh of 'string.string' failed because of string
  • ora-25532 : MTTR specified is too large: string
  • ora-02461 : Inappropriate use of the INDEX option
  • ora-16241 : Waiting for gap logfile (thread# string, sequence# string)
  • ora-13401 : duplicate entry for string in USER_SDO_GEOR_SYSDATA view
  • ora-26026 : unique index string.string initially in unusable state
  • ora-02150 : invalid new tablespace name
  • ora-31160 : max substitution group size string exceeded by "string" (string) for head element "string" (string)
  • ora-01283 : Options specified is invalid
  • ora-02292 : integrity constraint (string.string) violated - child record found
  • 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.