ora 01438

There are 4 main levels of setting Errorstack:0 Dump Error stack only (level 0 has been deprecated)1 Dump the error stack and the function call stack2 Level 1 + processstate3 level 2 + Context area (show all cursors, highlighting current

ORA-01438 Processing MethodSolution: (1) Track and execute the inserted SQL/stored procedure, locate the row that causes the culprit, and insert the row again after modification. (2) The simplest way is to increase the precision of the target field.

Solution: (1) Track and execute the inserted SQL/stored procedure, find the row that causes the culprit, and insert the row again after modification. (2) The simplest way is to increase the precision of the target field.   Because the specific table

Problem: the error "ora01438" is reported when the data is updated or inserted in the project. It is known that the precision of the number type does not match. However, I found that no specific table or field exists in debug.   Symptom: Java. SQL.

Orace error: ORA-01438: a problem with a value greater than the allowable precision specified in this column when operating the Oracle database reported the following error: Java code www.2cto.com ORA-01438: if the value is greater than the value

ORA-01438: The value is greater than the allowed precision specified by this columnFor example, if the value is defined as number (200.12) but is inserted, an error occurs because of number (p, s. Number (p, s), where p indicates the total length

Ora-01438:value larger than specified precision for this column When the eye is clear, the field length is not enough. INSERT INTO OSS_ADDR_MON_STATS_TMP06Select/*+use_hash (a,c) * *Provcode,AreaCode,Count (A.serialid) as

OneWhen the precision of a number is set to numbers (3,2), then the number of digits he can enter can only be 3-2 = 1 bits, and if the decimal place is not enough, it will be filled with 0, and the rounding that is exceeded retains 3 decimal

Problems encountered in the experiment: 1. At the beginning of the experiment, resetlogs reset the online log, resulting in misslogfile errors always reported during the flash. In this case, you need to use the noretlogs method to recreate the

Problems encountered in the experiment:1, just beginning to do the previous experiment, resetlogs reset the online log, resulting in flash back when always reported miss logfile error.This time you need to rebuild the control file in a noretlogs way,