DSXchange

No thanks.

Any fun columns like a CLOB in your table? Did you try with an array size of 1? What exact (all 4 segments) Oracle client version are you running?

Let us know if the command executes from Oracle Yes it is executed cleanly from Oracle Command Line. Just wanted to point out I never ask this question as a 'yes' here means so very little. Unless there is something wrong with the ordinary SQL syntax then may point someone that way as an object les...

But this job is running fine in production server. It is only when I imported it to Dev box, it started to throw this error. The table structure in both dev and prod schema is also identical. Hmmm... that would have been good information to share right off the bat. :? So, what *is* different betwee...

More to it than that. You first need to define it in the Project as a user-defined environment variable using the Administrator and that sounds like the step you missed. There you would set its value to $ENV which means it will take the current value from the job's environment. Then in the job, add ...

Hmmm... seems to me it is likely that you have a network problem.

There's a heck of a lot more to it than that, but Index would give you a minimal check. All kinds of regexp samples posted on the 'net for stuff like this - email, phone number, etc which a search should turn up. May help... may not.

And then pad zeros for the parts it doesn't handle.

More of that "amplifying", eh?

That never occurs to me as it's a Windows thing and I've never worked on a Windows-based DataStage server. Not every really sure when you would enable that, as all it seems to do is introduce a still measure of grief into people's lives.

Now it's 50 transformers rather than "datasets"?

If all you want are the failures, it's perfectly fine to capture the rejects like it sounds you did. For "Continue" however, did you check to see what the actual values were that "did not work" in your constraint? Push them out to a Peek stage so you know why it is not working......

Probably, but don't know for certain... others will.

ps. It is "tier" not "tire" by the way.

You've got the whole key / where clause thing basically right but your problem is using bind variables in the select list. You can only bind the key columns in the where clause of your sql, they are not available to stand in for column names in the list of columns to select.

Sorry, but this is a peer-to-peer support site so there's no concept of "ASAP"... that or our concept probably differs radically from what you're looking for. For that kind of help you should go to your official support provider, that's one of the reasons your company pays them big bucks e...