DSXchange

In this context the two are synonymous, I tend to use the terms interchangeably.

The DSGetJobInfo(YourJobHandle,DSJ.JOBCONTROLLER) will give you a job's parent.

how many and what type columns are you importing in that stage?

Could it be that the failure happens when the machine is under heavy load and manual starts happen when that is not the case? It this a materialized view in Oracle or a dynamic one?

Not being able to test it with reject links makes it tough; can you duplicate the production data on another DataStage machine in order to test it? What about duplicate primary keys?

Not really. If there are errors in the load then the job will show those errors, if they don't show up there, then I would look at duplicate keys overwriting existing records as a possible reason.

You could use a reject link and insert/update method to check.

This one somehow slipped through the cracks. Is the issue solved or is it still open?

What port are you using for the connection and can you ping 10.191.131.60 from your PC?

Please post to this duplicate thread of the same issue.

What happens when you try the UTF-8 map when reading? It would seem that the SQL Server map is MS-1252 (at least from what Google told me about the "SQL_Latin1_Genearl_CP1_CI_AS" setting), so you would need to replace any characters that are not represented in MS-1252 in any case.

The key is to know what map was used to generate the file. Could it be UTF-8 or UniCode?

If you go into the designer and open up a new job then save it with the same name as the job your are trying to import, does that work or do you get the same (or another) error?

Interesting spin on a data question, but put into a modern IT context.

Parallel jobs do not have hashed files, only server jobs do. Hashed files are similar to database tables and one can do indexed or keyed reads on them, as well as update the contents; this cannot be done with sequential files.

If you reset the job, do you get an entry "from previous run.." an could you post the contents to the thread; there might be some additional information available.