Multiple instance Error

hexaware_tmk · Post by **hexaware_tmk** » Tue Sep 09, 2014 9:44 am

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

chulett · Post by **chulett** » Tue Sep 09, 2014 10:10 am

Typically "not a runnable job" means the job is already running. It can also mean it is not compiled but that would not be the case here.

hexaware_tmk · Post by **hexaware_tmk** » Tue Sep 09, 2014 11:08 am

No,Its a Multiple Instance Job and we are passing different invocation Id's from different processes. So Ideally it should not block each other

chulett · Post by **chulett** » Tue Sep 09, 2014 11:32 am

Ideally... should... I agree. However, there's only two things that error means and like I said I'm sure the job is compiled.

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?

ray.wurlod · Post by **ray.wurlod** » Tue Sep 09, 2014 5:19 pm

I agree with Craig. Your symptom strongly suggests that whatever method you are using to request job runs is re-using invocation ID.

nagikondaveeti · Post by **nagikondaveeti** » Wed Sep 10, 2014 7:48 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.

ray.wurlod · Post by **ray.wurlod** » Wed Sep 10, 2014 7:50 pm

nagikondaveeti wrote: Please make sure all invocation Ids are different from each other especially when job is running in multi instance mode.

It's not a problem if you're not in multi-instance mode.