Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


Status Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Aug 22, 2018

Inconsistent locking behaviour between DB2 data sharing and non data sharing environemnt

In below use case, the result is not consistent between data sharing and non data sharing or task B running on same member or different member in data sharing.
Client application team is asking for consistent locking behaviour between DB2 data sharing and non data sharing. They expect DB2 data sharing is transparent for application developer on application lock behaviour.

Use case:
lock request for same row
1) Task A on Member1 acquire U lock first
2) Task B on Member2 request X lock, which wait
3) Task C on Member1 reuqest S lock
4) Task A change request to X lock

Deadlock will happen in this case. But if Task B run on same member member1, it will finish sucessfully.
  • Admin
    Janet Figone
    Reply
    |
    Dec 17, 2020

    It is true that there is a difference in behavior in this scenario because the request to upgrade from U to X is allowed to go ahead of X waiters if the X waiter is local to the U lock. That optimisation is not possible if the waiter is on another member of the group. Removing this optimisation would have a serious negative impact on applications and there are no plans to do so. One option which could be considered would be to use the USE AND KEEP EXCLUSIVE LOCKS clause which would cause Db2 to acquire an X lock straight away and thereby avoid the need to upgrade later, but of course this option is not without negative repercussions either.