DSXchange

Not on UNIX. I would guess you'd need the appropriate ODBC drivers and then use the ODBC stage.

Similar perhaps, but not the same. As noted, the Modify stage uses different functions from the Transformer and they are all documented. Looks like what you need is timestamp_from_string().

Yes, use dssh to get to that same "TCL prompt". Simplest way to get there is to cd to your project directory and then launch dssh from there. Never answer "yes" if it asks you to setup the directory for DataStage, it means you are launching the shell from the wrong place.

That's a Netezza error, as a quick google for "ERROR: crossed reserve : Out of memory" reveals. Follow their advice or take the error to your DBA.

Define for us what "rejected" means here. Are they not going down your link because the constraint is false or is Oracle rejecting them?

Or attempt again to remove the last delimiter. Not sure what you tried, but you should be able to simply substring what you need before it hits the Start Loop. Take everything from 1 through (length-1).

Well, the other readers answered the question as asked.

However, you'll notice in the replies that they've already tried that with no success.

So, just to be clear - they are running in a serial fashion and when the problem child runs there are no other jobs from the same sequence running at the same time. Yes? Not wondering about 'all' just 'some'.

Read the text file and pass the value in as a job parameter, then bind the parameter value into your source sql.

Nope, that is your next step IMHO. I'd also suggest you do not delete anything else until this is resolved.

You do not want to be in there manually deleting anything from the old repository. I sincerely doubt it will "work out well" if you continue down that path. I strongly suggest you stop doing that. What exact 8.x version do you have? Are you current on your fixpacks? In the 8.x world there ...

Interesting. Are there jobs running in parallel in the sequence? If so, can you isolate which ones would be running at the same time as the problematic one?

Do you have the same problems with this job if you run it stand-alone outside of the Sequence?

Let's start with the simple things first. Have you closed out and then re-opened the Director since you deleted the jobs in the Designer? Just wanted to ensure the Director had a chance to properly 'refresh' its list. It should happen automatically without needing that step, but still needs to be as...