DSXchange

Details, please! How are you running the jobs, from the command line using dsjob? If so, show us your syntax.

Of course, just trying to point out that it may go beyond that.

Just to point out the obvious: "May 9 201 12:00AM" is a perfectly valid date/time, it's just... old. So your validation will need to be more than just a simple validation check but will need business value range checks, it would seem.

... I figured that would have to be all correct seeing as how the job actually runs fine, the only issue is with the View Data option. Switching those around may actually cause the job to no longer run.

I'm not sure I'd want each and every update that "failed" captured to the log like that, but if it works for you that's great. Yes, ODBC has different rules on things than native Oracle would, even if using an Oracle driver. Makes it behave more like other databases, from what I've seen.

This post is 8 years old and from the 5.x version of DataStage, plus I'm not even sure what the "this" and "it" is that you are having an issue with. Always best to start your own post and provide the details of your issue and data examples, then we'll take it from there.

He didn't, as I'm sure you'll see shortly.

Rely is one thing, work is another. It should work even if what it shows you may not be reliable.

Sounds like you may need to contact your official support provider about a patch / fixpack as that smells a little buggy to me.

As noted, there's no warning to log as nothing has failed. I'd suggest you look into a pre- or post-process to compare the keys in your source to the target and log anything that exists in the source but not the target. You could do all of that in your source SQL and then stream the problems to an a...

That's standard Oracle behaviour. It will happily update or delete zero rows, it does not consider that any kind of a failure. That's why it is pretty standard to "pre-qualify" your updates by doing an existence check and only issuing the updates for existing rows. Tell us, what exactly do...

So this "timestamp" source column (QT_Travel) is it actually a string? Not sure how else one would not get "proper timestamp value". If so, can you show us some of these bad timestamps?

Welcome. As noted, the "Log warnings after activities that finish with status other than OK" option considers anything that does not return a zero to have failed, so it's doing exactly what you've told it to do. You'll need to explicitly handle the failure via triggers to shut down the che...

Yup, that was a "trick" that is very specific to Server jobs.

True. Silly assumption on my part.

Transformers aren't meant to be used as a source but found that you can do so provided you A) include a stage variable and B) constrain the output so it doesn't spit out records forever. I don't recall the gory details, but the job will not compile without the stage variable, I forget the error it t...