DSXchange

As a matter of fact...

Googling for "escape character" will give you everything you need to know. And your problem has nothing to do with that, rather you have an improperly formatted input file.

I'm curious, what is the "third party tool" of which you speak?

You can't, if by "running" you mean "while it is running".

It's one of the derivations on the output columns that you don't group by. Put a dummy column for the Aggregator, then in the following transformer include the fields you need. That or run them through the Aggregator.

#2 is your culprit.

Or run a link to an Aggregator set to 'Last', it will send a single row back out after the final row has been processed.

As far as I know, it's not a supported client platform, so there should be no expectation of it working from there. Check with your official support provider to confirm.

Just want to double-check - Is this a TX job (from your forum of choice) or a Server job (as marked)?

Edited to add: Job Type changed to TX.

The first bit of advice you are always going to get in situations like this is:

ray.wurlod wrote:We do not attempt to diagnose errors from APT_CombinedOperatorController. Please disable operator combination and report the actual error message produced afterwards.

Thought I'd save Ray the trouble.

Search the forums for "orchdbutil" and you'll find many conversations where people had metadata issues that it was the solution for. The problem examples and answers should all be out there.

First problem, you have two transformers in the job where you are dividing by zero. Fix that. Use an if-then-else derivation to check for that situation and skip the division in that case.

You cannot 'WaitForJob' to get the result you want. You need to loop through your list of jobs, starting whatever you can (without a wait) until you hit the limit. Then keep looping though the list, checking each running job to see if it has completed and starting new jobs when the running count dro...

What is your client platform? Does this happen to everyone or just you?

The answer is simple - it thinks it failed because it did not return a zero. As to why - please post whatever Compilation options you have checked on the General tab of the Sequence's job properties page.