ORA-22926: specified trim length is greater than current LOB value's length

Cause : The input length for which to trim the LOB value to is greater than the current length of the LOB value.

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

May not need to trim the LOB value because it's already smaller than the trim length specified. Or, if trimming the LOB value really is required, use a smaller trim length.

update : 26-04-2017

ORA-22926 - specified trim length is greater than current LOB value's length
ORA-22926 - specified trim length is greater than current LOB value's length

  • ora-30340 : illegal dimension name
  • ora-38471 : ROWIDs for table aliases cannot be null
  • ora-31011 : XML parsing failed
  • ora-00484 : LMS* process terminated with error
  • ora-02273 : this unique/primary key is referenced by some foreign keys
  • ora-13786 : missing SQL text of statement object "string" for tuning task "string"
  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-00351 : recover-to time invalid
  • ora-39021 : Database compatibility version string is not supported.
  • ora-19376 : no privileges on tablespace provided or tablespace is offline
  • ora-26020 : index string.string loaded successfully with string keys
  • ora-32803 : value for string cannot be altered
  • ora-13232 : failed to allocate memory during R-tree creation
  • ora-01259 : unable to delete datafile string
  • ora-00307 : requested INSTANCE_NUMBER out of range, maximum is string
  • ora-24120 : invalid string parameter passed to DBMS_REPAIR.string procedure
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-16248 : RFS connections not permitted during Terminal Apply
  • ora-01145 : offline immediate disallowed unless media recovery enabled
  • ora-14119 : specified partition bound is too long
  • ora-12543 : TNS:destination host unreachable
  • ora-39022 : Database version string is not supported.
  • ora-02348 : cannot create VARRAY column with embedded LOB
  • ora-02357 : no valid dump files
  • ora-16561 : cannot remove an active instance
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-29349 : tablespace 'string' already exists
  • ora-16732 : error executing dbms_logstdby.skip procedure
  • ora-00271 : there are no logs that need archiving
  • ora-27547 : Unable to query IPC OSD attribute 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.