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 : 25-04-2017

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

  • ora-23314 : database is not a materialized view site for "string"."string"
  • ora-39038 : Object path "string" is not supported for string jobs.
  • ora-12493 : invalid MLS binary label
  • ora-01300 : writable database required for specified LogMiner options
  • ora-08341 : On nCUBE, this command can only be executed from instance 1.
  • ora-28334 : column is already encrypted
  • ora-12022 : materialized view log on "string"."string" already has rowid
  • ora-04001 : sequence parameter string must be an integer
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-40262 : NMF: number of features not between [1, string]
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • ora-01240 : too many data files to add in one command
  • ora-27004 : invalid blocksize specified
  • ora-16065 : remote archival disabled at standby destination
  • ora-38956 : Target platform string not cross platform compliant
  • ora-30339 : illegal dimension attribute name
  • ora-13358 : circle type does not contain 3 points
  • ora-29509 : incorrectly formed Java binary class definition
  • ora-16705 : internal error in resource guard
  • ora-38478 : creation of system trigger EXPFIL_DROPOBJ_MAINT failed
  • ora-38760 : This database instance failed to turn on flashback database
  • ora-33447 : (ESDREAD16) Discarding compiled code for workspace object because workspace object and workspace object, which were partition-dependent when the code was compiled, are now not partition-dependent.
  • ora-32320 : REFRESH FAST of "string"."string" unsupported after container table PMOPs
  • ora-02313 : object type contains non-queryable type string attribute
  • ora-13331 : invalid LRS segment
  • ora-07587 : spdcr: $CREPRC failure
  • ora-32501 : Writing SGA to file failed
  • ora-31015 : Attempted to insert entry without name
  • ora-24124 : invalid ACTION parameter passed to DBMS_REPAIR.string procedure
  • ora-31630 : a job name is required to attach a job for user 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.