F2T Rejects Rows with Error 'ORA-01722: invalid number' When All Number Columns are Ok
(Doc ID 2065880.1)
Last updated on AUGUST 25, 2020
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 7.3.3.0.0 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Symptoms
In Oracle Financial Services Analytical Applications (OFSAA) Infrastructure 7.3.x, when running an F2T extract, several rows are rejected with an 'Invalid Number' error but you cannot find any invalid numbers in the row.
Errors like the following appear in the F2T sqlldr log file in /<ftpshare>/<Infodom>/logs/<Data Source>/<MIS Date>:
Record 234: Rejected - Error on table CUSTOM_TABLE_XX1, column XX5000_32.
ORA-01722: invalid number
Record 286: Rejected - Error on table CUSTOM_TABLE_XX1, column XX5000_32.
ORA-01722: invalid number
Record 408: Rejected - Error on table CUSTOM_TABLE_XX1, column XX5000_32.
ORA-01722: invalid number
The records contain character values that include accent marks over some of the letters (ex. Ú).
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |