DSXchange

Random thoughts... A) I have never in all my born days heard anything like your issue before and I doubt I will again B) Once you're on 9.1 who cares why it didn't work under 8.1, never mind the fact that support ended for that version just last month C) Why not upgrade to something more recent? 11....

Ah... 8.1 was old and broken. Case closed.

That's going to be a support question, I would think.

Not sure if this helps or not. And we can't really answer your proc question without seeing the actual procedure's pl/sql code.

Short answer? You can't, at least not gracefully. You can however still use a Server Sequential File stage in a Server Shared Container in your PX job for this particular need.

Then it would seem you have found a bug and you should report it. I'd still be curious what happens if you turn that option off...

So, a little lost... are you saying that after you added those two new output links and trigger conditions (5&6) that the Sequence no longer finishes but seems to get stuck / stay running after the 'specific PX job' finishes OK? Or do no downstream tasks run but the Sequence itself completes? Tr...

First try turning off the "Automatically Handle Activities that Fail" property.

A Null Pointer Exception? Think you'll need to involve support for that.

(cough) Server job so sequential file it is.

In all honestly, I suspect there is either a critical piece of information we don't have yet or that you have... miscommunicated. Impossible for us to know, however, and I think you are at this point firmly in the hands of someone with access to your system - which is what I meant by 'boots on the g...

No clue. Have you involved support yet?

Then it seems to me you are firmly on your own with this. Still, however, clarify this one thing for me that you really haven't yet about these 'wrong numbers' you are getting. Where are the counts going wrong, exactly: A) You take the same file and read it several times and it reads a different num...

Right... I'd wager the same thing. The contents are being changed between or during runs by this mysterious other team. Go with Mike's suggestion - record the file size / count before the job runs. Each time.

Duly noted!