DSXchange

Better to check the actual NLS_DATE_FORMAT in play in the target database. Best to do your work "format agnostic" and stick with a standard format like YYYY-MM-DD HH24:MI:SS and leverage the TO_DATE() function in your target SQL. All IMHO, of course.

No, it was vague so you had to re-clarify. And that should have happened here.

Again, what comes from the OConv is nothing that can be treated as a boolean. You'll need to explicitly check the output and then (if so desired) set the result to true/false.

Pay closer attention to what Ray noted was the result of the OConv.

Yes, that could be the derivation of a single stage variable that you would then reference in a constraint. For that, I would leave off the if-then-else and simply left the expression resolve to true or false and then leverage the variable as a boolean in the constraint.

The syntax is almost identical to what you already have, you basically replace the "CASE WHEN" with "IF". You'll need to change the NVL and IN verbs to DataStage equivalents, of course. And disregard the 'nested' part in this case, you just need one big one if-then-else.

What "same" would that be? The stage works the way it works in your version, not much you can do about that.

Post the entire, unedited error message or messages.

In the meantime, you could always translate that into the same structure you would use anywhere a case statement is not supported - a large nested if-then-else construct.

Correct, the state file and/or support of a sequence object were added in the 8.x release from what I recall.

If you read the other replies here, you would see that was already suggested and reported as not having helped.

Long story short, take all that evidence to your official support provider.

Since these are your questions, I split them out into your own thread rather than clutter up someone else's issue. And that way you can decide when your doubts have been resolved.

For the record, split from this post if you want to see the original context.

To source from a transformer, you need to do two things: 1) Define a stage variable. Note that I did not say "use" although you certainly could, it just needs to exist to allow the job to compile. 2) Set your output link constraint to let out only the number of records that you want, witho...

Moved this over to the Server forum. No, do not 'preload' the hashed file. You should have one input from the source and you should be doing a reference lookup and writing back to the same hashed file in a single transformer. You'll need to precreate the hashed file empty for this to work, use a tra...