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
Restrictions on ALTER TABLESPACE statements that cause pending changes:
ALTER TABLESPACE statements that cause pending changes have the following restrictions:
Options that cause pending changes cannot be specified with options that take effect immediately
Options that cause pending changes cannot be specified for the following objects:
Objects in a workfile database
An ALTER of PRIQTY is an immediate ALTER but the ALTER of COMPRESS is a pending alter and is not complete until a REORG is run. So when combined, the ALTER of PRIQTY is ignored. In this case, the ALTER of COMPRESS and PRIQTY should be done in separate DDL statements.
Though this is documented, it is doubtful most DBAs have reviewed the DOC that thoroughly. Since this action did not return a negative SQLcode, most DBAs would proceed under the assumption that the mixed DDL "took", and may not discover PRIQTY was lost until much later.
The DBAs need to be prompted to examine the documentation if they make an error in DDL such as this...I suggest a negative SQLcode be returned instead of allowing the operation to proceed.
Do not place IBM confidential, company confidential, or personal information into any field.