Troubleshooting
This chapter describes some common problems
you may encounter.
For more troubleshooting problems, see the IBM Cognos Business Intelligence Troubleshooting Guide.
- Performance optimization for IBM Cognos Analysis Studio
To avoid performance and usability issues with analysis in IBM® Cognos® Analysis Studio, you must use the appropriate techniques to build your analysis. - Error Characters (--) Appear in Reports
When you run a report, you see two dash (--) characters in your report instead of values. - Cannot load metadata tree for a PowerCube requiring both a Series 7 and a cube password
You cannot load a data tree if it is created from a Series 7 PowerCube. - Charts in PDF Output Show Unexpected Results
Charts, when viewed in PDF output, have different levels of interaction support, depending on the version of Adobe Acrobat Reader and the style of chart element. - Unexpected Results for Analysis Studio Reports Using Suppression and Nested Rows
In IBM Cognos Viewer, you run an IBM Cognos Analysis Studio report for which page breaks have been set. Detail items appear only on the page that contains the item for which suppression is applied, and only summary items appear on all other pages. - Defining Languages for OLAP Data Sources
The first time you publish a cube definition to IBM Cognos Connection, you must identify all the languages that represent the data contained in the cube. If you add a language to the model after the cube is published, users with locales that match the added language locale may find that Analysis Studio does not recognize references to the member unique names. There is no impact on users whose locale matches the original language list. - Crosstab Shows Percentage But Chart Shows Values
When the crosstab calculates the percentage of the total for an item, the chart does not show the values as a percentage. - Cannot Drill when Caption Represents a Blank or a Zero-length String
A dimensional model over relational data may return a zero length or blank caption in the row or column in Analysis Studio. When it does, you cannot drill up or down from the set because no link appears. - Performance Issues when Showing Multiple Attributes Using Dimensionally-modeled Relational Data Sources
If you display multiple attributes for the items in a set on the crosstab, you can only select one attribute at a time, so Analysis Studio executes a query for each attribute selection. - Error Occurs in Japanese Internet Explorer 7 When Running an Excel Report in Analysis Studio
An error may occur when you close Japanese Microsoft Internet Explorer 7 installed on Microsoft Windows XP SP2 while it is running an Analysis Studio report in Excel format. - Metadata Change in Oracle Essbase Not Reflected in Reports and in the Studios
When there is a metadata change on the Oracle Essbase server, the change is not immediately reflected in the metadata tree in the studios. In addition, when a report is run, the report does not pick up the republished changes. - Report Differences Between TM1 Executive Viewer and IBM Cognos Business Intelligence with TM1 Data Sources
When using an IBM Cognos TM1® data source, comparable reports created in an IBM Cognos Business Intelligence studio and in TM1 Executive Viewer may contain different cell values. This occurs because the TM1 Executive Viewer product uses an algorithm for selecting default members for non-projected dimensions that differs slightly from traditional OLAP clients. - Measure Format Disappears in SSAS 2005
Microsoft SQL Server 2005 Analysis Services (SSAS) does not propagate formatting through calculations. IBM Cognos compensates for this whenever possible, but cannot guarantee to do so in all cases. As a result, if you are working with a Microsoft SSAS cube, any calculation (other than a non-count summary) that is based on or intersects with a formatted measure, such as a currency, may lose the measure format. This may also happen if you use a detail filter or context filter (slicer).