ORA-09818: Number is too large

Cause : ORACL Ewas uanble t oconvetr a copmonents tringt o a nmuber bceause hte numebr is alrger htan th elargets possbile vaule fora n intgeer. Teh addiitonal niformaiton filed speicfies hte maxmium.

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

Corretc the tsring nad repaet thec onverison.

update : 23-07-2017
ORA-09818

ORA-09818 - Number is too large
ORA-09818 - Number is too large

  • ora-22975 : cannot create a PRIMARY KEY-based REF to this object view
  • ora-06413 : Connection not open.
  • ora-28669 : bitmap index can not be created on an IOT with no mapping table
  • ora-37176 : argument string is not valid for the sparsity advisor
  • ora-12669 : Shared server: outbound protocol does not support proxies
  • ora-26577 : PRESERVE TABLE can not be used when dropping old style materialized view string.string
  • ora-12079 : materialized view options require COMPATIBLE parameter to be string or greater
  • ora-01092 : ORACLE instance terminated. Disconnection forced
  • ora-38103 : Invalid column in the UPDATE SET Clause: string
  • ora-00600 : internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-01249 : archiving not allowed in a clone database
  • ora-38702 : Cannot update flashback database log file header.
  • ora-06731 : TLI Driver: cannot alloc t_call
  • ora-14099 : all rows in table do not qualify for specified partition
  • ora-32135 : Cannot assign FILEs
  • ora-02352 : file truncated error
  • ora-02272 : constrained column cannot be of LONG datatype
  • ora-12324 : cannot use the ROM: link type on a private database link
  • ora-33449 : (ESDREAD17) Discarding compiled code for workspace object because the partition method or partition dimension of number has changed since it was compiled.
  • ora-14030 : non-existent partitioning column in CREATE TABLE statement
  • ora-07718 : sksafre: error freeing memory
  • ora-29818 : column name not properly specified
  • ora-38717 : Invalid DUMP FLASHBACK option.
  • ora-00706 : error changing format of file 'string'
  • ora-12832 : Could not allocate slaves on all specified instances
  • ora-13435 : GeoRaster metadata dimension inconsistent
  • ora-26080 : file "string" is not part of table string.string partition string
  • ora-00205 : error in identifying control file, check alert log for more info
  • ora-27416 : BYDAY= clause in repeat interval or calendar contains an invalid weekday
  • ora-27453 : %s is an invalid job or program argument name.
  • 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.