Not able to add datasource in a job

A forum for discussing DataStage<sup>®</sup> basics. If you're not sure where your question goes, start here.

Moderators: chulett, rschirm, roy

Post Reply
sanygup
Participant
Posts: 34
Joined: Thu Sep 20, 2012 10:19 am
Location: newdelhi

Not able to add datasource in a job

Post by sanygup »

I am trying to add datasource in "ODBC Connector"

But following error is coming "Failed to send the request to the handler: The agent id <<hostname:31531>> is not available."

I have used netstat -an |grep 3153 and following entries are coming:
tcp 0 0 *.31533 *.* LISTEN
tcp 0.0 *.31538 *.* LISTEN

and no entry for port '31531'.

I have start/stop the DS engine, ASB Node agent and looging agent and no error is coming, all seems ok.

Also I am not to telnet the engine using 31531 port.

Environement I am using :
AIX 6.1, Information server 8.5, Websphere ND 7.0.15, DB 9.7 fix pack 3a.

Separately installed DB2 on separate AIX lpars on active passive cluster mode. WAS is on separate lpar on cluster mode with two nodes. Datastage engine is on same machine as WAS (with service tier).

Please provide the solution of aboe issue.

Thanks in advance.
Aspirant
jerome_rajan
Premium Member
Premium Member
Posts: 376
Joined: Sat Jan 07, 2012 12:25 pm
Location: Piscataway

Post by jerome_rajan »

Is that a runtime error or is it something you see when you try to view data?
Jerome
Data Integration Consultant at AWS
Connect With Me On LinkedIn

Life is really simple, but we insist on making it complicated.
sanygup
Participant
Posts: 34
Joined: Thu Sep 20, 2012 10:19 am
Location: newdelhi

Post by sanygup »

Hi Rajan,

No not at run time. I am facing this error even on clicking on datasource button (under ODBC connector).

I am not able to locate any service running on port no. 31531 when I run netstat -an command.

I have tried to stop and start nodeagent and engine many times but have not found any success.
Aspirant
sanygup
Participant
Posts: 34
Joined: Thu Sep 20, 2012 10:19 am
Location: newdelhi

Post by sanygup »

resolved:
Please check if any listener port such as orb_listener port is not having 0 value and also not equal to any other websphere cluster node port.
Assign unique port number and restart the server.
Aspirant
iq_etl
Premium Member
Premium Member
Posts: 105
Joined: Tue Feb 08, 2011 9:26 am

Post by iq_etl »

Just wanted to add some information here in case it's useful to anyone else.

We were getting the same error, and discovered (in our case) that the ASBNode service will refuse to start a listener on TCP port 31531 if you have the following empty config files in place:

/path/to/datastage/ASBNode/conf/https.conf
/path/to/datastage/ASBServer/conf/https.conf

Background: we enabled SSL on our 8.7 server but then reverted to cleartext / non-SSL. When we reverted, we didn't delete the empty https.conf files. And the TCP 31531 listener refused to start again until we did delete them.
Post Reply