Kbase 21438: Errors 1438, 2728, 4212 can occur during record load/addition/update with ORACLE DataServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
15/10/2008 |
|
Status: Verified
FACT(s) (Environment):
Oracle DataServer
SYMPTOM(s):
Protoora does not migrate all the data from the progress database to oracle database
No error is displayed on the screen
Value larger than specified precision allows for a column. (1438)
A column in this row being inserted or updated is too large (4212)
Character field too long; table: <table-name> column: <column-name>. (2728)
Any of these errors can occur when loading .d file into ORACLE via ORACLE DataServer
Load fails with the generation of a .e file
The errors can be written to .e ile
Any of these errors can occur when adding and/or updating a record into ORACLE via ORACLE DataServer
CAUSE:
If you're experiencing any of these errors, you may not always get them together. However, the cause of these errors are the same.
These errors occur when length of the column in ORACLE is too small for the data that is being imported into it, or the data being inserted by the application is too large for the defined length of the column in ORACLE.
Errors 4212 and 2728 occurs when the data within a character field exceeds the defined column length within ORACLE.
Example:
Actual data size being imported/added = 10
Progress format; x(8)
Oracle format; VARCHAR2(8)
Error 1438 occurs when the data within a decimal field exceeds the defined column length within ORACLE.
Example:
Actual data size being imported/added = 20
Progress format; -ZZ,ZZZ,ZZZ,ZZ9.99
Oracle format; NUMBER(13,2)
FIX:
These errors basically tell the user to expand and/or increase column length in ORACLE. Determine the record size of the data that is being imported/added/updated versus the length of the column in ORACLE. If there are any records that are longer than the defined column length, then the column length within ORACLE will need to be expanded.
Note that field lengths cannot be adjusted nor changed manually within the schema holder. The column length must be adjusted within the ORACLE and then the schema holder must be updated (pulled back) to reflect the new table definitions.