ORA-01455: converting column overflows integer datatype
The error 1455 is reported on MOS. This problem may occur during exp export.
1087122.1 introduction:
"When creating a sequence with an initial value greater than 10 bits, the following problems may occur:
ORA-01455: converting column overflows Integer datatype
ORA-06502 PL/SQL: Numeric or value error: number precision too large
APP-01564: Oracle error 1455 in fdsgsv
ORA-01455: converting column overflows integer datatype.
Arzira: Error from fdsnxt: 2
APP-AR-11526: ORA-01403: no data found
No errors but the document number generated is 0
The cause may be:
1. Generally, a fixed length is used in the C code to create a serial number. The maximum value is 10 characters. Sometimes some code may be replaced to call PLSQL to process serial numbers that exceed 10 bits, but not all of them can be replaced.
2. the workbench with the display number can only contain 15 digits.
Solution:
Once the serial number is used, the initial value cannot be modified. The only way is to create a new serial number, take the initial value of a farmland, and then assign it to the category where the old serial number is being used. If you use a sequence without intervals, re-initializing the serial number may lead to more complicated tasks ."
For this error, I have inquired carefully about the execution of the SELECT statement. This error will be reported when a special filter condition is included, and no error will be reported for other filter conditions, it is likely that there are some minor problems in the records corresponding to this special filter condition. After troubleshooting by colleagues, it is determined that a field of one of the records is defined, and NUMBER (10) is defined in Oracle) type. The actual value is 10 digits starting with 8, but the getInt () value is used in the application. The Integer value is-2 ^ 15-2 ^ 15-1, obviously, this value exceeds the maximum value allowed by Integer. Therefore, an error is reported when the SELECT statement is executed. Change getInt () to getDouble.
Summary:
According to the error message: converting column overflows integer datatype, you can check whether the field types defined in the table do not match the variable types defined in the program, resulting in the failure to match the precision length, the length of the INTEGER type is exceeded in the conversion process. That is to say, the field type must correspond to the variable type.