Greetings all.
We have an interesting situation where we have a complex job in Project ABC running and when a particular job in Project XYZ kicks off it basically pauses the job in ABC in an Oracle write out.
Naturally we suspected the machine might be overloaded but CPU is running around 40% on average and little to no memory is being used. We brought in a DBA and he monitored the outputs and reported there did not appear to be any issues until the job in XYZ kicked off. He noted that it appears Oracle goes into a wait waiting for additional commands from the job in ABC until the job in XYZ finishes or is aborted.
Other items we have noticed - all other jobs in project ABC run without issue when the jobs in XYZ are running. In fact while the job we mentioned in ABC is stalled other jobs will run as scheduled and have simular read and write stages to and from the same Oracle instance.
We have verified that while the two jobs are using the same Oracle instance they are not using the same tables. (i.e. no tablelocks)
I am in the process of submitting this to our support provider but thought it might be interesting to ideas/thoughts from this community.
Another job in another project takes priority
Moderators: chulett, rschirm, roy
