DSXchange

I want to restart it automatically. No such thing. You could code something but there's no automagical option for this. The aborted child job can be easily reset as noted and you can build a loop of some kind for the sequence itself but how will the actual problem fix itself? Sounds to me like all ...

All of those "@" variables are documented in the help under the heading of System Variables.

That's the nature of floating point. Are you doing any transforms or a simple move? Any chance your source always has a scale of 2?

Use the Folder stage to read and process multiple XML files. For other types, it is a... less than optimal solution. What kind of 'loads' are you doing?

No can do. Accept the fact that anything that will cause a hard 'reject' will log warnings/errors. Don't want them? Don't cause them.

Show us exactly what you tried and post the actual error messages generated.

Sreenivasulu wrote:Here we would like to implement version control badly.

Hopefully it won't go too badly.

Lookup.

Just how different do your queries need to be, one to another? Can you break them up into logical pieces with the inner parameters already in the job?

#p_SELECT_FROM##$SAPDWSchema##p_REST_OF_QUERY#

I see it won't work when you have a subquery like your example, but something to consider perhaps.

Exactly... turn it on at the job level when you really need or can leverage it properly, case by case. All IMHO, of course.

No, it was dropped from the "initial" 8.x releases and is scheduled to return in a more... traditional... form in a later release. Perhaps even the next one, which will be 8.5 I do believe.

You can't use parameters in parameters, so you'll need to 'hardcode' that aspect of it if you want to pass in everything that way.

To answer the question as originally asked, IMHO I would never simply turn it on at the Project level unless you had an expert developer team all of whom were very comfortable with it.

Have you gone through the documentation, the configuration steps there? For 7.x thatshould be in something like the dsdb2.pdf manual.

So, in your old environment you didn't get these messages at all? If so, what's different about the Oracle environment between servers, specifically the exact Oracle client version installed in each?