unable to connect to DB2 database using DB2 EE Stage

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
arvind_ds
Participant
Posts: 428
Joined: Thu Aug 16, 2007 11:38 pm
Location: Manali

unable to connect to DB2 database using DB2 EE Stage

Post by arvind_ds »

I am trying to connect to a remote DB2 database through a datastage job. When I run the job I got the below error.

Please note that I have enabled rsh between host machine and remote machine.
I have made an entry of the remote machine node into default.apt file as well.
I have made an entry of remote node into db2nodes.cfg file also.

Kindly Help guys.



##I TFCN 000001 17:05:45(000) <main_program>
Ascential DataStage(tm) Enterprise Edition 7.5.2
Copyright (c) 2004, 1997-2004 Ascential Software Corporation.
All Rights Reserved


##I TUTL 000031 17:05:45(001) <main_program> The open files limit is 2000; raising to 2147483647.
##I TOSH 000002 17:05:45(002) <main_program> orchgeneral: loaded
##I TOSH 000002 17:05:45(003) <main_program> orchsort: loaded
##I TOSH 000002 17:05:45(004) <main_program> orchstats: loaded
##I TFSC 000001 17:05:45(005) <main_program> APT configuration file: /home2/dsadm/Ascential/DataStage/Configurations/default.apt
ksh: /home2/dsadm/Ascential/DataStage/PXEngine/etc/standalone.sh: not found.
##W TFPM 000152 17:06:16(000) <main_program> Accept timed out retries = 12
>##E TFPM 000153 17:06:16(001) <main_program> The section leader on ADMINBCU died
>##E TFPM 000356 17:06:16(002) <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.
>
>
##I TFPM 000177 17:06:16(003) <main_program> Step started on node PNBDWH03; it uses 3 nodes.
The program running the step is /home2/dsadm/Ascential/DataStage/PXEngine/bin/osh.

##I TFPM 000178 17:06:16(004) <main_program> The ORCHESTRATE startup program in /home2/dsadm/Ascential/DataStage/PXEngine/etc/standalone.sh is being used.

##I TFPM 000181 17:06:16(005) <main_program> A startup script is not being used.

##I TFPM 000183 17:06:16(006) <main_program> The TCP port being used for startup is 10,002; the associated socket number is 5.

##I TFPM 000184 17:06:16(007) <main_program>
Node status:


##I TFPM 000185 17:06:16(008) <main_program> PNBDWH03 -
##I TFPM 000186 17:06:16(009) <main_program> OK

##I TFPM 000185 17:06:16(010) <main_program> PNBDWH03 -
##I TFPM 000186 17:06:16(011) <main_program> OK

##I TFPM 000185 17:06:16(012) <main_program> ADMINBCU -
##I TFPM 000187 17:06:16(013) <main_program> rsh issued, no response received


>##E TFPM 000247 17:06:16(014) <main_program> Unable to contact one or more Section Leaders.
>Probable configuration problem; contact Orchestrate system administrator.
>
>##E TFSR 000011 17:06:16(015) <main_program> Step execution finished with status = FAILED.
Arvind
aakashahuja
Premium Member
Premium Member
Posts: 210
Joined: Wed Feb 16, 2005 7:17 am

Post by aakashahuja »

Your answer lies in the long error message.
>**** 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.
Further,
##I TFPM 000187 17:06:16(013) <main_program> rsh issued, no response received
Check if,

1. PX engine is present on db2 node.
2. The user id which is used to run the job has rsh enabled for the db2 server.

Hope it helps.

Cheers
Aakash
L'arrêt essayant d'être parfait… évoluons.
arvind_ds
Participant
Posts: 428
Joined: Thu Aug 16, 2007 11:38 pm
Location: Manali

Post by arvind_ds »

Thanks Aakash.

The issue has been resolved by making PX Engine available on remote machine.
Arvind
lottokahe
Premium Member
Premium Member
Posts: 21
Joined: Thu Nov 02, 2006 5:56 am

Re: unable to connect to DB2 database using DB2 EE Stage

Post by lottokahe »

Another solution:

Check if the user is able to reach the DB-Server via 'SSH'.
In $APT_ORCHHOME/etc/remsh you have to change rsh mode in ssh.

The Operator wants to start some processes on the DB-Server and cannot start, because of missing Password.

That was our problem in that case.

Maybe it is helpful for somenone.

Kind regards,

Sven
Post Reply