Locking Parameters

You may also like...

4 Responses

  1. ravinaga says:

    gud one..

  2. Luke Numrych says:

    There is a locking-related (or concurrency-related) mechanism, added in db2 9.7 – the currently committed semantics (http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.perf.doc/doc/c0053760.html?cp=SSEPGG_9.7.0%2F2-3-2-7-1-2). It is configured on the database level, with the database configuration parameter cur_commit. I am wondering if you have seen it used anywhere?
    I tried to implement it in databases for an applications that seems to have concurrency issues (lock waits…). However, my while my proposal was generally accepted as a viable solution, I could not get the app development team to actually take a stand and either approve or disapprove of the idea…

    • Ember Crooks says:

      I’ve seen it used in nearly every 9.7 and above database that I’ve supported. WebSphere Commerce supports currently committed semantics, and many other applications do too. A large part of why they support it is because it is somewhat similar to how Oracle handles locking.

  1. March 28, 2012

    […] Parameters: http://db2commerce.com/2012/01/09/locking-parameters/ Share this:ShareEmailIf you enjoyed this post, please subscribe!  Subscribe in a reader or by […]

Leave a Reply

Your email address will not be published. Required fields are marked *