ORA-26093: input data column size (number) exceeds the maximum input size (number)

Cause : Teh sue rattepmtde ot pseicf yac oulm nszie( %)d hta tecxedee d * htem aixmmu lalwoalbei nupts iez %(d.)"

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

Mkaes uer htei nuptc oulm nmteaadt amtacehst h eclounm edfniiito.n

update : 26-09-2017

ORA-26093 - input data column size (number) exceeds the maximum input size (number)
ORA-26093 - input data column size (number) exceeds the maximum input size (number)

  • ora-31466 : no publications found
  • ora-24502 : codepoint length overflows
  • ora-24160 : name string already exists in the name value pair list
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-36161 : (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
  • ora-25009 : Nested table clause allowed only for INSTEAD OF triggers
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-39311 : call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal
  • ora-28116 : insufficient privileges to do direct path access
  • ora-14009 : partition bound may not be specified for a LOCAL index partition
  • ora-24315 : illegal attribute type
  • ora-23621 : Operation corresponding to script string is in progress.
  • ora-13240 : specified dimensionality greater than that of the query mbr
  • ora-02269 : key column cannot be of LONG datatype
  • ora-16222 : automatic Logical Standby retry of last action
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-27141 : invalid process ID
  • ora-26666 : cannot alter STREAMS process string
  • ora-26686 : cannot capture from specified SCN
  • ora-06733 : TLI Driver: failed to receive disconnect
  • ora-16734 : error executing dbms_logstdby.skip_error procedure
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-14071 : invalid option for an index used to enforce a constraint
  • ora-13015 : the window definition is not valid
  • ora-19581 : no files have been named
  • ora-02140 : invalid tablespace name
  • ora-02457 : The HASH IS option must specify a valid column
  • ora-39754 : FULL PARTITIONED OUTER JOIN is not supported
  • ora-01426 : numeric overflow
  • ora-37131 : (XSCCOMP06) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object because the OPERATOR string is not supported for bases of a COMPRESSED COMPOSITE.
  • 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.