DSXchange

Immediately after running your sqlldr command in UNIX, execute the command This will report the code returned by the command.

Welcome aboard.
Left() is a Function in the String category.

Are they like servals?

How many different configuration files do you have? For example, is there a single-node configuration file that uses only node 1?

Do your configuration files make use of node pools? Disk pools? If so, please advise details.

If the hyphens are always present, then something like Num(Convert("-","",InLink.Telephone)) should suffice as the test expression in an If..Then..Else construct.

Or maybe Len(Convert("0123456789-","",InLink.Telephone))

mail2krishna79 wrote:Job previously run successfully but now got a problem.

There's no patch. What has changed since the job ran successfully? ("Nothing" is demonstrably not the correct answer.)

Welcome aboard. Make very sure that BigInt (uint64) is used throughout - that it is never Integer (uint32).

Oh, many more than several!

Not necessarily. Depends how the hashed file was created in the first place and whether the metadata were available at that time.

Would a diff command at UNIX suffice? Or is your "matching" requirement not the same as "exact match"?

2 is "file not found". Perhaps you'd better sort that out first?

Someone did, in 7.5.

To verify, check that the values in //PURGE.SETTINGS match those of the project default. Yes, in each log hashed file. Or you could simply delete the //PURGE.SETTINGS record. (Or \\PURGE.SETTINGS if that's what it happens to be.)

Your actual question is not clear. You have posted the code for the supplied routine UtilityWarningToLog. What (precisely) do you wish to accomplish, and under what circumstances? Do you expect this routine magically to do that for you?

Fair enough.

Use a Join stage for "true" joins. Use Merge stage for a "master and updates" model which allows you to detect unmatched masters.