We are getting the same error message in many jobs randomly . This job is scheduled to run everyday , Somedays its running without issues and somedays it fails with this error message then if we start the job again even without compiling its completing successfully.
Its a multiple instance job and we pass proper invocation Id.In our production environment multiple jobs gets triggered at same time ,somedays 10 jobs runs at same time and somedays 5 jobs run at same time
Is it something releated to insuffcient datastage configuration?
its Datastage 8.6 -parallel extender - Windows OS
Error Message: Error calling DSAttachJob(JobName.InstanceId)<L>(DSOpenJob) Cannot open job JobName.InstanceId - not a runnable job
Multiple instance Error
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 17
- Joined: Wed Mar 19, 2014 3:53 pm
Ideally... should... I agree. However, there's only two things that error means and like I said I'm sure the job is compiled. ![Wink :wink:](./images/smilies/icon_wink.gif)
Double-check that you are indeed passing in unique at run time Invocation ID values. The fact that later you can run it successfully without any changes / intervention also points to points to the distinct possibility that it was still / already running. Before you restart it do you check the logs to see when last it successfully ran?
![Wink :wink:](./images/smilies/icon_wink.gif)
Double-check that you are indeed passing in unique at run time Invocation ID values. The fact that later you can run it successfully without any changes / intervention also points to points to the distinct possibility that it was still / already running. Before you restart it do you check the logs to see when last it successfully ran?
Last edited by chulett on Tue Sep 09, 2014 10:59 pm, edited 1 time in total.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 2
- Joined: Wed Oct 02, 2013 12:21 pm
I ran into this situation last week. job is being called with multiple invocation id values but there was a case with two invocations but using same invocation Id caused same error. Please make sure all invocation Ids are different from each other especially when job is running in multi instance mode.
Nagendra Kumar
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It's not a problem if you're not in multi-instance mode.nagikondaveeti wrote: Please make sure all invocation Ids are different from each other especially when job is running in multi instance mode.
![Wink :wink:](./images/smilies/icon_wink.gif)
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.