DSXchange

Read my post again re: when the truncation happens, it's not about who wins the data race. Shouldn't matter which of the two has the truncate, but for sanity's sake I'd put it on the first link based on your output order.

So you try searching here for 'dssearch'? I got 27 hits not counting yours when I checked. None of them helped in any way?

The truncate happens when the stage is 'opened' and the Oracle connection established, not when rows flow. Me, I'd arrange for the truncation to happen in a separate step or remove it from one of the links as both don't need that update action since they reference the same table.

Who is "we" - everyone or just you? Regardless, I'd guess your workstation(s) were updated in such a matter that broke DataStage... welcome to the Wonderful World of Windows.

First suggestion would be to uninstall and reinstall the client.

Not that I've found. I use Manual mode and then with job control tweak the generated ctl file (typically via sed) to get the bits in there that I need and then invoke sqlldr. Lastly I have to check for all of the things that sqlldr uses to tell me Something Went Wrong - the presence of a .bad file, ...

This is a common approach to supply job params at runtime - place the code in a Before-Job routine allowing job params to be sourced externally and set for the job, even though it's already started. Really? This hack... err, workaround is 'a common approach' and our dear friend Vincent has blogged ...

Then you're not searching the right search as there are tons of posts on extracting the log information and shoving it into another hiding place. They may not all deal specifically with just 'warnings' but the information is out there. I'm assuming the 'get out' part is the issue, not the 'put into ...

So we're not resolved? You are correct that you populate the key columns with non-null data from the input stream so they "should not be null". However, when the lookup fails all columns return null (including the keys) so they can be checked for null post-lookup to determine failure. The NOTFOUND L...

Hmmm... ok. Care to post your resolution?

It would probably help if you explained where you heard about this mysterious document... was it somewhere here? There is an older Ken Bland and Mike Favero document on "ETL Methodology", I'm wondering if perhaps this is what you heard about? However, it is 5 years old and Server specific but is sti...

I'm sorry but what is the point of this Sequence? There's nothing to cause an exception in it nor anything to terminate.

Aha! I knew it!

Welcome! :D You are correct, both of those are Windows only things so you won't find a UNIX equivalent to the best of my knowledge. I'll let others more smarter in this regard give advice, but the first thing that pops into my head is changing the jobs to land the data, then copy it over the the Win...

You can't as the Sequence will always do a 'WaitForJob'. You'd need to start the two jobs at the same time instead.

Unfortunately no, as at that point it is 'too late' - the parameter values have already been assigned Is this a change in 8.x because this work's in 7.5. No, it doesn't... if we are literally talking about a job trying to use DSSetParam on its own parameters in a before-job subroutine. The job has ...