DSXchange

I'm sorry, but is there a question in here somewhere?

Yes, but how many modicums (modicii?) does it take?

(and don't call me Shirley)

Specifically, 'cannot get exclusive access to executable' from what I recall. And then it will pony up the 'job may be being monitored' bit.

Are you sure you need to change the line termination? It's all about who you are creating them for, other Windows or UNIX systems. If it's only for internal consumption by DataStage, it can handle either way without issue. Pretty sure the only 'con' to using DOS style line terminators on UNIX would ...

Search the forums for "did not finish OK" and you'll find this has been asked and answered many times over.

It's an option in the XML Output stage - check the help for Trigger Column. Every time the value in the trigger column changes, it switched to a new file.

Typically, one would ask an SA. What kind of patch?

How are you 'ending the loop'? If you need to Terminate, just branch directly to a Terminator rather than trying to get out of the loop gracefully and then terminate. Same for the email - send it then terminate, all while still "inside" the loop. It won't mind. Much. You could also branch outside th...

Which one you'd use is totally dependant on where you need this information, which the OP has not stated.

"Goes over to the next day"?

Current date is current date and simply running over midnight doesn't change the value of the 'current date' when the the query started, which is when it would be evaluated. Of course, if you start after midnight, then of course it will use the 'next' date.

Key to Ray's point is the use of exports made before the 8.x install. And anything done post upgrade would be lost.

Sure sounds to me like you ran out of space and corrupted the project. Suggest you attempt to reindex - search for DS.REINDEX or DS.TOOLS discussions on the subject for the gory details.

To help diagnose - does this happen with all attempts to view Oracle data? Just this one job? Just this one query? Just this one table?

Usually there is more to it than simply putting a UV stage over the hashed file. As noted, you need a VOC entry and for many people that's unknown territory. It can also involve building / maintaining indexes over the remaining keys, otherwise lookup performance can be pitiful. Glad you got it sorte...

Yes, they "should" be but don't get used to importing new versions into old versions. While you can always "upgrade" by importing older version jobs into a newer version installation, the reverse is not always true. As noted, you're only getting away with it in this context because there is only a m...