DSXchange

Permissions and access for the datastage service account to talk with the other database is also important.

I'd try researching the StringToTimestamp function available. It sounds like it may fit your needs

Yes, the only consistent thing is that the same main sequential jobs will fail. And that it will always fail with the same error while the parallel job is set to use 1 node. And they seem to always fail at the same parallel job. But as soon as I make those parallel jobs to use 2 nodes, it works.... ...

I have tried that :/
And most of the posts are seeing things like job core dumps. Which we are not seeing. And using DB2 which we are not using.
Most of the jobs failing just are using oracle connector, xfm, and sequential stages.
But again its completely random which multi-instance job fails

So we are the process of moving all our jobs from Windows over to Unix and are experiencing some strange errors. Our main sequence jobs consist of about 8 small parallel jobs. The smaller parallel jobs we had set to use 1 node, as most of them are simple jobs writing a single line to a table. (for a...

For purposes of updating this post with the solution: We found that a MKS Toolkit file (mkstk.dll) in system32 was showing up as unregistered by windows. And now that we have registered this .dll, this errors have seemed to vanished. IBM told us this was probably because our servers were not hooked ...

Ok so our issues were on two separate posts. One being a fifo pipe error randomly while jobs are running: http://www.dsxchange.com/viewtopic.php?t=153463 Second being that we found whenever the issues occured, sh.exe popped up on our process explorer on the server: http://www.dsxchange.com/viewtopic...

I'm going to revive this old topic, since we may be having issues with MKS toolkit. We are running Version 9.1 on Windows. Is installing MKS toolkit a requirement to install datastage? Because our admin told me that he didn't see an option to not install it. And that it was done behind the scenes. H...

Neither one of these things are the case. This is the strangest error I've encountered :/

Yeah, we still are. They just have not been super helpful sadly. I figure I'd just try to exhaust as much resources as possible in the mean time.

Well..... That's what we are trying to figure out honestly. IBM told us setting "APT_PM_USE_STANDALONE_EXE = 1" would avoid calling it. But its still popping up in process explorer and is causing clients to crash and breaking jobs.

Hi, This is somewhat of a jump off my old post, but a new topic in general. http://www.dsxchange.com/viewtopic.php?t=153463 We've found out that "sh.exe" is causing issues and breaking jobs randomly. Is there a way to avoid calling it without switching to unix? Any ideas are appreciated. T...

Well I appreciate the time everyone has took to try and help!

We worked with an experienced consultant today, and he narrowed it down to a process on our server that was causing this issue. Something called "sh.exe" is randomly breaking and causing this error. Still have yet to determine why its happening. **As a side note, we worked with IBM before ...

Yeah, we are currently working on that now too. There's been some talk that our environment may not be setup properly.