Unable to start ORCHESTRATE job
Posted: Tue Jun 21, 2011 2:08 pm
Hi,
A few months back we had many of our parallel jobs just hanging on the
OSH script (...) step. We opened a PMR with IBM and they suggested to install Fix Pack 3 We were running version 8.0.1 Fix Pack 1. We installed Fix Pack3 and we are now receiving the following error(for the past month)
main_program: Fatal Error: Unable to start ORCHESTRATE job:
APT_PMwaitForPlayersToStart failed while waiting for players to confirm
startup. This likely indicates a network problem.
Status from APT_PMpoll is 0; node name is node0
Once one parallel job gets this error no other parallel job would run unless we bounce the server(I have a dummy job that tests this with a rowgen going to a peek). We are currently bouncing the server 3 to 4 times a day to allow our ETL processes to run in production.
This has no affect on our server jobs, and a new PMR has been opened with IBM. We are getting nowhere with IBM, only the suggestion that upgrading to 8.5 may resolve the issue. They had us turn the McAfee Virus scan off on certain directories thingking that may be the culprit but that did not help.
I have read the other posts for this error and did not find much.
Any suggestions would be appreciated.
Thanks - -John
A few months back we had many of our parallel jobs just hanging on the
OSH script (...) step. We opened a PMR with IBM and they suggested to install Fix Pack 3 We were running version 8.0.1 Fix Pack 1. We installed Fix Pack3 and we are now receiving the following error(for the past month)
main_program: Fatal Error: Unable to start ORCHESTRATE job:
APT_PMwaitForPlayersToStart failed while waiting for players to confirm
startup. This likely indicates a network problem.
Status from APT_PMpoll is 0; node name is node0
Once one parallel job gets this error no other parallel job would run unless we bounce the server(I have a dummy job that tests this with a rowgen going to a peek). We are currently bouncing the server 3 to 4 times a day to allow our ETL processes to run in production.
This has no affect on our server jobs, and a new PMR has been opened with IBM. We are getting nowhere with IBM, only the suggestion that upgrading to 8.5 may resolve the issue. They had us turn the McAfee Virus scan off on certain directories thingking that may be the culprit but that did not help.
I have read the other posts for this error and did not find much.
Any suggestions would be appreciated.
Thanks - -John