DSXchange

Server job (as marked) or parallel job (as posted) question?

Do you have a hashed file called STG_Parameters_Hash_File?

Do you have a VOC pointer to it?

You will need both for the OPEN statement to work.

As far as I can recall it's something to do with the licensing of the Data Direct ODBC driver - a way for DataStage to identify itself to the driver licensing mechanism. (But I'm not 100% certain on this and would be happy to be corrected.)

If volume were the problem I'd expect error messages from Oracle relating to the size of the UNDO segment.

Kim by the way it is.

Glad you found it. I was next going to suggest fixtool on UV.ACCOUNT, and only after that on the SQL Catalog tables.

joesat wrote:your message got cutoff, Ray... i know i have to subscribe, alas my heart is willing but my purse is weak

can you display the post in full please?

No.
For reasoning please see this post where you make the same request.

your message got cutoff, Ray... i know i have to subscribe, alas my heart is willing but my purse is weak can you display the post in full please? No. Premium membership is one of the ways that the hosting and bandwidth costs incurred by DSXchange are met. You will note that there is no advertising...

That looks reasonable. Curiously, perhaps, I don't have all the environment variables in my head at the moment.

Looks like a full outer self Join to me.

Being attached to a directory is what happens after you CD to that directory. The directory (folder, if you must) becomes your "current working directory"). The CommandeDS variable is passed as an argument to the script. This is the command that is executed in DataStage in the project. Dir...

Why "at script level"? If that's mandatory why did you waste your money buying DataStage? And how do you propose to handle uniqueness across parallel processing nodes?

Resist stupid requirements!!!

I believe there's an /O switch.

What's different in the production environment?