DSXchange

Still curious why the perceived need to update environment variables... to what purpose?

This is regarding the DataStage SLEEP function rather than the one at the operating system level, yes?

USERSTATUS is a 'single value' job level area that anyone can query after-job and see what is in there from the last run. Sequence jobs are the easiest way to leverage that, use the 'Insert Parameter Value' helper in any stage downstream of a Job Activity stage to see that <StageName>.$UserStatus is...

We'd have to know precisely what kind of "load" you are doing to be able to answer that, Kryt0n.

Consider it verified. A Server job cannot re-order records in a Transformer stage.

Ah... thanks for posting the resolution Tony.

Seems like it. Odd that they work that way, even if there are being consistent. Would be interesting to ping IBM or your official support provider for an explanation, see what (if any) reasoning is behind that decision.

Database table means "database stage" to retrieve. Why not use one? Read the value, stick it in USERSTATUS and then anything downstream can use it as a parameter fairly easily via a Sequence job.

It may be a 32bit v. 64bit issue, see if you have a $ORACLE_HOME/lib32 directory (instead of just lib) and try that one instead if it exists.

Interesting... we just recently had the same problem crop up with Neteeza, I wonder if this information helps at all:

viewtopic.php?t=127940

I don't really understand what "file" it is referring to.

Here is the kind of thing I was finding online, but it doesn't seem applicable:

http://zotline.com/shownote.zot/NoteNum/2738.html

OK. So you have an Oracle client installed on the DataStage server and you've made the required changes to the 'dsenv' file, yes? Can you post the changes that you made?

Several ways. Server job could write it to a file and then you 'cat' it in the Sequence to capture it. Or search here for USERSTATUS as another (probably simpler) option.

Please define what "got shifted" means. I suspect I know, but would rather not guess or assume.

Unfortunately, Oracle is the source here so hard to swap it out for something else... except pehaps for an ODBC stage.