SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
02-26-2008, 02:44 PM
| ||||
| ||||
 idthtoin and db2 lock contention We are having a contention problem with Excel users querying a DB2 for z/OS table and their threads remaining active, holding locks. Periodically during the day, the same table gets loaded with the DB2 LOAD utility, but gets a -911 or -904 if the Excel thread is still in an active, idle state holding locks. If these threads would terminate at completion, I don't think we'd have the contention problem. IDTHTOIN is set to 900 seconds. When the same query is entered from Access, the window closes automatically, locks are released and the thread terminates. A couple of questions: 1) Should I just change IDTHTOIN to a lower number like 60 seconds? Adverse implications? What are other installations using? 2) Is there something I can do on the client side to get Excel queries importing data from DB2 to behave like the Access ones - i.e., commit and release locks upon completion of the data return.      |
 |
« Trigger & stored procedure to archive deleted records
|
Running procs and scripts from the Liux command line »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 01:44 PM.
