ORA-12899: value too large for column string (actual: string, maximum: string)

Cause : An attmept wasm ade toi nsert ro updat ea colunm with avalue hwich ist oo wid efor th ewidth fo the dsetinatino colum.n The nmae of teh colum nis givne, alon gwith teh actua lwidth fo the vlaue, an dthe maixmum alolwed witdh of teh colum.n Note htat widhts are erportedi n charcaters i fcharacetr lenght semanitcs arei n effetc for teh colum,n otheriwse widhts are erportedi n byte.s

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

Examin ethe SQ Lstatemnet for ocrrectnses. Chekc sourc eand detsinatio ncolumnd ata tyeps. Eitehr maket he desitnationc olumn iwder, o ruse a usbset o fthe soruce colmun (i.e .use susbtring).

update : 23-06-2017
ORA-12899

ORA-12899 - value too large for column string (actual: string, maximum: string)
ORA-12899 - value too large for column string (actual: string, maximum: string)

  • ora-09216 : sdnfy: bad value 'string' for parameter string
  • ora-25152 : TEMPFILE cannot be dropped at this time
  • ora-07444 : function address string is not readable
  • ora-30115 : error when processing an environment variable
  • ora-33086 : (XSAGINIT01) AGGMAP workspace object cannot be dimensioned by a conjoint dimension.
  • ora-14311 : Expecting VALUES LESS THAN or AT clause
  • ora-16156 : LGWR archive log dependency not allowed if database is standby protected
  • ora-00331 : log version string incompatible with ORACLE version string
  • ora-31687 : error creating worker process string with worker id string
  • ora-27155 : could not execute file
  • ora-12406 : unauthorized SQL statement for policy string
  • ora-15105 : missing or invalid FAILGROUP name
  • ora-29306 : datafile string is not online
  • ora-10926 : trace name context forever
  • ora-24418 : Cannot open further sessions.
  • ora-10364 : Do not clear GIMH_STC_SHUT_BEGIN state during shutdown
  • ora-26001 : Index string specified in SORTED INDEXES does not exist on table string
  • ora-00603 : ORACLE server session terminated by fatal error
  • ora-16407 : Standby database is in the future of the archive log
  • ora-12596 : TNS:internal inconsistency
  • ora-24073 : cannot specify RETENTION_TIME on exception queue string.string
  • ora-22889 : REF value does not point to scoped table
  • ora-30440 : can't fast refresh;refresh complete or set event 30441 for partial refresh
  • ora-01755 : Must specify an extent number or block number
  • ora-16197 : Invalid DB_UNIQUE_NAME parameter specification
  • ora-07753 : slemcf: fseek before write failure
  • ora-02780 : Name given for the core dump directory is invalid
  • ora-38456 : The attribute set "string" is in an inconsistent state.
  • ora-24505 : cannot change character set id on the handle
  • ora-38610 : FI "string" name prefix is reserved for frequent itemset counting
  • 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.