DSXchange

You missed the whole point, I'm afraid.

Pradeep, do an exact search here for "rules engine" to get an idea what can be involved. Most are older discussions but still relevant I believe. You'll also find mention of third party tools like ILOG JRules which is now part of IBM as BRMS.

The technote seems to be specific to all jobs hanging rather than 'some'...

I cant use a server job. Sure you can. Doing something like that in a Parallel job borders on the ridiculous. Use the right tool for the job. Why would it need to stop running it after it finds a 'Y'? Sure it makes sense to stop but it wouldn't hurt anything to run it over the course of the day eit...

You can't use a File Watcher to do this, at least not directly. You'll need something to poll the table for a column that is newly set to 'Y' (I suggest a Server job) and then you'll need to check to see if it successfully found a row. At that point you'll need to do two things, 1) mark the row as p...

In my experience, one would be converting any NULL values to an in-band value that you know doesn't naturally occur in the data before the join and then converting them back afterwards. Assuming you want the NULL values to be considered equal and be joined.

Thanks for posting that!

Sure... just not the entire log, please.

iShoreETL - you really should open a NEW post with the details behind whatever issue it is that you are having.

Not necessary. Please check the Inactivity Timeout value as noted.

OK, that's a start. Can you answer any of the questions that I asked?

Sweet! Been far too long since I've had to worry about anything of that ilk... thankfully.

Specifically because of the MKSToolkit or natively? I'll have to dust off a DOS tome and see.

What I believe that you should see is the parallel hint without the required 'tablespec' (rather than applying to all tables) is invalid and invalid hints become comments, so no error is thrown. Regardless, the explain plans should reveal all as there can be several factors at work here. Also realiz...

A couple of thoughts... Run both with the proper separator between them. For UNIX I would typically use '&&' which means only run the thing on the right if the thing on the left succeeds. Not sure if there is a DOS equivalent but that shouldn't really matter. Or write a wrapper script that r...

OK... then why all of this concern to force it to 3?