DSXchange

Make sure the proper C++ compiler is installed that the version was certified to work with. It is very picky and will not work with other compilers. Your "g+" in the subject is actually "g++" in the errors and is a GNU compiler - is that what you are trying to use?

I've got a much more complicated loop that still basically does the same thing - a mixture of Server and Sequence jobs, most running inside a Loop (but not all) - and I have no such issue with restarts. You mentioned that you have 'Reset if required' set for the Server jobs but don't mention it for ...

'Custom' as in a user written plug-in? Or is this something that only ships with the Windows version of DataStage?

[sigh] What "plug-in" stage? There are... several.. and I refuse to guess anymore what you are doing.

There is no 'command' stage in Server jobs.

I'm assuming Roy moved it.

Check the contents of the dsenv file. Somewhere in it, the environment variable ORACLE_HOME must be set and match where your client is installed. Also, your SHLIB or SHARED_LIB 'path' variable must have $ORACLE_HOME/lib or $ORACLE_HOME/lib32 added to it, depending on your platform and if your Oracle...

Well past time you took this question to Support and asked the source, I would think.

Also, for the morbidly curious in the audience - why isn't "Going down the path of datastage version control and promotion" an option for you?

You need to configure DataStage for Oracle. Did you follow the steps noted in the Plug-In Configuration pdf? Add the appropriate entries to your dsenv file and recycled DataStage? Have an Oracle client installed on the DataStage server?

All are needed before the stage can function.

Both steps assume you have an active support contract for the product...

Actually, I can not use link for passing this max_tid value because I have to pass this value between two *transformer* stages, so second transformer stage treats the link as a *lookup*. This confuses me. I specifically meant add it to the link between the two *transformer* stages, that's what link...

It's certainly there and not all that hard to find.

First step - log in! From the LHS navigator click 'Software Updates'. At the bottom of the page now shown, click 'All DataStage Recommended patches'.

Third one down.

As with all 'abnormal termination' errors, you need to reset the job from the Director and let us know if an entry labelled 'From previous run...' is logged. If it does, post the contents.

So, no one is interested in treating it as an XML snippet and seeing if the XML Input stage could parse it?

Just based on the fact that it can't happen with generated sql, the assumption would be that it must be some form of user defined which simply selects the field without the 'cast' that DataStage expects for the target datatype. Odd that it worked in one environment but not the other when sourced fro...