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:
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
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Assuming that there is more than one temp tablespace with the same page size and 'IN TABLESPACE' clause is not specified in the DECLARE GLOBAL TEMPORARY TABLE command, then DB2 optimizer should allocate the temp tables across all temporary tablespaces of the page size and not just in one temp tablespace.
According to IBM documentation from the following link, DB2 optimizer will create new user temporary tables in round robin fashion if more than one user temporary tablespace of same page size exists. This is assuming that the 'IN TABLESPACE' clause has not been specified in the DECLARE GLOBAL TEMPORARY TABLE statement and all the users are granted 'USE IN' tablespace permission on all the temporary tablespaces.
In our environment, we are hitting the limit on maximum number of tables created in a user temporary tablespace (SQL0960C). We have several 100's of stored procedure where temp tables are created. Since the stored procedures are compiled/bound by the instance owner it doesn't make a difference that the user, who is executing the stored proc, has been granted USE of a specific temp tablespace. Regardless of that permission the temp table is getting created in the same temp tablespace. We had the following PMR opened with IBM with regards to this.
Do not place IBM confidential, company confidential, or personal information into any field.