Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


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.

Status Delivered
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Dec 2, 2020

Make the number of concurrent copies of plan cache SQLs a dynamically configurable parameter

We have a very serious need to increase the number of concurrent copies of SQLs in the plan cache well beyond the current hard-coded limit of 3 copies. We currently have 631 production schemas, each with the same database and SQLs. It's a separate-schema, multi-tenancy database.

Our plan cache is at full size, but has many old SQLs. I believe we are "spinning" the 3 copies of highly used SQLs, while leaving much of the cache stale. Increasing the number of copies of concurrent SQLs will allow more frequently used SQLs to take their place. Our plan cache hit ratio is regularly dropping below 80% and occasionally below 75%, because of this.

And, of course, we would like this to be dynamically configurable.


Use Case:

I'm not sure what you want for a use case, but I want to be able to change the number of copies allowed in the statement cache and have it take effect immediately.


Idea priority Urgent
  • Guest
    Reply
    |
    May 14, 2021

    An enhancement was delivered in spring 2021 with IBM i 7.4 PTF Group level 13 and IBM i 7.3 PTF Group level 24 that should help with this type of plan cache situation.

    The QSYS2.CLEAR_PLAN_CACHE procedure was extended to allow clearing specific plans from the plan cache based on the QRO hash values and the plan identifier. This control allows you to remove plans that you believe should no longer be used.

  • Guest
    Reply
    |
    Mar 9, 2021

    IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements an enhancement for plan cache pruning.

  • Guest
    Reply
    |
    Jan 16, 2021

    IBM will use this request as input to planning but no commitment is made or implied. This request will be updated in the future if IBM implements it.

    We are working with the submitter to understand the situation that occurred. We are also considering an enhancement to permit targetted user pruning of the plan cache.

  • Guest
    Reply
    |
    Dec 14, 2020

    I see this has 7 votes now. What is the next process for this? When will IBM's DB2 team review this?