Player 3 terminated unexpectedly

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
JeroenDmt
Premium Member
Premium Member
Posts: 107
Joined: Wed Oct 26, 2005 7:36 am

Player 3 terminated unexpectedly

Post by JeroenDmt »

Since a few days we're having a new datastage served installed (same version 7.5.1.A as on the old server, but a different machine).

When running some jobs on the new server, I'm now and then getting fatal error messages

Code: Select all

   node_node2: Player 3 terminated unexpectedly.
    main_program: Unexpected termination by Unix signal 9(SIGKILL)
    main_program: Step execution finished with status = FAILED.
(sometimes the second line is missing).
The jobs run with the same files, the same data, etc. Most of the time it runs correctly, sometimes it aborts with these error messages.
(and no, nobody is using unix kill commands)

I have searched the forum about these error messages and saw it could be related to a JOBMON problem for which a patch exists. Can somebody tell me which patch I need for that?

I can see on the old server is a subdirectory ../Ascential/patches that has two installed patches (patch_85840 and patch_91846), but on the new server there is no such directory, so I assume there are no patches installed on that machine then?

Is there a way to find out if one of these two patches could be related to this problem and installing the patch could fix it?

The person that installed the server is away for the rest of the week, so I can't get any information about this there now. But it would be nice to know if installing one of these patches would solve the problem and I can stop wasting my time trying to find out the problem or I need to go on figuring out why it works most of the times and doesn't other times.
balajisr
Charter Member
Charter Member
Posts: 785
Joined: Thu Jul 28, 2005 8:58 am

Post by balajisr »

I have no idea about the patch but as a temporary solution until next week you can disable job monitor to solve this problem.
Post Reply