ORA-16031: parameter string destination string exceeds string character limit

Cause : The value for the specified parameter contained a destination string that is too long.

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

Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.

update : 24-07-2017
ORA-16031

ORA-16031 - parameter string destination string exceeds string character limit
ORA-16031 - parameter string destination string exceeds string character limit

  • ora-25131 : cannot modify unique(string) - unique key not defined for table
  • ora-29371 : pending area is not active
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • ora-14506 : LOCAL option required for partitioned indexes
  • ora-19728 : data object number conflict between table string and partition string in table string
  • ora-38491 : could not evaluate subexpression for rowid "string"
  • ora-02223 : invalid OPTIMAL storage option value
  • ora-33456 : (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.
  • ora-34210 : (MXCHGDCL18) You cannot change workspace object to a dimension composite because one or more surrogates has been defined for it.
  • ora-13761 : invalid filter
  • ora-16062 : DGID from standby not in Data Guard configuration
  • ora-26080 : file "string" is not part of table string.string partition string
  • ora-02719 : osnfop: fork failed
  • ora-36669 : (XSDPART07) string is not a legal LIST partition.
  • ora-01211 : Oracle7 data file is not from migration to Oracle8
  • ora-02177 : Missing required group number
  • ora-12091 : cannot online redefine table "string"."string" with materialized views
  • ora-06701 : TLI Driver: incorrect number of bytes written
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-10647 : Tablespace other than SYSTEM, string, string not found in read only mode
  • ora-19500 : device block size string is invalid
  • ora-02824 : Request free list is empty
  • ora-35578 : (SQLOUT11) SQL cursor 'number' cannot be used with CURRENT OF syntax
  • ora-31506 : duplicate subscription name string
  • ora-39058 : current object skipped: string of type string
  • ora-06933 : CMX: error during attach
  • ora-00161 : transaction branch length string is illegal (maximum allowed string)
  • ora-16784 : the database name in Dependency property is incorrect
  • ora-01864 : the date is out of range for the current calendar
  • ora-10842 : Event for OCI Tracing and Statistics Info
  • 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.