DSXchange

It doesn't matter what *you* see from the command line, what matters is what exists in the job's environment when it runs... and even with 'the same user' they're not the same thing. Since it seems to be missing there on production, add it to the environment of that server at whatever level seems ap...

Dear LS,



Please give our friend the Reply to topic button a try next time, there's no need to quote everything every time you want to add to a conversation. I would be eternally grateful and it will cut down on my superfluous quotation cleanup work.

Have fun,
me!

[rimshot]

Or that... another technique the search would have turned up.

One approach requires sorted data, the other does not.

LOGTO is used to connect to an internal Project (aka 'account') not an external ODBC datasource. To test out your ODBC connections you really should be using a DataStage job and one of the ODBC stages rather than any 'command language' or activities at the TCL prompt.

Yah... the key in Server is the ability to use a single target ODBC stage for all of this work and then a single COMMIT or ROLLBACK for the entire unit of work. Ernie helped me do this very thing (on a somewhat smaller scale) a number of years ago. And, as noted, not something easily conveyed in a p...

abhilashnair wrote:How we can we make this work on 4 node file without causing deadlock ?

chulett wrote:Try it now that you are hash partitioning...

Is that more clear?

... and here we are.

Still a vertical pivot and to me the easiest way to solve the 'concatenation' part in a Server job is to use a Hashed File. Read and write to it in the same transformer, create a new record for each key on a lookup miss and append values on a lookup hit. Make sure you do not cache the lookup. A sear...

Try it now that you are hash partitioning...

You need to investigate the use of the 'Preserve type' property.

As noted, there's no documentation so any job generation you end up doing will be via your own experimentation and discovery. To me that's an entirely different discussion from 'modifying job export xml' and something that's been going on forever as Ernie notes. I've personally been involved in a pr...

Actually, you need to "Save as" your xls file to another format - .csv, .txt, .prn for example - before you transfer it to your UNIX system. Then you'll be able to read it with the Sequential File stage.

That would be a 'vertical pivot' (aka rows to columns) and an exact search here will reveal the options you have.

DOS pathnames with spaces need to be enclosed in single quotes, that or you need to switch back to the internal 8.3 format: C:\Progra~1\Micros~1\90\Tools\Binn\SQLCMD No guarantees that the second one is "~1" as it de-dups after 6 characters, so it could be "~2" or "~3" ...