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 Submitted
Workspace Db2
Created by Guest
Created on Nov 30, 2024

Make SET TENANT available in connect procedure

The new Db2 release 12.1 provides the namespace isolation via tenant feature.
Default is the SYSTEM tenant.
The tenant feature is ideal to replace small personal databases for developers where many may have the same sets of tables and also in the same schema.

To achieve maximum separation and to prevent users from accidentally creating objects in the wrong tenant, and especially in the system tenant, the preferred way would be to not rely on the user having to do SET TENANT or rely on the use of jdbc parameters.

The most obvious way to do this would be to SET TENANT = SYSTEM_USER at login time through the use of a connect procedure.

Unfortunatelly trying that brings a

SQL0270N Function not supported RC 127.
127: The SET TENANT statement is not supported inside a routine

Without the ability of providing a tenant other than SYSTEM from database side migration of existing applications might also be blocked due to the code change.

This is especially true for software provided by third parties where you don't have the chance to change anything.

Needed By Quarter