DSXchange

Enabling checkpoints in the Sequence job will allow it to automatically restart from the point of failure when run from an Aborted/Restartable status. There's no built-in mechanism to handle your initial "if or" condition. You'd either need to craft your own flavor of checkpointing, keepin...

Hmmm... first suggestion would be to search the forums for oletype and see how it goes from there. Lots of sql has been posted but probably not exactly what you are looking for.

Interesting... had to look that one up.

Why did this post go from being marked as 'Resolved' to 'Workaround'? Are you having an issue with the solution?

Search the forums for COMO ON for discussions on how to land that output for you.

Please verify that this is, in fact, truly happening. The log messages you've posted so far seem to indicate otherwise.

You do understand that, for any multi-instance job to work "in parallel" that each invocation id must be unique amongst any running invocations, yes?

Are the first two columns marked as Key fields?

Hmmm, sounds like a possible disconnect between the XMETA repository and the "Universe" one. Seems to me that might manifest itself as dsjob -lprojects working but the GUI not showing them. Not that I have any clue how to fix that, just saying...

Not in a Server job unless you specifically add these steps in the before- and after-sql tabs. Even the Server ORABULK stage doesn't include an option for that. That happens either from command line sqlldr or when using the Enterprise stage in a PX job. And no, simply truncating the table would not ...

Can't check right now but from what I recall, there's a Designer option to not display these. Also note that once you add a 'Description Annotation' to a job, that option will be disabled when that job is open as only one is supported per job.

Can somebody expleain me why this happens even if had primary key constraint in the table level. i saw many duplicates. how come datastage loaded duplicate data into the table. There isn't any way you could create this situation with that job design. Worst case, your job will fail with duplicate ke...

Yes, of course, as you are comparing before resetting the 'previous' value, something it appears the OP was not doing.

Still... regardless, for this technique to have any chance of working when you compare current and previous values, you need to set the 'previous' value last or they'll always be the same.

Not directly, no. If there's an API and you can get the email piped out or dumped then perhaps, but as noted it's the wrong tool for the job.

If this is really a TX job question as marked, then you're in the wrong forum.