Fatal error.

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
deesh
Participant
Posts: 193
Joined: Mon Oct 08, 2007 2:57 am

Fatal error.

Post by deesh »

Hi,

After installation i ran my job, it was showing below message, please can any one suggest, how i should solve the below issue.

main_program: **** Parallel startup failed ****
This is usually due to a configuration error, such as
not having the Orchestrate install directory properly
mounted on all nodes, rsh permissions not correctly
set (via /etc/hosts.equiv or .rhosts), or running from
a directory that is not mounted on all nodes. Look for
error messages in the preceding output.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Well... that message is pretty clear. Is this job using a new configuration file? Did you "Look for error messages in the preceding output"?
-craig

"You can never have too many knives" -- Logan Nine Fingers
deesh
Participant
Posts: 193
Joined: Mon Oct 08, 2007 2:57 am

Post by deesh »

Hi,
Following message getting.

main_program: The section leader on ITEM-43826 died.


main_program: Unable to contact one or more Section Leaders.
Probable configuration problem; contact Orchestrate system administrator.
arvind_ds
Participant
Posts: 428
Joined: Thu Aug 16, 2007 11:38 pm
Location: Manali

Post by arvind_ds »

Hi,

How many nodes are defined in the configuration file? Does the configuration file contains nodes external to underlying host? If yes, try to rsh or ssh from host machine to other machine(if configuration file contains aditional nodes remote to host machine).

If rsh or ssh is successful, then you should be able to run the job.Also verify the configuration file by using datastage designer, --> tools --> configuration --> select a configuration file --> check
Arvind
Post Reply