ITM Agent Insights: Typical Errors seen while running TCR 3.X reports
ssnachan 0600020S7X Visits (4738)
In this blog I will try to capture the typical error (Data Source) connection errors that are received while running out of the reports provided by any product reports imported in Tivoli Common Reporting (TCR) 3.X. As you know, TCR 3.X is offered via. Jazz for Service Management (JazzSM) offering. The product reports once imported require a data source connection. This connection is established between the TCRDB (Content Data Store) and TDW (Warehouse Database which holds the historical data). When a data source connection fails there are errors generated. These errors differ in verbiage based on the operating system used.
NOTE: The assumption here is that DB2 is used to host both the Content Data Store as well as the historical database.
Error 1: Pertains to DB2 client library libdb2.a not being loaded
QE-DEF-0285 The logon failed.
QE-DEF-0325 The logon failed for the following reason:
RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
UDA-SQL-0569 Unable to load the driver manager library ( libdb2.a(shr.o) ).
UDA-SQL-0571 The operating system returned an error message ( 0509-022 Cannot load module shr.o.
0509-026 System error: A file or directory in the path name does not exist. ).
BME-EX-0144 Trace back:
Script Stack Trace
Action No=1 Action Name
As I mentioned before the text of the error messages change based on the operating system used. In this case, the failure revolves around the libdb2.a - DB2 client library not being loaded. This is on an AIX OS. Both the 32-bit and 64-bit libraries are needed, in many cases 64-bit library gets sourced in the Cognos directory however the 32-bit library is missing. It is important to locate these libraries and ensure they exist in the Cognos path as well. Use the following steps to resolve this issue:
- Run find / -name libdb2.a (this will locate both the 32 and 64 bit client libraries in DB2 home)
- Copy the 32, 64 bit or both libraries into the Cognos path which is sourced for the data connection.
- Once this is done restart the JazzSM (WAS) server.
Example (assuming JazzSM server is server1):
- Login in to the Common Reporting portal again and run the reports. You should be able to run the reports without any problems.
NOTE: Depending on the operating system the following environment variables are set and the DB2 library names may differ accordingly. Use the same steps mentioned above to resolve the issue.
I will continue to capture error messages as I run into them moving forward.
Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM
Subscribe and follow us for all the latest information directly on your social feeds: