Timeout Expired

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
Sreedhar
Participant
Posts: 187
Joined: Mon Oct 30, 2006 12:16 am

Timeout Expired

Post by Sreedhar »

Hi,

I am getting the following error.

ODBC Function "SQL Connect" Report SQLSTATE=HYT00:Native Error Code =0 MSG = [IBM(DataDirect OEM)}{ODBC DB2 Wire Protocol driver] Timeout Expired.

and this is not consistent. When I rerun the job some times it runs fine and some other time it fails.

Not sure what is causing this.

Did any of you come across this?

Is there any Timout Period which we can set it to some max value?
Regards,
Shree
785-816-0728
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

Sounds like a question for your DBA.
-craig

"You can never have too many knives" -- Logan Nine Fingers
sjordery
Premium Member
Premium Member
Posts: 202
Joined: Thu Jun 08, 2006 5:58 am

Post by sjordery »

I've had this with multiple lookups with multiple ODBC connectors. The downstream DB connections seem to time out waiting for data to flow from the earlier lookups.

The only way I found to get around it is either:

A) If you are using lookups - examine your strategy, ie. whether you are using normal or sparse and whether that is appropriate, or

B) split the job so that there are less lookups/ODBC connections per job

If you're not using lookups (not clear from your post) then ignore this!
Post Reply