Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 Submitted
Workspace Db2
Components Db2 on-premise
Created by Guest
Created on Apr 14, 2026

Provide a dedicated metric to monitor the exact physical/logical size of individual indexes separately

Problem Statement & Real-life Scenario: In large-scale enterprise environments (e.g., SAP on Db2 and etc), tables often have dozens of indexes. Currently, built-in routines such as ADMIN_GET_INDEX_INFO only return the aggregated size of ALL indexes defined on a table (or data partition) for the INDEX_OBJECT_L_SIZE and INDEX_OBJECT_P_SIZE metrics. When a table's total index object size grows exceptionally large, DBAs cannot identify which specific index is the root cause of the abnormal growth.

Current Workaround(s): There is no official or technical workaround to determine the exact physical and logical disk space allocated for a single, specific index. DBAs are forced to treat the index object as a single black box.

Proposed Solution(s): Introduce a new administrative routine (e.g., a table function) or extend existing catalog views to report the exact P_SIZE and L_SIZE strictly at the individual index level (INDNAME / IID), regardless of whether the table is partitioned or non-partitioned.

Benefits/Value & Impact: This capability is crucial for advanced database administration. It enables DBAs to perform precise capacity planning and proactive storage tuning. Specifically, it allows us to calculate the exact expected storage reclamation ROI before dropping unused or redundant indexes. This impacts all enterprise DBAs who manage storage daily.

Needed By Quarter
  • Guest
    Apr 17, 2026

    I strongly support this proposal.

    Providing granular P_SIZE and L_SIZE metrics at the individual index level (INDNAME/IID) will enable:

    1. Precise ROI Analysis: Accurate estimation of reclaimed space before dropping unused indexes.

    2. Effective Maintenance Planning: Identifying exactly which index requires a REORG or compression.

    3. Proactive Capacity Management: Better visibility into storage growth patterns.

    This is a much-needed enhancement for modern database administration.

  • Guest
    Apr 15, 2026

    I’m all for it. This is a must-have feature for our workf