DSXchange

What do you mean by 'work with the sql being generated'? You've done the right thing in my book - treat the Oracle DATE field as a Timestamp datatype and format what you received into what Oracle was expecting. I wouldn't go switching to user defined sql or anything. And handling the two pieces (dat...

Well... the first thing to check would be the problem it suggested - is the RPC 'daemon' running on your server? Less certain on a Windows server but it would be running as a service there and you'd need to see if it shows as Started. Assuming, of course, that you cannot connect at all - not just ha...

Drop a Sequence object on the canvas and set it to 'Any'. Drag a new (second) link from each of your Job Activity stages to the Sequence. Change the trigger value in each to 'Otherwise' - this will catch any other status other than 'Finished Ok'. From the Sequence, run a link to a Routine Activity s...

Actually, this is a very typical problem people run into when first having Sequencers running sequencers. You see, S3 hasn't failed - one of the jobs S3 was responsible for running failed. S3 finished without error - and that's the crux of your problem. A child Sequencer needs to propogate any error...

You've got what you need - a zero is not found and a non-zero is found.

A Shared Container is a code 'fragment' and cannot be compiled on its own. Make your changes, save them and then see how it works out when you next work with a job that uses it.

That looks familiar.

Or that.

Load them into a hashed file.

And in the Properties, you've changed 'Fixed Width Columns' to 'Yes'?

Without specifying an Invocation ID in the routine - yes, two calls at the same time will fail. Make sure you are attaching to "<resuable job>.<unique invocation id>".

The answer will only be Yes if the hashed misses are actually written back to the hashed file in question. I got the impression that the two hashed stages in the 'diagram' were both lookups: We look up HASH twice . one for update and other for insert. If that's the case, they'll need to add another ...

Also the column lengths are included correctly. As a guess, I would say - no, you didn't. All it takes is one wrong one to hork the whole thing up. The other tidbit - assuming it works the same as the Sequential File stage - is it uses the information in the Display Size column - not the Size size ...

Unfortunately, that's the way the Execute Command stage works - and it's confusing as all get out. Your job parameters are translated in everything that it logs, so it looks great there - however, the actual command sent to the O/S doesn't get the parameters translated so it fails. Stupid. You eithe...

No, the key point here is that if you want to rollback the entire transaction, you must make the job abort. Job reset should be handled automatically by your job control, and restart is as easy as it gets in an all-or-nothing load - just run the job again. If there's something in your job design pre...