DSXchange

We are having the same problem here when an indexed column is a character data type (char or varchar2). DataStage does something with the bind variables (ORCHESTRATE.INV_BK in your case) and Oracle gets confused. As a workaround, we wrap the bind variables used in the where clause of an update state...

UNION is UNION ALL plus DISTINCT (in SQL terms). So, you can use Funnel stage and Remove Duplicates Stage right after that.

Thanks for the hint. It looks like it fixed the issue - I'm getting no more errors for now. My only fear is it may accumulate something that will blow up later.

For the past 6 month, we applied a number of patches that while fixing the original issue would introduce another one or two.

Do you know the patch name for "the multi-instance jobs with auto-purge of logs bug"? We installed JR30015 patch today that according to IBM should fix the problem, but the issue still exists...

Create a signal file in your after-job subroutine without running DSGetJobInfo and check "Only run after-job subroutine on successful job completion" checkbox.

Or you can use TimestampFromSecondsSince(-86400,input.timestamp)

Should not after-job subroutine run only after a job completion (successful or not based on the option) anyway?