IBM Support

ITM Agent Insights: Missing summarized data in the "Unix Memory" and "Disk" DB2 data warehouse tables after the upgrade to 6.30 FP5

Technical Blog Post


Abstract

ITM Agent Insights: Missing summarized data in the "Unix Memory" and "Disk" DB2 data warehouse tables after the upgrade to 6.30 FP5

Body

The  6.30 FP5 Sumarization and Pruning agent fails to write data into the DB2 data warehouse hourly, daily, weekly, monthly, quarterly and yearly summarized tables of the Unix Memory and Disk groups. This issue applies only to DB2 data warehouse.

 

Because of a set of  new attributes introduced  by the 6.30 FP5 UNIX OS Agent into the "Unix Memory" and "Disk" attribute groups the size of the summarized warehouse tables for these groups has crossed the 4K DB2 tablespace boundary.  As a consequence the Summarization and Pruning agent fails in adding the new columns to these tables' definitions . The following kind of error can be found in the Summarization and Pruning RAS1 logs:

== 3720 t=work2 SQL IN ERROR :                                            
statement name     : Unix_Memory_H.Alt1 SQL

                               : ALTER TABLE "ITMUSER"."Unix_Memory_H" ADD  "AVG_MR" DECIMAL (31, 2)   

                                 template SQL                                          
== 3721 t=work2 SQLException occurred. SQL State = 54010 , SQL Error Code  = -670  

== 3722 t=work2 com.ibm.db2.jcc.am.SqlException:

The statement failed because the row size of the resulting table would have exceeded the row size limit. Limit: "4005". Table space: "USERSPACE1".. SQLCODE=-670, SQLSTATE=54010, DRIVER=3.65.110     

Because of this error no new rows can be written into the hourly, daily, weekly, monthly, quarterly and yearly summarized "Unix_Memory" and "Disk" tables.

Even if raw data warehouse tables are not affected by this issue, it may rapidly lead to a loss of information or to inaccurate historical data depending on the configured pruning frequencies.

This problem is tracked via APAR IV75908 "THE SUMARIZATION AND PRUNING AGENT FAILS IN SUMMARIZING HISTORICAL DATA FOR THE UNIX OS AGENT "UNIX MEMORY" ATTRIBUTE GROUP" and APAR IV79257 "FAILURE COLLECTING "DISK" SUMMARIZED HISTORICAL DATA INTO DB2 WAREHOUSE"
                      
In order to solve this issue it is necessary to run a set of SQL warehouse upgrade scripts that move the "Unix_Memory" and "Disk" summarized tables into the 8K DB2 tablespace.  These scripts are named:

kux_63migr_Memory_H.sql
kux_63migr_Memory_D.sql
kux_63migr_Memory_W.sql
kux_63migr_Memory_M.sql
kux_63migr_Memory_Q.sql
kux_63migr_Memory_Y.sql

kux_63migr_Disk_H.sql
kux_63migr_Disk_D.sql
kux_63migr_Disk_W.sql
kux_63migr_Disk_M.sql
kux_63migr_Disk_Q.sql
kux_63migr_Disk_Y.sql


Files for APAR IV75908 (kux_63migr_Memory_*.sql) are included in the 6.3.0.5-TIV-ITM_UNIX-IF0002 UNIX OS Agent Interim Fix  as part of the UNIX OS Agent TEPS support files, as well as included in 6.30 FP6.

 

Files for APAR IV79257 (kux_63migr_Disk_*.sql) are included in the 6.3.0.5-TIV-ITM_UNIX-IF0003 UNIX OS Agent Interim Fix  as part of the UNIX OS Agent TEPS support files, as well as included in 6.30 FP7.

 

The procedure is the same as the one documented for the "System" summarized tables in the Appendix A "Upgrading your warehouse for primary key and tablespace changes" of the UNIX OS Agent Reference Guide.

 

Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM Agent Insights: Introduction.

 

 

 

Tutorials Point

 

Subscribe and follow us for all the latest information directly on your social feeds:

 

 

image

 

image

 

image

 

 

  

Check out all our other posts and updates:

Academy Blogs:https://goo.gl/U7cYYY
Academy Videos:https://goo.gl/TLfMoF
Academy Google+:https://goo.gl/HnTs0w
Academy Twitter :https://goo.gl/AhR8CL


image

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""}]

UID

ibm11084971