DSXchange

Ah... good to see some things never change.

And both of those native stages would require their respective clients be installed on the DataStage server.

It would be for every '100 records from ETL'. It's all about the requests sent down the link regardless of what that turns into in the actual database.

I'm sorry but that's not nearly enough information for anyone to be able to help. Post the complete, unedited error message and explain your job design as well.

Those "Parallel options" are so small in number (and usually defaulted) that I don't see an issue with having both windows up and doing a visual check / manual syncing of the two.

Search for the proper linker and compiler settings. I've no Windows server here so no clue, but they have been posted in the forums.

That was my question - I don't see how you can restore XMETA back to an older copy without doing the same with the Universe repository. They are a matched set now.

If Oracle is the source, how are you "Connected to Microsoft SQL Server"? Regardless, it doesn't like the fact that you have quoted identifiers as noted in the error message.

Ah... that's what it is. I was looking for a macro called DSLogName but not having any luck. Forgot it was a system variable.

You'd probably have to go back to an ORCHESTRATE manual for that. Check the Generated OSH tab in the job, you'll see them there.

The difference between two timestamps will be in seconds. Compute the hours / minutes from there.

Because someone already screwed up and said "Yes" in dev. :? Always answer that question "no", it means you're in the wrong place. Always launch "uvsh" or "dssh" from one of two places - $DSHOME or inside a project directory. For the latter you're good to go, ...

There's no magic answer. I would suggest that you search for SIGSEGV here and concentrate first on any that are marked Resolved, see if anything in them helps. Then go through the allegedly unresolved ones. Then experiment. Does the grid node the job runs on matter? Does it work if you constrain it ...

Why not use the Stored Procedure stage? That is, after all, what it is for.

These are not typically simple to figure out. Involve your official support provider.