We just upgraded To TD 14.10.04.06 version from TD 12, and we are in a process of replacing all the fastload scripts with TPT Load.
Earlier with fastload, it used to load the good records and move bad records to ET and job used to fail.
I noticed TPT doesn't fail even when bad records (data issue like, NULLs value into not null column etc.) goes to ET table, and it loads the table with good records.
I want to make it fail or successful with warning code 4, so that I can take some action for the bad records. Otherwise I will never get to know if it runs in batch.
Or atleast could someone suggest me any alternative for the problem.
I'm using TPT version 14.10.00.05.
I would greatly appreciate any help. Thank you.
FastLoad exits with "Highest return code encountered = '0'" if there are any rows in the Error Tables.
Only when you specify an ErrorLimit the job will fail, this is the same for TPT.
So either add ErrorLimit or check if the Error Tables exist after the job finished.
Perfect. Dieter thank you for your prompt reply.
Now, I have a small rather stupid question, is there any way/option by which I can make my TPT job load all the good records and let bad record go to error table but my script should fail/"success with warning" and my target table should not be locked.
where in the FastLoad log did you find that information?
Only the number of errors is returned.
and now for something completely different :-)
0008 SET RECORD VARTEXT "»" DISPLAY_ERRORS NOSTOP;
Total Error Table 1 = 0 ---- Table has been dropped
Total Error Table 2 = 0 ---- Table has been dropped
Total Rejected Rows = 5
I explored these DataConnector options. It will handle only less columns, more columns or excess column width.
But I'm looking at data issues like Null into Not Null column, char into integer/date column or invalid date value.
In these cases, it goes to loader and it fails the job when I set the ErrorLimt, also locks the target table and ET table.
In this situaltion, how can I locate the erroneous records when I can't access ET table nor it be displayed in log.