DSXchange

Are you sure the error is being generated in the Oracle Enterprise stage and not, say, a Transformer stage? Can you post the entirety of the detailed error message from the job log?

Something about "The Matrix" perhaps?

No idea from me also. Please provide a context.

If you're in a version of DataStage that supports looping in the Transformer stage then yes. Otherwise probably not.

Output from a Join stage is the result of the join. There's no such thing as rejected rows.

Tip: write out the logic in English. It will help you to design the logic (which is not difficult) or to understand - or even correct - what someone else suggests.

Or might another job be generating values for the same sequence name?

They're the ones I meant.

Might be an interview question though.

This script loads the environment variables from a DataStage project into the common metadata repository so that they can be resolved when Metadata Workbench is stitching assets together. I think this is a problem for your official support provider. "Array index out of bounds" suggests an ...

There are also functions in parallel Transformer stage for generating date offset from weekday. I can't research them right now, but you can.

CMD shell typically.

My understanding is that there's only one comma. Anything to the left of the comma is Last_Name, the first space-delimited field to the right of the comma is First_Name, and anything else is Middle_Name. Hence: svLastName Field(Inlink.TheString, ",", 1, 1) svOtherNames Field(InLink.TheStri...

Same rules as for any other command line, provided that the relevant environment variables, such as APT_ORCHHOME, have been set.

Craig's solution is the most elegant offered. Group by id, min start_date, max end_date.

chulett wrote:Isn't this restriction removed in the later 8.x releases?

Yes. In 8.5 I think, definitely in 8.7.