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 : 27-04-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-06129 : NETTCP: unable to transfer socket ownership to ORASRV
  • ora-07280 : slsget: unable to get process information.
  • ora-25193 : cannot use COMPRESS option for a single column key
  • ora-01426 : numeric overflow
  • ora-00331 : log version string incompatible with ORACLE version string
  • ora-09809 : Unable to get user's group ID from connection
  • ora-22280 : no more buffers available for operation
  • ora-01533 : cannot rename file 'string'; file does not belong to tablespace
  • ora-32606 : missing NAV keyword in MODEL clause
  • ora-22933 : cannot change object with type or table dependents
  • ora-32591 : connect string too long
  • ora-12649 : Unknown encryption or data integrity algorithm
  • ora-19333 : Invalid flags for the CREATE_DBURI operator
  • ora-19692 : missing creation stamp on piece string
  • ora-13462 : invalid blocking specification
  • ora-30013 : undo tablespace 'string' is currently in use
  • ora-23514 : invalid or incorrect number of arguments
  • ora-39098 : Worker process received data objects while loading metadata. Invalid process order range is string..string
  • ora-01979 : missing or invalid password for role 'string'
  • ora-12056 : invalid REFRESH method
  • ora-12212 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-12872 : First slave parse gave different plan
  • ora-38717 : Invalid DUMP FLASHBACK option.
  • ora-03210 : DBMS_ADMIN_PACKAGE invalid option specification
  • ora-10664 : Table has bitmap join indexes
  • ora-07324 : smpall: malloc error while allocating pga.
  • ora-16254 : change db_name to string in the client-side parameter file (pfile)
  • ora-15125 : ASM file name 'string' contains an invalid template name
  • ora-30042 : Cannot offline the undo tablespace
  • ora-14099 : all rows in table do not qualify for specified partition
  • 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.