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 : 23-07-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-03218 : invalid option for CREATE/ALTER TABLESPACE
  • ora-02056 : 2PC: string: bad two-phase command number string from string
  • ora-39127 : unexpected error from call to string string
  • ora-01879 : the hh25 field must be between 0 and 24
  • ora-22293 : LOB already opened in the same transaction
  • ora-26762 : Cannot autogenerate name for parameter string because of the following reason: string
  • ora-02088 : distributed database option not installed
  • ora-36268 : (XSCGMDLAGG01) 'string' is not a valid dimension value.
  • ora-30443 : definition for filter string's item string is invalid
  • ora-29362 : plan directive string, string does not exist
  • ora-01031 : insufficient privileges
  • ora-12545 : Connect failed because target host or object does not exist
  • ora-37120 : MDX string is null
  • ora-30204 : buffer is not large enougth
  • ora-25472 : maximum open iterators exceeded
  • ora-02160 : index-organized table can not contain columns of type LONG
  • ora-31462 : internal error while accessing metadata
  • ora-01491 : CASCADE option not valid
  • ora-09743 : smscre: could not attach shared memory.
  • ora-13228 : spatial index create failed due to invalid type
  • ora-39088 : file name cannot contain a path specification
  • ora-14006 : invalid partition name
  • ora-15193 : Internal ASM tracing event number 15193
  • ora-24394 : invalid mode for destroying connection pool
  • ora-01343 : LogMiner encountered corruption in the logstream
  • ora-29390 : some resource plans are not part of any top-plan
  • ora-39159 : cannot call this function from a non-Data Pump process
  • ora-14307 : partition contains too many list values
  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • ora-13460 : GeoRaster metadata SRS error
  • 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.