Hello,
i have the problem, that many of our datastage jobs get a timeout -14 DSJE_TIMEOUT when the maschine is very busy.
All other jobs on the same maschine like pure Unix/SQL-Loader don't fail, they just run longer.
Therefore my question is, whether i can set any datastage parameters so that the jobs may run very long, but don't fail ???
I found this parameters in this forum.
Adding DSWaitResetTimeout
Adding DSWaitResetStartup
Adding DSWaitStartup
Are these the parameter which should be set?
And if yes, which numbers are recommended ?
Thanks a lot for any hints
Manfred
14 DSJE_TIMEOUT
Moderators: chulett, rschirm, roy
-
Manfred Hagedorn
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
Oracle
Hello,
one additional hint:
i seems, that this timeout often come when waiting for Oracle feedback
Is there any special parameter setting for this waiting time?
one additional hint:
i seems, that this timeout often come when waiting for Oracle feedback
Is there any special parameter setting for this waiting time?
I've always heard that it is a hard coded limit and required a "patch" from the vendor to change. Contact your official support provider and see what they suggest. One suggestion I would wager you'd hear would be to run fewer jobs at the same time if the "very busy" part is from running your jobs rather than other processes on the machine.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
Manfred Hagedorn
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am
Chulett,
thanks for your feedback.
I see, that we currently have set only this DSWaitStartup=60
and not the other 2 parameter mentioned.
As these parameters are set under "user defined" variables, i would expect, i can set and change them.
Can anybody tell me the usage / meaning / purpose of
DSWaitResetTimeout
DSWaitResetStartup
DSWaitStartup
To be honest, DSWaitStartup=60 wasn't set by me ... i don't understand/know why.
Manfred
thanks for your feedback.
I see, that we currently have set only this DSWaitStartup=60
and not the other 2 parameter mentioned.
As these parameters are set under "user defined" variables, i would expect, i can set and change them.
Can anybody tell me the usage / meaning / purpose of
DSWaitResetTimeout
DSWaitResetStartup
DSWaitStartup
To be honest, DSWaitStartup=60 wasn't set by me ... i don't understand/know why.
Manfred
The DSJE_TIMEOUT error is because when a Datastage job is invoked the 'calling process' expects a handshake back to say it has started running, and by default expects this reply in 60 secs
When the box is busy (or when a lot of jobs kick in at same time) - the engine can get overloaded a bit - and some jobs take longer than a minute to kick in - hence the error.
As someone has mentioned there was a patch to allow you to configure the timeout seconds to something a bit more reasonable via env variables - and suspect you have this patch installed however presume the default value for DSWaitStartup is 60 secs - so would suggest bumping this value up
Should point out I cant guarantee that this is what the env var is for - however if you look in admin there is normally some help text for each Enviornment variable
When the box is busy (or when a lot of jobs kick in at same time) - the engine can get overloaded a bit - and some jobs take longer than a minute to kick in - hence the error.
As someone has mentioned there was a patch to allow you to configure the timeout seconds to something a bit more reasonable via env variables - and suspect you have this patch installed however presume the default value for DSWaitStartup is 60 secs - so would suggest bumping this value up
Should point out I cant guarantee that this is what the env var is for - however if you look in admin there is normally some help text for each Enviornment variable
-
Manfred Hagedorn
- Participant
- Posts: 58
- Joined: Wed Apr 04, 2007 10:02 am