Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
Thanks for your help in advance.
I'm having an issue where only the 1st column of my CSV file is being considered for constraints.
I've setup tMap (attached) to pick up erroneous rows and reject them into a Reject.CSV file.
When the job is run and a constraint column other than column 1 is found, it gives me an Oracle error.
Not sure why the tMap isn't picking up other columns. Please see attached.
Thanks
@manodwhb the error is an Oracle error that I cannot enter a NULL value is a non-null column. But the columns I have specified in "LOADED" connection in tMap should all be checked for NULL values, and they should be sent to REJECTED connection if they are NULL, or am I missing something here? But this is only happening for the first column which works fine, the rest of the columns are not checked if they are NULL and therefore I'm getting errors. Please take a look at the first posting for the screenshots.
@manodwhb No, I just have the "Loaded" tMap connection transferring the columns with the same constraints as I have in the Oracle table. The "ErrorReject" connection (I disabled Die on Error) has the same setup which is where it should create the CSV file with rejects. I don't have any expressions to check, do I need to? I thought that the "Die on Error" and "ErrorReject" options would accommodate this fact.
Thanks again for your help.
@manodwhb Sorry, should have added screenshots embedded in the message.
Here is my current setup. How do you propose I should adjust it?
Thanks
@manodwhb that would make much more sense. I can't seem to find the Reject link at tdboutput though.