I'm finding an issue I'm having with a Fastload job and a text file with pretty standard dates extremely maddening, and I am sure V12/V13 has changed Fastload's behaviour in some way, as I'm sure what I am trying to do was not this difficult before.
Consider a few rows of the tab-delimited text file:
1000224684 37108336867 . . . . . . . . . . . . .
1000228778 58108070333 . . . . . . . . . . . . .
1000229352 62108322621 . . . . . . . . . . . . .
1000230221 55108081702 1000230221 -5000 -5000 103.
In the table I am loading, the date fields are defined as:
USLFIRSTODATE date format 'DD/MM/YYYY',
USLFIRSTOADATE date format 'DD/MM/YYYY',
USLLASTOADATE date format 'DD/MM/YYYY'
In my DEFINE, I have the following (nullif to cater for full-stops):
USLFIRSTODATE (VARCHAR(250), nullif='.'),
USLFIRSTOADATE (VARCHAR(250), nullif='.'),
USLLASTOADATE (VARCHAR(250), nullif='.')
Although I have formatted the date fields correctly (as I see it) in the underlying table, have defined them correctly in the DEFINE section, and put in NULLIF handling, it will simply not accommodate the actual dates. Those rows with full-stops are no issue.
I've got round this issue by simply defining the date fields as CHAR(10), but obviously this isn't a good workaround if I then want to do any date handling once loaded.
Any ideas? Tearing my hair out here and absolutely sure it is something simple, or bound to be!
What is the result?
Does FastLoad actually terminate with an error, or are the rows ending up in one of the error tables?
(What does "full-stop" mean?)