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 Under review
Workspace Db2 for z/OS
Created by Guest
Created on Apr 24, 2024

One-Fecht Index Scan for SELECT min(), max()

At the moment only a single SELECT min(a) or a SELECT max(a) uses a suitable index I(a, ...).

When selecting both, min() and max(), a tablespace scan is used to determine the minimum and maximum value. With large tables this behaviour is very expensive and could easily be avoided with a lookup at the beginning leaf node and ending leaf node of the index. A messy workaround is at the moment possible e.g. with a subquery in the SELECT-statement (SELECT min(a), (SELECT max(a) from t) from t)).

The related documentation, where it is listed that a one-fetch index access only occurs either by min or max: One-fetch access (ACCESSTYPE='I1') - IBM Documentation

Needed By Yesterday (Let's go already!)