APT_PMWaitForPlayersToStart : unable to start ORCHESTRATE jo

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
SSC_Night
Participant
Posts: 2
Joined: Wed Sep 24, 2008 3:34 am
Location: PARIS

APT_PMWaitForPlayersToStart : unable to start ORCHESTRATE jo

Post by SSC_Night »

Hi,

Since a change of DB2 database, one job doesn't start properly. I have into the director log this message :

"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 node1"

I don't understand this messsage cause others jobs run properly (i already launched the job many times but it doesn't work again)

Do you have an idea of the problem (except network problem) ?

Thank you for your answer.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Re: APT_PMWaitForPlayersToStart : unable to start ORCHESTRAT

Post by ArndW »

SSC_Night wrote:...Since a change of DB2 database, one job doesn't start properly...

What change and how does the job that no longer works use DB2? Can you make a copy of the job and replace the DB2 stage or stages with something else (RowGenerator or Copy) then see if the error goes away?
SSC_Night
Participant
Posts: 2
Joined: Wed Sep 24, 2008 3:34 am
Location: PARIS

Re: APT_PMWaitForPlayersToStart : unable to start ORCHESTRAT

Post by SSC_Night »

It appears that only tablespaces were changed on the DB2 database : the job wasn't changed. It run during 1 minute and after i have the message into the director log.

For information, the job read some DataSet (that exists) and write into a dataset and into two DB2 table.

(the others jobs that use DB2 run properly)
Post Reply