This section contains general known issues. This includes issues that affect more than one IBM Cognos 8 component, such as Query Studio and Report Studio. Issues that affect just one component are described in the section for that component.
There will be no currency symbols, units of measure, or other formatting applied when data is returned from the cubing services technology of IBM InfoSphere Warehouse. This applies to Report Studio, Query Studio, and Analysis Studio.
To resolve this issue, manually apply the required formatting in reports.
603133
The select * from <table> syntax does not work in IBM Cognos 8 if the referenced table was created using the VERCOLS option.
When running a query in IBM Cognos 8, error messages similar to the following are displayed:
This query contains an error and can not be executed.
It is recommended that you view the query feedback on the Query Information tab.
RQP-DEF-0177 An error occurred while performing operation 'sqlPrepareWithOptions' status='-3'.
UDA-SQL-0283 Metadata describing "select * from 'gosales1'.country" does not match results from the database.
To resolve these errors, do one of the following, then re-run your query.
If possible, create the table without the VERCOLS option.
Specify all the required columns by name in the select statement.
When you open a PowerCube in an IBM Cognos 8.3 Web studio or in IBM Cognos 8 Business Intelligence Mobile Analysis 8.3, you may notice changes in the number of default decimal places shown in currency formats.
This behavior is due to the following changes:
The default decimal formatting in currency formats is now determined by the measure format selected in the cube, instead of from the data source Currency Table definition.
For example, if the Actual Revenue measure format specifies two decimal places and the USD currency in the Currency Table specifies no decimal places, two decimal places will now be shown in the USD currency value.
Calculations that include a division operator and at least one currency operand will now show a resulting value with three decimal places only when
neither of the currency values includes decimals
two currency operands have different numbers of decimal places
In all other calculations of this type, the number of decimals in the resulting value will be determined by the number of decimals in the currency value. The following examples illustrate this new behavior:
$4.00 / $2.00 = $2.00
$4 / $3.0000 = $1.3333
$4 / $3 = $1.333
$4.0 / $3.00 = $1.333
For more information about measure formats or currency tables, see the Transformer online help.
545573, 545408, 545427, 546183
When viewing documentation with Adobe Reader version 7, some extended characters (notably the é character) display as dots (.), and the font is different from that used for the rest of the bookmarks.
To resolve this issue, upgrade your copy of Adobe Reader to version 8.
In TM1 data sources, administrators can secure elements within a dimension so that they are visible only to certain users. However, in IBM Cognos 8, a visible path must exist from each element to the root of the hierarchy. It is possible to secure sub-trees of a TM1 data source hierarchy, but each element in the sub-tree must be secured.
For example, consider the following hierarchy for Total Business Unit:
Europe
UK
Germany
North America
Canada
United States
Asia Pacific
Australia
Japan
In this example, if only the North America element is secured, leaving the Canada and United States elements visible to all users, the path of accessible elements is impeded. IBM Cognos 8 users may receive messages explaining that inaccessible members were encountered.
If the entire sub-tree of North America, Canada, and United States is secured, IBM Cognos 8 will report correctly because there is a direct, visible path from the lowest level of data in the hierarchy to the highest level of data.
To reliably detect this situation, please install TM1 build number 9.4.00001.576.
606308
TM1 data sources can include rule-derived cells. IBM Cognos 8 cannot identify these rule-derived cells ahead of time, so performing an aggregation on these cells may yield unexpected results. For example, aggregating a set containing a rule-derived value may produce unexpected results in Report Studio and Analysis Studio.
Note: Explicit aggregation operations like sum, average, count, minimum, and maximum are not affected.
If you are using TM1 data cubes with rule-derived cells in IBM Cognos 8, we recommend that you install TM1 build number 9.4.00001.576, which identifies aggregation errors by marking the error cells with dashes (--).
592809.3
Using either Report Studio or Analysis studio, you cannot load the metadata tree for a Series 7 PowerCube. With Internet Explorer 7 enabled to show warnings and errors, you are waiting to be prompted for both a Series 7 namespace and a PowerCube password. The following error is shown:
element not found
This problem may occur if you register the file shdocvw.dll after installing Internet Explorer 7.
To fix the problem, follow these steps:
From the Windows Start menu, click Run.
In the Open box, type regedit, and then click OK.
In the Registry Editor, go to the registry branch:
HKEY_CLASSES_ROOT\TypeLib\{EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B}\ 1.1 \0\win32
Double-click (default) and set C:\WINDOWS\system32\ieframe.dll as the value data.
Click OK, and then close the Registry Editor.
608677
If the target of a drill-through definition is an Analysis Studio report with a drill-through filter, and the application has been upgraded from IBM Cognos 8 version 8.3 to IBM Cognos 8 version 8.4, then filters may not be correctly passed from the source to the target. Instead, the Analysis Studio report appears with the authored settings unchanged, or users may be prompted to select a context.
This is true for authored drill-through definitions (created in a Report Studio report) and package drill-through definitions (created in Cognos Connection) that use parameterized drill through.
This problem occurs because of changes in how parameters are automatically named in Analysis Studio. To correct the problem, recreate the mapping in the drill-through definition, and save the definition.
In Report Studio, Professional Authoring, open the source report.
Select the report item that contains the drill-through definition.
From the Properties pane, open the drill-through definition (Data, Drill-Through Definitions).
From the Drill-Through Definitions window, open the Parameters table, and re-select the target parameter(s).
Save the drill-through definition settings and then save the report.
Test the drill through to confirm that the problem is resolved.
For more information, see the Report Studio Professional Authoring User Guide.
In IBM Cognos Connection, launch Drill-through Definitions.
Navigate to the root of the source package, locate the drill-through definition to be updated, and click Set Properties.
In the Target tab, under Parameter mapping, re-select the target parameters.
Save the drill-through definition.
Test the drill through to confirm that the problem is resolved.
For more information, see the IBM Cognos 8 BI Administration and Security Guide.
607932
TM1 cubes and IBM Infosphere Warehouse Cubing Services have the same level of drill-through support within IBM Cognos 8 as other OLAP sources.