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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Planned for future release
Workspace Db2
Created by Guest
Created on Mar 11, 2019

Add option :statement rollback is able to release the locks for the failed statement.

When -803 ( violating unique key constrain ) happen on a statement, there are two things happen
1) db2 still hold the lock on the row accessed by the statement that cause -803 , no matter the statement had fail.
2) The transaction was not rollbacked.

This is WAD, we db2 won't rollback the transaction when -803 happen.

It has always been the behavior in index manager in Db2 to keep the lock on the duplicate row found when sqlcode -803 is returned. To change that could break existing applications that may depend on that lock to guarantee that the duplicate that was found, continues to exist for the duration of the transaction that got the -803 error.
An example of such an application may be the following where there is a unique index on the first column, col1.
insert into table1 values (1, 1000)
if -803 is returned then update t1 set col2 = 1000 where col1 = 1
In this case the transaction expects the row with col1=1 to continue to exist.

This may not be the desired behavior for everyone but to change it could break any application depending on this behavior.
Therefore, we can not change this WAD.

On the otrer hands, it is very strange for end user, because failed SQL leaves unrecognized locks and they cause deadlock.
In this case it is desirable to be rollbacked.

We think that Db2 should provide the option of which action to choose.
We hope to add options allowing the user to choose to roll back.