DSXchange

You may be able to compute "c" from "a-b" but as noted it's not always true rejects. You'd need to specifically capture those and even then things may not foot.

Which exact 8.x version? And by 'upgrade' you mean you built an entirely new 8.x server and imported your 7.5 jobs into it, or something else? If we're comparing two servers, what other components may not be exactly the same? For example, is the version of the Oracle client the same on both?

I'd wager you've got a mismatch between what the VOC thinks is there and what it finds on the disk. For example, the VOC record was successfully deleted but the drectory was not and it errors when it goes to create it and find it already exists. Make sure the VOC record is gone and delete the hashed...

Somewhat moot at this point as I still think you need to ask support, but it would have been nice to get all relevant details up front rather than this one at a time pulling teeth approach we're taking. So, where do your parameter values come from? Since there is (apparently) nothing feeding the Sta...

How are you controlling your loop? Does it run for a fixed number of times? Perhaps that has something to do with this as I've always used a UserVariables stage to feed a dynamic 'list of things' to the stage.

Odd. As noted, I know this works just fine in the 7.5.x world, perhaps something is not quite right in the version you have. I would suggest contacting your official support provider and seeing if this is a known issue with perhaps a patch available for it. :? In the meantime, can you list the stage...

Time to involve your official support provider, it seems.

Try:

FILEPATH : /Data/#Execute_Command_1.$CommandOutput<1>#_#Execute_Command_3.$CommandOutput<1>#.csv

You say 'underlying table' singular - are all seven jobs writing to the same table? If not, I would think getting your DBA involved to monitor things when they are 'hung' would be the next logical step.

Another possibility is the 'List all files and tables' tool available on Chuck Smith's website. I adapted it to write to a database table so the results can be easily queried.

OK, perhaps it's unclear which job is giving you the warning message re: the parameters. I was assuming the outer loop Sequence job but you are talking about the inner Sequence job it seems. Question: when the inner Sequence job aborted did the outer Sequence job abort as well? It must and both need...

Restart it with the same parameters you used for the failed run and then let us know what happens. And have you checked any of the "Do not checkpoint" options in your stages?

Welcome. I would suggest you check with your vendor, your source for these "packs". They should definitely come with installation instructions, not to mention "they" should help you with the installation as well. And before you ask, if I had any Words of Wisdom I would have added...

Post your syntax.

"Did not work out" doesn't really help. Have your script echo your output and then use Stage.$CommandOutput<1> or Convert(@FM,"",Stage.$CommandOutput) in the Job Activity stage.