467,887 Members | 1,594 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 467,887 developers. It's quick & easy.

Problem with accessing 2 different tables using the same binary

Our system is on AIX5.3 ML5, DB2 v8.2 FP11, and we are running C applications.

There are 2 scheduled cronjobs, which are actually triggering the same binary, but passing in different parameter. With different parameters given, these 2 jobs are meant to do delete unused records from 2 different tables (there's no relationship between these 2 tables).

The scenerio is when the first job is still running (it takes longer when there are more records to be deleted), the second job get triggered. Looking at the application logging, it seems like the first job just stop there, and waiting for the second job to run finish, then it will continue running. But when it continues, it become very slow. Sometimes it managed to finish running, sometimes it'll exits with error.

There's no lock escalation in DB2 log files, but the number of lockheld keep increasing. The application is actually doing batch commit, but somehow the commit count doesn't increase while it keep taking up locks. No error captured in the db2diag.log either even when the application exits with error.

Anyone come across anything like this?

Also, wonder why the locktimeout didn't work as the application doesn't time out, but keep waiting until the second job finish, then continue to run again.
Aug 22 '07 #1
  • viewed: 1012

Post your reply

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

Similar topics

2 posts views Thread by Michele Belloli | last post: by
13 posts views Thread by lupher cypher | last post: by
4 posts views Thread by Leslaw Bieniasz | last post: by
11 posts views Thread by Abhishek | last post: by
39 posts views Thread by Martin Jørgensen | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.