DSXchange

Exactly... nothing really to be confused about as they run just like any other PX job would. And no need for all that YELLING.

Job design?

You'll have to let us know. Are you using the MCM to switch between client versions? Do you understand that only one can be active at any given time?

Nowadays, always start with the Connector as the others have been "deprecated". And the differences (or at least the details of each so you can compare) are in the documentation.

For looping I have used a constraint which increments the count and checks for the required count. This is confusing as constraints can't increment anything, all they do is evaluate an expression for true/false and if true allow a record to pass through. And you can't do any "looping" in ...

Or the dreaded double convert which an exact search here will turn up.

Ah... so it stops working in other applications (like Toad) when you have DataStage open? I thought you meant it wasn't working in DataStage. Mea Culpa.

I'm not sure I follow what exactly it is you mean by "all ALIAS names from ROWS to COLUMNS". Can you show us a sample of the output you need based on the sample input you posted? Meaning what it should look like pivoted? Thanks.

OK... still, since it is working in QA & PROD, your mission is to discover what is different in DEV that is causing this failure. It could be on the LDAP, Oracle or the DataStage side, so check everywhere. I don't think anyone will be able to hand you the solution, instead it will require good o...

The obvious answer would be "yes". :wink: Verify your ORACLE_HOME in DEV is what you think it is. Verify your tnsnames file is where you say it is and is accessable by your DataStage user. And just as an FYI - you only need to set TNS_ADMIN if your tnsnames file is not under $ORACLE_/netwo...

You could always use a Sequence Generator tied back to an Oracle sequence.

If you truly feel you've followed the steps in the link and your issue is unchanged then I'd suggest you involve your official support provider.

No need to post this again. Anyone that can help can do so here.

I've seen many times where whitespace causes odd issues. The stage doesn't need any kind of formatting in the SQL it runs so at the first sign of trouble first thing I do is remove all of the "pretty print" people-centric formatting... tabs, returns, blank lines, comments, etc. Can't tell ...

Sorry, thought I replied to this. More like no one here on the same side of the glass as you has any control over this. And now that you're moved to the "Site" forum you can see that you are not alone and this has been discussed before. For example: http://www.dsxchange.com/viewtopic.php?t...