IBM Support

No historical collection on TEPS.

Technical Blog Post


Abstract

No historical collection on TEPS.

Body

image

No historical collection on TEPS.

A customer reported that they were unable to see details of historical collections previously set up
on the TEPS and were unable to see details for new agents added.

Although the TEPS is used to configure the details of historical collection the data is stored in the warehouse database not in the TEPS database.


So in a case like this the first thing to check is if the TEPS can connect to the warehouse.

It is in the *cq*.01.log and there should be line something like:

(5720DCE2.0000-170C:ctreportcache.cpp,225,"CTReport::ReportCache::fetchWarehouse") Warehouse found for 'ITM Warehouse', SQL type = 'ODBC'.
(5720DCE2.0001-170C:ctreportcache.cpp,246,"CTReport::ReportCache::fetchWarehouse") Warehouse 'ITM Warehouse' table name max: 128, column name max: 30.
(5720DCE2.0002-170C:ctreportcache.cpp,263,"CTReport::ReportCache::fetchWarehouse") Warehouse 'ITM Warehouse' is CT400 format.
(5720DCE2.0003-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   ---> name = Data source for Warehouse is:
(5720DCE2.0004-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -1022 = "ITM Warehouse"
(5720DCE2.0005-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -1023 = "IBM DB2 ODBC DRIVER - DB2COPY1"
(5720DCE2.0006-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -2507 = "ODBC"
(5720DCE2.0007-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -2554 = true
(5720DCE2.0008-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   ---> name = Data source for Warehouse details:
(5720DCE2.0009-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -1022 = "ITM Warehouse"
(5720DCE2.000A-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -1023 = "DB2CLI.DLL"
(5720DCE2.000B-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -2507 = "ODBC"
(5720DCE2.000C-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -2509 = "DB2"
(5720DCE2.000D-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> -2511 = "ITMUser"
(5720DCE2.000E-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> SQL_DBMS_NAME = "DB2/NT64"
(5720DCE2.000F-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> SQL_DBMS_VER = "10.01.0000"
(5720DCE2.0010-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> SQL_DRIVER_VER = "10.01.0000"
(5720DCE2.0011-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> SQL_IDENTIFIER_QUOTE_CHAR = """
(5720DCE2.0012-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> SQL_MAX_COLUMN_NAME_LEN = 128 L
(5720DCE2.0013-170C:ctpropertysequence.cpp,738,"CTPropertySequence::Dump")   -----> SQL_MAX_TABLE_NAME_LEN = 128 L

depending on what RDBMS is used and what the database is called.

For this customer it had :

(5720DCE2.0013-F:ctreportcache.cpp,203,"CTReport::ReportCache::fetchWarehouse") No Warehouse found for 'WAREHOUS'.


 This indicates that the warehouse database can't be reached, but this can be for a number of reasons.

First steps are to check that DB2 (or other RDBMS) is running, then that WAREHOUS (or what name you have called the database)  is defined and active.

That can be as simple as checking for the processes on the machine and doing a connect to the database via SQl commands.
In a large complex environment this may need to be checked with the RDBMS Administrator.

If that is up and running, the next check is network, can you ping between the TEPS machine and the machine that the warehouse is on.

In this case this was all checked and everything was working,
it was then acknowledged that there had been a change to the location of the warehouse database.

If there is a change to your warehouse along with changing the connections for the WPA and S&P agent; the TEPS needs to be updated.

This is done by running a reconfigure on the TEPS, and supplying any changes to connection to the warehouse database.


Once this was done then the previously saved historical collections could be seen and new collections configured.

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:  http://ow.ly/Otue0
Academy Videos:  http://ow.ly/PIKFz
Academy Google+:  http://ow.ly/Dj3nn
Academy Twitter Handle:  http://ow.ly/Dj35c

[{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"","label":""},"Component":"","Platform":[{"code":"","label":""}],"Version":"","Edition":""},{"Business Unit":{"code":"BU004","label":"Hybrid Cloud"},"Product":{"code":"SSZ8F3","label":"IBM Tivoli Monitoring V6"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":""}]

UID

ibm11084053