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 : 23-05-2017

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

  • ora-39179 : unable to load table "string"."string" because of OID transform
  • ora-09301 : osncon: local kernel only supported in standard mode
  • ora-29355 : NULL or invalid string argument specified
  • ora-31478 : could not detach LogMiner session after change set advance
  • ora-32140 : cannot peform this operation on stream
  • ora-33018 : (XSAGDNGL08) In AGGMAP workspace object, the data type of workspace object must be TEXT, not string.
  • ora-16752 : resource guard could not mount standby database
  • ora-29914 : ODCIGETINTERFACES routine does not return required stream version
  • ora-12457 : security label exceeded maximum allowable length
  • ora-24239 : object could not be invalidated
  • ora-01625 : rollback segment 'string' does not belong to this instance
  • ora-31407 : end_date must be greater than the begin_date
  • ora-15205 : requested mirror side unavailable
  • ora-01082 : 'row_locking = always' requires the transaction processing option
  • ora-37020 : (XSMULTI01) Analytic workspace string is not in MULTI mode.
  • ora-30343 : level name is not unique within this dimension
  • ora-37023 : (XSMLTUPD01) Object workspace object cannot be updated without dimension workspace object.
  • ora-08450 : invalid specification of CR in picture mask
  • ora-32624 : illegal reordering of MODEL dimensions
  • ora-00084 : global area must be PGA, SGA, or UGA
  • ora-38456 : The attribute set "string" is in an inconsistent state.
  • ora-00286 : no members available, or no member contains valid data
  • ora-31168 : Node localname and namespace values should be less than 64K
  • ora-13333 : invalid LRS measure
  • ora-27412 : repeat interval or calendar contains invalid identifier: string
  • ora-39079 : unable to enqueue message string
  • ora-16515 : no rcv channel
  • ora-30677 : session is already connected to a debugger
  • ora-39162 : Transportable tablespace job require privileges
  • ora-28662 : IOT index and overflow segments must share the same LOGGING attribute
  • 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.