I'm doing an initial load Here is what I have done.
Source has 18.6 million records.
Method 1 :
Job1 extract to file (success)
Job2 Load from file (Failed)
lots of warnings and rejects
Error message :Inserted value too large for column, row rejected.
ORA-01722: invalid number.
I used the same meta data information for the sequential file column definition as that of the target table.
I have no clue for the error.
Method 2:
Direct load from database to database.
No warnings or rejects.
Only concern is snapshot too old may occur.
Any suggestions.....
Unexpected reasons for failure
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 76
- Joined: Wed Jan 25, 2006 6:42 pm
-
- Participant
- Posts: 76
- Joined: Wed Jan 25, 2006 6:42 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 1
- Joined: Fri Aug 03, 2007 12:19 am
Re: Unexpected reasons for failure
Hi,
U can try this
In Job1:
Before loding into the staging target file,If u dont have then map one Transformer stage trim the columns as target mttadata lengths
If ColumnName1 contains length 38
Eg:Trim(ColumnName1[1,38])
U can try this
In Job1:
Before loding into the staging target file,If u dont have then map one Transformer stage trim the columns as target mttadata lengths
If ColumnName1 contains length 38
Eg:Trim(ColumnName1[1,38])