IBM Data and AI Ideas Portal for Customers


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:

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

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.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Delivered
Created by Guest
Created on Oct 30, 2018

Improve Performance of RTS Collection Process RFE 126577

 
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=126577

We are using Data Server Manager 2.1.5.1 and Autonomics Director 1.6 together to collect and save RTS stats for our tablespace objects on a 
weekly basis.  We have noticed progressively slower performance of this process over time to the point where it is now consuming a large amount of CPU.                                                                
                                                                       
We investigated this situation and found that the following SQL UPDATE statement was running very slowly.                                     
                                                                       
UPDATE SYSAUTO . SYSTABLESPACESTATS_HIST H SET H . SNAPSHOTTIME = CURRENT TIMESTAMP                                                      
WHERE H . UPDATESTATSTIME =                                            
( SELECT P . UPDATESTATSTIME FROM SYSIBM . SYSTABLESPACESTATS P        
WHERE P . DBNAME = H . DBNAME AND P . NAME = H . NAME AND P . PARTITION
= H . PARTITION AND P . INSTANCE = H . INSTANCE )                      
AND EXISTS ( SELECT 1 FROM SESSION . TEMP_OBJECTS_SNAPSHOT I           
WHERE I . DBNAME = H . DBNAME AND I . SPACENAME = H . NAME AND I .     
PARTITION = H . PARTITION )                                            
                                                                       
I subsequently ran this statement through the Query Workload Tuner tool to see how it could be improved.  The tuner results showed that this   
statement is doing a very expensive tablespace sequential scan on the 
SYSAUTO.SYSTABLESPACESTATS_HIST table.  The tuner indicated that adding
the following index would improve the statement performance by 99%!    
                                                                       
CREATE INDEX                                                           
"SYSAUTO"."SYSTABLESPACESTATS_HIST_VIRT_IDX_153971497095923067" ON     
"SYSAUTO"."SYSTABLESPACESTATS_HIST" ( "NAME" ASC, "DBNAME" ASC,        
"PARTITION" ASC, "INSTANCE" ASC )  NOT PADDED FREEPAGE 0 PCTFREE 10;   
                                                                       
Please investigate this issue and consider updating the Autonomics Director to include this index so that the RTS collection performance  
can be improved.

A similar index should probably also be      
defined on the SYSAUTO.SYSINDEXSPACESTATS_HIST  since a similar UPDATE  statement is probably being used to update this table as part of the RTS collection process.



Use Case
 
Collecting RTS stats on a regular basis is necessary to help determine when to reorg DB2 objects.  However, the process can be very CPU intensive and time consuming due to a lack of appropriate indexes on SYSAUTO tables.