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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
Enhance ALTER STOGROUP DROP ‚storage-path’ with optional specification of the Path_ID
As you may ADD the same path multiple times to a storage group (in order to have multiple containers of a single tablespace within that path), it should be possible to even DROP a single reference to that path from the storage group as well! But so far there’s no option to specify the unique path ID to precisely identify the path to be dropped! if you specify the storage-path, which occurs multiple times within the storage group, Db2 will try to drop ALL of the entries for that path, which will remove ALL containers from that path.
Thus the ALTER STOGROUP command should allow to optionally specify the path ID along with the path name to uniquely identify the path entry to be removed.
In order to reduce cost for storage, which is not really used, a multiple specification of the same path within a storage group would allow to unevenly distribute tablespace containers between storage pathes pointing to file systems of different sizes!
Using AUTOMATIC STORAGE makes DBAs life easier, but you will have to monitor file system usage in order to get alerted if storage becomes short for the databases, but which threshold should you use, if a smaller FS can become 100% full, before tablespaces are further extended on a larger file system? Managing hundreds of databases it’s needed to have data balanced over file systems of different sizes to use the same alerting threshold value for ALL file systems use by Db2.
Do not place IBM confidential, company confidential, or personal information into any field.