DSXchange

What about any surrounding warning message?
Reset the job and see if you have any message "From Previous Run ...." pop up in the log. If it does, post its "entire" content here.

Welcome Aboard
Most of the general as well as specific questions have been answered in the past. Use the search facility liberally. Do a "search for all terms" on keywords "difference between dataset and sequential".

How can you not have the dsenv file? Go to your DSHOME directory. Its there.
also, try with small caps uv instead of big caps.

I hope you checked the TNSNAMES.ORA file on your datastage server. The entry looks alright. Can you login, from sqlplus from your datastage server, to your database?

It should work. You can access 10g using 9i client. Check the tnsnames.ora file. Do you have that particular sid set up?

Try searching for it. It really is a DSN error. Basically you need to add entries into the .odbc.ini and uvodbc.config file. Search on the 'How to'. This is also clearly explained in the manuals.

ray.wurlod wrote:Rubbish! A parallel job can certainly be used.

....and who said it cant be. The job type argument was based on specifically using USER STATUS. Any other method, including the one you advised, has no relation to the "USER STATUS with Parallel Job" discussion.

So, a px job cannot be used. But as you said, a server job is a perfectly viable solution.

UV stage will read your hashed file. OCI stage cannot do that.

Did you close the monitor. It might be still open.

USER STATUS is not present in parallel jobs.
For a parallel job. You can load the value into a flat file and then use execute command stage to cat the value and pass it as a parameter value to your next job, via job sequence.

Are you montoring this job? Even that can cause this error.

What kind of dataconversion is being done on Column5 ? What have you specified in your database stage and what is the actual datatype specified at the database level?, for this particular column?

No. Atleast none that I know of.

Do a lookup against the hashed file via UV stage. With the hashed file, it has to be lookedup with all the keys and all the keys need to match to grab a record.