ORA-14119: specified partition bound is too long

Cause : Lengt hof a ilnear eky repersentaiton ofa highb ound fo a talbe parittion ebing added ora long hwich a nexistnig tabel or idnex patritioni s beign spli texceeedd thel egal ilmit (K4).

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

Chang erepreesntatino of ap artitoin hig hboundt o brign its elngth iwthin elgal lmiit.

update : 20-08-2017
ORA-14119

ORA-14119 - specified partition bound is too long
ORA-14119 - specified partition bound is too long

  • ora-37182 : you may only specify one dimension to partition
  • ora-13114 : [string]_NODE$ table does not exist
  • ora-31010 : XML element index string exceeds maximum insertion index string
  • ora-30508 : client logon triggers cannot have BEFORE type
  • ora-25016 : cannot specify column list for insert into nested table view column
  • ora-12472 : policy string is being used
  • ora-30078 : partition bound must be TIME/TIMESTAMP WITH TIME ZONE literals
  • ora-02435 : cannot disable unique(string) - unique key not defined for table
  • ora-07279 : spcre: semget error, unable to get first semaphore set.
  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-30072 : invalid time zone value
  • ora-30929 : ORDER SIBLINGS BY clause not allowed here
  • ora-37015 : (XSACQUIRE_YNRESYNC) Object workspace object is ambiguously listed to be acquired both with and without RESYNC.
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-32612 : invalid use of FOR loop
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-27146 : post/wait initialization failed
  • ora-16000 : database open for read-only access
  • ora-14108 : illegal partition-extended table name syntax
  • ora-19568 : a device is already allocated to this session
  • ora-04064 : not executed, invalidated string
  • ora-02209 : invalid MAXTRANS option value
  • ora-30382 : DROP MATERIALIZED VIEW string.string operation is not complete
  • ora-14070 : option may be specified only for partitioned indices or with REBUILD
  • ora-01639 : instance string has no thread assigned to it
  • ora-14628 : specification of bounds is inconsistent with LIST method
  • ora-29504 : invalid or missing schema name
  • ora-36261 : (XSAGPARTDEP00) Can not Aggregate PARTITION TEMPLATE %J because the path of aggregation would recursively enter partition %J.
  • ora-22312 : must specify either CASCADE or INVALIDATE option
  • ora-29529 : invalid function or method call string in trigger string
  • 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.