DSXchange

bhaskarjha wrote:see the log file for the Oracle specific message.

What's in the log?

The only option is to host them somewhere, as in one of the many free file uploader sites. Then you can use the image tags to link them into your post.

In PX you capture rejects from the actual stage itself, not from the transformer feeding it as in Server.

Yah, there was nothing wrong with the OConv you posted. If you still have the issue, show us exactly how/where you are using it, something else is causing the issue.

Post it. Please.

There's a default in the Director client but that one is only good for that PC when using the GUI. Otherwise there's always the dsjob option to set the warning limit when you start jobs at the command line.

Search the forums for "COMO ON", you'll find "COMO OFF" too. That's one way, it should find others being discussed as well, from what I recall.

I wonder if Phil's work would help with this?

Why not add it before then and then simply fill it there?

RAJARP wrote:the list generated doesn't has stages like dataset included.

Known... "issue". Unsure if it was ever addressed.

Nothing really mysterious about it, you do the join in the source sql.

xch2005 wrote:Tried by manually overiding the $NLS_LANG but no luck.

How?

You'll need to do better than that if you want more help. What exactly did you do in the Aggregator and what output are your getting?

Use a Sort stage to add a 'Key Change Column' to your data flow. In a transformer check the new column - when true set your 'number' to 1, when false increment it by 1.

Write the routine and then leverage it in the BASIC Transformer. Or in a Server job.