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 Employees should enter Ideas at

Status Not under consideration
Workspace Db2
Components Other/Unknown
Created by Guest
Created on Feb 11, 2021

Automatic Lock-Escalation from Row- to Extent-Level

Db2 is mainly using row-level locking and tries to avoid lock-escalation to table-level. This behavior is helpful in most of Db2s use cases, but there are some particular situations when locking on a higher level than row would be beneficial. Consider a kind of Data Warehouse environment which contains data for a defined time window, e.g. the last 2 years (24 months).

New data is inserted into the Db2 tables and 'old' data is deleted. The new data is inserted 'en bloc', physically stored beneath each other in continuing pages/extents. The removal of the old data deletes the continuous rows.

These actions process several millions of rows, acquiring at least several millions of rows. If Db2 would detect the 'mass insertion' and 'mass deletion' as a sequential operation which locks a significant mount of rows in an extent, Db2 could 'escalate' the locking level from row to extent.

On the one hand this would reduce the resource consumption without on he other hand reducing the concurrency (since a significant amount of rows per extent must be locked anyway).

Needed by Date Apr 30, 2021