ODBC on AS400 - the query gets stuck(?)

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
kerensho
Participant
Posts: 13
Joined: Mon Jul 11, 2005 5:36 am

ODBC on AS400 - the query gets stuck(?)

Post by kerensho »

Hi,

we run here SQLs on DB2 through ODBC stage. usually it works fine, but in some cases the query gets stuck after a while. so far we got stuck trying to select from 2 tables: first query 2 columns and got stuck after 3812 and the second got 65 columns and got stuck after 300 records.

we think that once the first buffer is getting full it stops reading data from the DB. the jobs keep on running for hours (until we stop them) but without doing anything.

does anyone know what might cause it?

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

Post by ray.wurlod »

Welcome aboard! :D

Does the same thing occur when you execute the same SELECT statements using the diagnostic command DS_CONNECT?

Can you successfully perform the query from a different client on the DataStage server machine?
Last edited by ray.wurlod on Mon Jul 11, 2005 3:50 pm, edited 1 time in total.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kerensho
Participant
Posts: 13
Joined: Mon Jul 11, 2005 5:36 am

Post by kerensho »

hi again,

we run the same query through Bosonova emulator, which sits on the same client and it is working ok.

how do I run it through DS.connect?

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

Post by ray.wurlod »

You can use the Administrator client command window or a telnet session to the DataStage server before invoking dssh there while attached to a project directory.

DS_CONNECT is invoked as a command. It takes the DSN as its command line argument. It prompts for user name and password. You then enter SQL till you're finished. Exit from DS_CONNECT back to dssh using the .Q command.
Last edited by ray.wurlod on Mon Jul 11, 2005 3:50 pm, edited 1 time in total.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
kerensho
Participant
Posts: 13
Joined: Mon Jul 11, 2005 5:36 am

Post by kerensho »

Hello...

after 10 minutes the DS.CONNECT still does not give any feedback. dince I have no group by or order by, I asume it is stuck as well....

Keren
roy
Participant
Posts: 2598
Joined: Wed Jul 30, 2003 2:05 am
Location: Israel

Post by roy »

Hi (my welcome aboard was sent via private message ;)),
For other people lets make it clear your talking about the DS_CONNECT command.

Try having your DB2 poeple debug the connection and perhaps enable server side trace in the DS side.

Your first objective is to figure out what is blocking the flow?

Is it that the DB isn't supplying rows?
Or
the DS process isn't asking for more rows?

I know your working on a remote location,
So try getting Uri to do it.

IHTH,
Roy R.
Time is money but when you don't have money time is all you can afford.

Search before posting:)

Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Image
roy
Participant
Posts: 2598
Joined: Wed Jul 30, 2003 2:05 am
Location: Israel

Solved !

Post by roy »

Hi All,
AFAIK from onsite report:
A new downloded DataDirect driver seems to have resolved this problem.

All's well that ends well :)
Roy R.
Time is money but when you don't have money time is all you can afford.

Search before posting:)

Join the DataStagers team effort at:
http://www.worldcommunitygrid.org
Image
Post Reply