Oracle Connector stage issue

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
vgundavarapu
Premium Member
Premium Member
Posts: 22
Joined: Wed May 08, 2013 8:38 am
Contact:

Oracle Connector stage issue

Post by vgundavarapu »

Hi,

I am getting the following DataStage issue, so please let me know what are the steps to be taken to fix it.

Oracle Connector issue:

Failed to send the request to the handler: The agent at the datastage:31531 is not available.


Thanks,
Venkat
Thanks,
Venkata Gundavarapu
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The ASB Node Agent is not started on the engine tier machine where your DataStage project resides.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vgundavarapu
Premium Member
Premium Member
Posts: 22
Joined: Wed May 08, 2013 8:38 am
Contact:

Oracle Connector stage issue

Post by vgundavarapu »

ASB Agent is started and DB2 Connector connection is working fine. The problem is with Oracle Connector stage connection.

May be I am missing any other service or any confirguration set up.

Thank you in advance.
Thanks,
Venkata Gundavarapu
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

31531 is the port number used by the ASB Node agent (at least by default).
Until this is remedied you cannot assert that this is an Oracle issue.

Use a netstat command to verify that this port is listening.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vgundavarapu
Premium Member
Premium Member
Posts: 22
Joined: Wed May 08, 2013 8:38 am
Contact:

Oracle Connector stage issue

Post by vgundavarapu »

Hi Ray/all,

I have run and check netstat command, but I don't see this port number: 31531 in the netstat list.

When I looked at Services and NET AGENT Service is running and I am able to connect Datastage and DB2.

Could you please let me know what steps need to be taken to start port number 31531.



Thanks,
Venkata
Thanks,
Venkata Gundavarapu
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

NET AGENT is not the same as ASB Node Agent.

You need to start the ASB Node agent (and probably the Logging agent as well, which uses port number 31533 by default).

There is a single script (Node_Agents.sh) in the ASBNode/bin directory that starts both agents. This should be documented in your shut down/start up documentation.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
vgundavarapu
Premium Member
Premium Member
Posts: 22
Joined: Wed May 08, 2013 8:38 am
Contact:

racle Connector stage issue

Post by vgundavarapu »

Thank you for your reply.

I am using Datastge 8.7 and run the script as you mentioned. Now I am able to see the port number 31533, but it is in TIME_WAIT state, I have run netstat command again and again, still I see the same message.



Thanks,
Venkat
Thanks,
Venkata Gundavarapu
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Talk to your System Administrator about what that state means and what can be done about it. For some light reading, here is probably more than you've ever wanted to know about it. :wink:
-craig

"You can never have too many knives" -- Logan Nine Fingers
vgundavarapu
Premium Member
Premium Member
Posts: 22
Joined: Wed May 08, 2013 8:38 am
Contact:

Oracle Connector stage issue

Post by vgundavarapu »

Thank you Craig, I will check with administrator.



Thanks,
Venkat
Thanks,
Venkata Gundavarapu
lstsaur
Participant
Posts: 1139
Joined: Thu Oct 21, 2004 9:59 pm

Post by lstsaur »

What you can do is
1.) lsof -P | grep 31533
2.) Find pid
3.) Kill pid
4.) Restart Ds
Post Reply