IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Sep 21, 2015

Real-time statistics with statistics profile can lead to deadlocks and lock timeouts

DB2 real-time statistics facility honors RUNSTATS options specified in the statistics profile, while performing synchronous statistics collection during statement compilation.

If the statistics profile contains ALLOW READ ACCESS option, this can lead to additional table-level S-locks being acquired (and waited for) the table of interest. Depending on other executed statements, and, specifically, having an IX-lock on the same table due to previous DML activity in the same transaction, this can lead to lock timeouts and/or deadlocks of the synchronous RUNSTATS execution.

As a result, statement execution fails at the compilation phase with error SQL0911N.

A workaround is to avoid setting ALLOW READ ACCESS option in the statistics profile. However, this option might give benefits in other situations - such as asynchronous RUNSTATS execution performed by the automatic maintenance tasks.

It would be better if RTS would ignore the ALLOW READ ACCESS option during synchronous statistics collection, allowing this option to be set for use by automatic maintenance tasks.