By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,610 Members | 1,697 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,610 IT Pros & Developers. It's quick & easy.

Resolving SQLCODE -911 in IBM DB2

P: 2
Hi ,
This error is got in the logs
ErrorLogger E org.quartz.core.ErrorLogger schedulerError An error occured
while scanning for the next trigger to fire.
org.quartz.JobPersistenceException: Couldn't
acquire next trigger: DB2 SQL error: SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 2


On going through few DB2 sites i was able to find that SQLSTATE: 40001 is got when we have an deadlock situation. But i was not able to find the SQLCODE matching to the one we get in our logs. Some one please explain as to what this code means and is it interrelated to deadlocks. This happens during finding the next trigger to fire using quartz job scheduler.
Feb 7 '07 #1
Share this Question
Share on Google+
1 Reply


P: 1
Hi ,
This error is got in the logs
ErrorLogger E org.quartz.core.ErrorLogger schedulerError An error occured
while scanning for the next trigger to fire.
org.quartz.JobPersistenceException: Couldn't
acquire next trigger: DB2 SQL error: SQLCODE: -911, SQLSTATE: 40001, SQLERRMC: 2


On going through few DB2 sites i was able to find that SQLSTATE: 40001 is got when we have an deadlock situation. But i was not able to find the SQLCODE matching to the one we get in our logs. Some one please explain as to what this code means and is it interrelated to deadlocks. This happens during finding the next trigger to fire using quartz job scheduler.

Hi Amar,
I am getting the same exception while working with Weblogic8.1, DB2 and Quartz. If you have solved the problem, please post the solution here.

Thanks..
Premit
Mar 1 '07 #2

Post your reply

Sign in to post your reply or Sign up for a free account.