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 : 29-05-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-21605 : property [string] is not a property of value instances
  • ora-33261 : (DBERRLEN) Analytic workspace string extension number truncated at number bytes while trying to read at number.
  • ora-12042 : cannot alter job_queue_processes in single process mode
  • ora-12028 : materialized view type is not supported by master site string
  • ora-32838 : exceeded maximum number of properties
  • ora-06112 : NETTCP: invalid buffer size
  • ora-14193 : invalid ALTER INDEX MODIFY SUBPARTITION option
  • ora-36222 : (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object
  • ora-13001 : dimensions mismatch error
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-02281 : duplicate or conflicting CACHE/NOCACHE specifications
  • ora-19526 : only one location allowed for parameter string
  • ora-31690 : Process name buffer size must be specified and must be greater than 0.
  • ora-00350 : log string of instance string (thread string) needs to be archived
  • ora-23423 : job number string is not positive
  • ora-39116 : invalid trigger operation on mutating table string.string
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-16416 : Switchover target is not synchronized with the primary
  • ora-14267 : cannot specify PARALLEL clause when adding a (Composite) Range partition
  • ora-01497 : illegal option for ANALYZE CLUSTER
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-13786 : missing SQL text of statement object "string" for tuning task "string"
  • ora-24756 : transaction does not exist
  • ora-02723 : osnpui: cannot send break signal
  • ora-12434 : invalid audit type: string
  • ora-14005 : missing RANGE keyword
  • ora-12715 : invalid character set specified
  • ora-01944 : IDENTIFIED EXTERNALLY already specified
  • ora-02145 : missing STORAGE option
  • ora-32826 : Messaging Gateway agent has already been started
  • 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.