Why are my Tivoli Common Reports failing after the turn of the year?

Body

Every year after the turn of the year, some clients are surprised that after the 01.01. their Tivoli Common Reports are not longer working. The reason and solution is easy and caused by the TIME_RANGE_END date in the IBM_TRAM.TIME_DIMENSION table.

When you run an ITM  Warehouse Database on DB2 run the following commands:
                  su - db2inst1
                 db2 connect to warehous user itmuser using <itmusers password>
                 db2 "select min(TIME_RANGE_START) MIN_DATE, max(TIME_RANGE_END) MAX_DATE from IBM_TRAM.TIME_DIMENSION"

you will get a result like;

            MIN_DATE                                       MAX_DATE
---------------------------------------       ----------------------------------------
2016-01-01-01.00.00.000000        2017-12-31-00.59.59.000999

                                  1 record(s) selected.

  
If the MAX_DATE is 2017-12-31-00.59.59.000999 run the following command to enlarge the TIME_RANGE_END

                  db2 call IBM_TRAM.CREATE_TIME_DIMENSION('2018-01-01-00.00.00.000000','2023-12-31-00.00.00.000000', 60)

When you have an Oracle or Microsoft SQL Database for your IBM Tivoli Monitoring Warehouse, so please have a look at:

Creating and populating the time dimensions tables
https://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/adminuse/tcr_reports_dimensionsshared.htm 

PS: the mentioned db2inst1 is the instance owner of your Warehouse instance and itmuser the name of the Warehouse schema. This can be a different name on your system.

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