Oracle Error Code 01438
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About ora 01438 error in oracle Us Learn more about Stack Overflow the company Business Learn more about hiring developers
Ora-01438 How To Find Column Name
or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack how to resolve ora-01438 Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up ORA-01438: value larger than specified precision allows sql error: 1438, sqlstate: 22003 for this column up vote 7 down vote favorite We get sometimes the following error from our partner's database: ORA-01438: value larger than specified precision allows for this column The full response looks like the following:
Number Precision In Oracle
the cause for this error? sql database oracle plsql ora-01438 share|improve this question edited Dec 21 '15 at 13:34 Kiquenet 5,0822487148 asked Oct 8 '08 at 4:30 user11104 1621310 View stackoverflow.com/questions/14357816/… –Kiquenet Dec 21 '15 at 13:35 add a comment| 8 Answers 8 active oldest votes up vote 6 down vote The error seems not to be one of a character field, but more of a numeric one. (If it were a string problem like WW mentioned, you'd get a 'value too big' or something similar.) Probably you are using more digits than are allowed, e.g. 1,000000001 in a column defined as number (10,2). Look at the source code as WW mentioned to figure out what column may be causing the problem. Then check the data if possible that is being used there. share|improve this answer answered Oct 8 '08 at 4:56 Thorsten 6,695124370 add a comment| Did you find this question interesting? Try our newsletter Sign up for our newsletter and get our top new questions delivered to your inbox (see an example). Subscribed! Success! Please click the link in the confirmation email to activate your subscription. up vote 4 down vote The number
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! oracle ora-01438 which column Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don oracle error 1438 Burleson Blog
ORA-01438:Ora-01438 Identify Column
value larger than specified precision allowed for this column tips Oracle Error Tips by Burleson Consulting (S. Karam) The Oracle docs note this on http://stackoverflow.com/questions/181344/ora-01438-value-larger-than-specified-precision-allows-for-this-column the ora-01438 error: ORA-01438: value larger than specified precision allowed for this column Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column. Action: Enter a value that complies with the numeric column"s precision, or use the MODIFY option with the ALTER http://www.dba-oracle.com/t_ora_01438_value_larger_than_specified_precision_allowed_for_this_column.htm TABLE command to expand the precision. Because ORA-01438 often consists of an erred entry in your SQL, it is often the case that syntax needs to be evaluated. For example, in the Oracle Technology Network's forums, a user consistently received ORA-01437 when he is running his procedure. His replier pointed out that the values entered may exceed the column definition, or he was entering the CHAR value in the NUMBER field. From that information, ORA-01438 was successfully resolved. Burleson is the American Team Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals. Feel free to ask questions on our Oracle forum. Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications. Errata
Early Adopter Program ArcGIS Ideas Esri Support Services ArcGIS Blogs ArcGIS Code Sharing Product Life Cycles Manage Cases Request Case Start Chat Back to results Print Share Is This Content Helpful? Search on GeoNet http://support.esri.com/technical-article/000002107 Submit to ArcGIS Ideas Error: ORA-01438: value larger than specified precision allows for this column Error Message Using cov2sde command may generate the following error: SDE Error(-51) Underlying DBMS error Extended error code(1438): ORA-01438: value larger than specified precision allows for this column. Cause Attribute values of the coverage in one or more NUMBER fields are too large for the new fields created in the oracle error Oracle table. Cov2sde first creates an Oracle table to receive the data. This new table's NUMBER fields are defined from the output/display column and decimals fields specified for the coverage's INFO table. To illustrate, assume we have a single parcel coverage with an AREA field whose output/display width is 3, and its decimal column is set to 1 decimal place. When this AREA field oracle error code is added to the new Oracle table it will be defined as NUMBER(3,1). The 3 indicates the maximum number of digits Oracle will store in this number field. The 1 means that one of those three digits is reserved for a position to the right of the decimal point. Thus, if the area value in the coverage is 12.3, it would be a legitimate number, but an area value of 123.4 would not be¹.¹Koch, G., and K. Loney, "Creating, Dropping, and Altering Tables and Views," Oracle: The Complete Reference, Electronic Edition (1997):383. Solution or Workaround Changing the output/display column width in the INFO table to a width larger than the attribute value before loading the coverage into the Oracle table eliminates the error, and should allow the data to load. In the previous example, changing the column width from 3 to 4 or higher will correct the problem.Find offending INFO column(s) and increase output/display width size using ArcCatalog™ or INFO . Note: ArcINFO™ Workstation refers to the column as Output width.ArcInfo™ Desktop refers to the column as Display width. Created: 5/5/2016 Last Modified: 5/5/2016 Article ID: 000002107 Software: ArcSDE 8.0.1, 8.0.2 I