Kbase P58663: 1438 and 4212 occur when data exceeds column length in ORACL
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/12/2003 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.x
FACT(s) (Environment):
Oracle DataServer
SYMPTOM(s):
Value larger than specified precision allows for a column. (1438)
A column in this row being inserted or updated is too large (4212)
Errors occurr during a load of data (.d) into ORACLE
Pro-to-ORA was recently run to create an ORACLE db
CAUSE:
Error 1438 occurs when the data in decimal and integer fields exceed the defined column length within ORACLE
Error 4212 occur when the data in characters fields exceed the defined column length within ORACLE
FIX:
Use Solution P57768 to determine which fields are affected.
P57768, "How to determine the record size within Progress and compare it to the defined length of the column in ORACLE?"
1. Run the code provided in Solution P57768 against the Progress db.
2. This will generate report called LOG4.txt
3. Review report and find out which columns are affected
4. Run Pro-to-ORA however do not load the .sql nor select any other option
5. Adjust the .sql (created by Pro-to-ORA) based as needed
7. Create empty schema holder
8. Pull table from oracle
9. Adjust Oracle schema to progress schema, under Schema Migration Tools
10. Load .d into ORACLE