DSXchange

Yes, DataStage will insert re-partitions and re-sorts when it deems it necessary. For jobs where I know what these two are I will set the runtime parameters of "$APT_NO_PART_INSERTION" and "$APT_NO_SORT_INSERTION" to "true" (note the double-negative). It is useful to al...

I see now what you meant regarding the string length. DataStage server treats strings differently internally and doesn't really limit the length, so that isn't part of your problem.

Do integer values come across the ODBC interface correctly?

Ah yes, pre-8... my mind was stuck somewhere in the featureless void of xmeta and couldn't escape

What is your xmeta repository on "MachineA" - is it Oracle? If yes, then I'd suggest a complete backup of the DataStage server then delete DataStage and Oracle 10, install Oracle 11g then re-install DataStage. If xmeta is db2 on that machine then Oracle changes won't affect the DataStage s...

I'm a bit confused about your project, the machines you have, and versions of Oracle server (and client). Machine "A" has DataStage 7.5.3 and which version of Oracle and is it the repository? Machine "B" has Oracle 11g and what else? What exactly do you want to do with the second...

...if at all i run the job with specifying current length descriptor...

Where are you specifying the length?

When i do a select in mysql it displays correctly if at all i pass a string and load into db then it shows small boxs I didn't quite understand that last part, if you load it into the db how? Also, if you load integer or date or decimal values using the ODBC driver do they show up correctly? Do you...

Ray, I'm confused as to why you mention a dataset not taking an input and output in the same job - my proposal using a dataset specifically stated two jobs, one to read the source and produce a dataset, then a second to read that dataset into a database.

This cannot be done with the interface in the Director, but since you are on UNIX you are probably using cron and you can schedule this by a line similar to:

@yearly {path_to_dsjob} {dsjob -run options}

Note that if all goes well the dummy lookup will get no rows - it is just there to perform timing synchronization so that the second database stage doesn't get any data until the first (truncate) stage completes execution. This isn't a particularly clean method and I would recommend solving it with ...

OK, that means that DataStage internal and sequential files are OK. It is necessary to examine the ODBC connection in Server. Could you post your definition in the odbc.ini file?

How are you viewing the data when you see the Chinese characters, as a SELECT in MySQL?

Here is what that job would look like

Since the stages in your job all get started in parallel the design will not work as you described in one job. While you could write a complicated job to emulate this functionality (have a transform stage split the source stream, one output link would only take the first row (from the first processi...

It really does look like you have problems with multibyte data and NLS in your server job. To narrow down your problem, create just one row of data with just one column and fill it with the value "abc" in a transform stage. Compile and run the job. - Do a "view data" on the outpu...

3.View data in the job works fine with full lengh. Make a copy of the job with just the ODBC read and write to a sequential file. Are the strings truncated? 5.No,If we write to a mysql database using the same ODBC settings, no strings are inserted(the value is '') What if you do a dummy job where y...