Today I was running into a mysterious error in DataStage as I was running a sequence job. Things seemed to be going well until one of my Fact jobs at the end of the sequence reported “Aborted” in DataStage Director. Looking into the log for this job revealed a rather vague error message:
[StageName] DB2 function SQLFetch failed: SQLSTATE = HY000: Native Error Code = -1,042: Msg = [IBM][CLI Driver][DB2/LINUXX8664] SQL1042C An unexpected system error occurred. SQLSTATE=58004 (CC_DB2Connection::queryServerHostName, file CC_DB2Connection.cpp, line 3,256)
What’s strange is that the job, when re-compiled and run on its own, executes without error. So it only fails when its run in the context of the sequence job.
To fix the issue, I simply rearranged the order of the sequence at the end. Here is a before and after look at the sequence:
The sequence job runs every job now without error. Now I only wish I knew why this works – perhaps it’s an issue with server resources getting tied up if both Fact jobs are running at the same time? I’ve decided to go with the above as my solution and move on, since neither Fact job takes an enormous amount of time to run. Hopefully this solution will work for others as well!comments powered by Disqus