DSXchange

Well, it seems to be failing you now.

You need to specifically set the value of ORACLE_HOME in the dsenv file, not just attempt to use something you believe is already set elsewhere. Do you have an entry setting ORACLE_HOME before it hits the SHLIB_PATH?

I think that it looks like a really useful tool It is a very useful tool, but you need training to be able to use it properly. Hopefully they will not pull the tool because they have not given proper training, that would be the result with any tool, not just DataStage. Be careful with your quoting....

ps. As far as I know, it should always be enabled... or at least I don't recall ever seeing it disabled. Perhaps it is related to having NLS installed as I don't.

Why don't we start with why you think you need to enable it.

It's got nothing to do with database 'Archive' errors. And keep in mind the fact that Auto Purge of a job's log will only kick in if the job finishes without warnings. James - you need to take the time to get up to speed on hashed file stages and precheck lookups to determine insert v. update (etc) ...

You can't. Hashed lookups are equi-joins.

There are several alternatives for you, try searching the forum for range lookup and many conversations on the topic will be revealed.

Space.

In other words, searching the forum for the words range lookup will provide quite a number of interesting conversations on the topic.

then it gives a fatel error "This jobtype is not currently runnable on this platform" could u help me to solve this issue Easy - this jobtype is not currently runnable on this platform. You have to have a very special version of DataStage in order to run PX on Windows. Normally they must be promote...

To 'merge XML' you would typically put the various pieces up into hashed files as unformatted XML chunks. Then an incoming data stream would lookup the various chunks appropriate to that record and allow the XML Output stage do the merging. Seems like you could do that for the SUB_SEG and then strea...

I don't think it has anything to do with locked jobs - those seem to stop the INIT process dead in its tracks. And it's the INIT process, not the actual PROMOTE step that's the culprit from what I've seen. I had the problem happen to me some time ago after not seeing it for years. I can't prove anyt...

What about 'the DSSENDMAIL' doesn't work? You really should start a new post rather than jump on the end of an old one so we have some clue what your specs are. What operating system?

Not sure how anyone here could help. You've got the problem spelled out in the error message, perhaps another set of eyes onsite with you would help. Or try increasing the size... again.

From what I recall - wherever you tell it to put it. It's a property in the stage.