This document is intended to provide a troubleshooting methodology which incorporates publicly available utilities to diagnose and resolve an issue identified within a specific use case. The use case will be presented as a scenario where an IBM Cognos Support Analyst is working with a client to diagnose and solve a particular issue.
The utilities mentioned in this document can be found at http://www.ibm.com/software/analytics/support/cognos_sdk.html.
Although the troubleshooting approach outlined is not IBM Cognos BI version specific, some of the diagnostic utilities used are. The version of the utility to be downloaded will be specific to the IBM Cognos BI version that is experiencing the issue.
Use Case Description
In this particular scenario, the administrator notices that the IBM Cognos BI Content Store is growing in size significantly day after day in a way that he cannot explain.
Troubleshooting the Use Case
As with troubleshooting any use case, a set of basic information needs to be collected in order to further clarify the environment and the issue at hand.
The environment consists of a single server install with the following details:
- IBM Cognos BI version: 8.4.1
- Operating System: Windows 2003
- Content Store Database: Microsoft SQL Server 2008r2
The support analyst asked the administrator to down load the IBM Cognos BI Content Manager Size Diagnostic utility from the following URL,
NOTE: This utility is also available in most IBM Cognos BI versions under the bin/utilities/diagnostictools sub-directory of the IBM Cognos BI installation directory.
The IBM Cognos BI Content Manager Diagnostic utility reports the size and count of all objects in the Content Store database. Within specified search scope and type of objects, it returns the count, approximate size and Content Store search path of the object.
In order to look at the entire Content Store, the administrator logs in with an IBM Cognos BI System Administrators account. What they find are about 1500 reports and about 15 reports that have a large size of saved outputs in public folders.
The IBM Cognos Support Analyst tells the administrator to run this utility every day, for several days and monitor the activity.
What the administrator found after a few days of monitoring is that the number of reports is staying the same but the 15 reports with large report outputs are growing very significantly.
The administrator then checks on the reports from IBM Cognos Connection and finds that these are all bursted reports being sent to over 1000 users. In addition, 30 versions of the report output for each user are being saved to the Content Store. The administrator goes off to work with his colleagues to find out if the bursted reports still need to be sent to all the 1000+ users and if the number of report outputs that are saved for each user can somehow be reduced.
Dig deeper into Big data and analytics on developerWorks
Get samples, articles, product docs, and community resources to help build, deploy, and manage your cloud apps.
Experiment with new directions in software development.
Software development in the cloud. Register today to create a project.
Evaluate IBM software and solutions, and transform challenges into opportunities.