DSXchange

As noted, you don't "sort a row" so this makes absolutely no sense. Extend your example to all 10 rows and show 10 rows of output, maybe that will help explain what you are trying to say.

I've seen these from 'normal' stages when there are... environment issues. Can you post complete details of your job design, please?

Forget that error and post whatever error(s) failed your job.

Build a hashed file reference lookup from your target and use that to drive your actions. That way you can insert new records and update any changed records and pitch everything else with the right constraints.

Sainath.Srinivasan wrote:I think you can skip :1 if you are not using it.

No, you cannot, which is why Ray asked about it and why the error is being generated. All columns must be bound into the DML.

Use a TO_CHAR() on the select with a mask of 'YYYY-MM-DD HH24:MI:SS' and use a Datatype of Timestamp in the job all the way through.

I've seen this and from what I recall, it's an Oracle bug. What exact Oracle client version do you have installed on your DataStage server? Also note that 11g is not officially supported.

I don't understand what you are asking or what your 'failure' is. Yes, it will wait for the job to complete before returning. Explain what fine versus not fine across environments means in detail. Please.

You can certainly copy them and change or enhance them any way you like. However, I have no idea what "generate -ve number" means, never mind the fact that it sounds like something you should handle in your job, not in the routine call.

Your ultimate goal is a "vertical pivot" of rows to columns, something that's been discussed here quite a bit. The actual Pivot Stage only supports a "horizontal" pivot of columns to rows at the moment. Is your SQL being used as a reference lookup? Only the ODBC and UV stages are...

Or that.

Very odd. First suggestion would be to delete that stage from the job and set it back up again from scratch, see if that fixes whatever is going on.

First bit of advice - don't do all that in a routine, they're not really meant for that kind of functionality. Why not simply do all that "in job" where it is much simpler to setup and easier to maintain. A hashed file reference lookup can get you the three fields, if you can't stream them...

Come to think of it, I've seen the same thing too. Rare, but i've seen it. Seems like there are certain kinds of fatal situations that don't get noticed properly and thus are not reflected accurately in the job status. :? Unless someone else comes along with better advice, all I can think at this po...

Never seen any such thing. What 'update action' are you using? How many links are going into the stage?