rdm_cr_updates

Cognos ® 8 Business Intelligence
README

Product Information
This document applies to Cognos ® 8 Version 8.3 and may also apply to subsequent releases. To check for newer versions of this document,
visit the Cognos Global Customer Services Web site (http://support.cognos.com).
Copyright
Copyright © 2008 Cognos Incorporated.
Portions of Cognos® software products are protected by one or more of the following U.S. Patents: software products are protected by one
or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188 B1; 6,728,697 B2; 6,741,982 B2; 6,763,520 B1; 6,768,995
B2; 6,782,378 B2; 6,847,973 B2; 6,907,428 B2; 6,853,375 B2; 6,986,135 B2; 6,995,768 B2; 7,062,479 B2; 7,072,822 B2; 7,111,007 B2;
7,130,822 B1; 7,155,398 B2; 7,171,425 B2; 7,185,016 B1; 7,213,199 B2; 7,243,106 B2; 7,257,612 B2; 7,275,211 B2; 7,281,047 B2; 7,293,008
B2.
Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks
or registered trademarks of their respective companies.
While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or
technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained
in this document.
This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements
or changes to either the product or the document will be documented in subsequent editions.
U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or
disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software
clause at DFARS 252.227-7013, or subparagraphs (C)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227-19,
as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803.
This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this
software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted
in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated.

Table of Contents
Introduction 9
Readme Updates By Date 11
Updated: February 6, 2008 11
Known Issues - SAP BW Data Sources 11
Known Issues - Report Studio 11
Updated: January 18, 2008 11
Known Issues - Transformer 11
Updated: January 10, 2008 11
Known Issues - Issues Affecting Multiple Components 11
Documentation Updates - Cognos 8 Administration and Security Guide 11
Updated: January 3, 2008 12
Documentation Updates - Cognos 8 Administration and Security Guide 12
Updated: December 21, 2007 12
Known Issues - Event Studio Issues 12
Updated: December 13, 2007 12
Known Issues - Report Studio Issues 12
Documentation Updates - Cognos 8 Administration and Security Guide 12
Updated: November 22, 2007 12
Known Issues - Analysis Studio Issues 12
Known Issues - Report Studio Issues 12
Updated: November 12, 2007 13
Known Issues - Administration Issues 13
Known Issues - Framework Manager Issues 13
Known Issues - Installation and Configuration Issues 13
Known Issues - Issues Affecting Multiple Components 13
Known Issues - Metric Studio Issues 14
Known Issues - Report Studio Issues 14
Known Issues - Transformer Issues 14
Documentation Updates - Cognos 8 Administration and Security Guide 14
Documentation Updates - Cognos 8 Installation and Configuration Guide 14
Documentation Updates - Cognos 8 Metric Studio User Guide 14
Documentation Updates - Cognos 8 Report Studio Professional Authoring User Guide 15
Deprecation Notices - Supported Environments 15
Chapter 1: Cognos 8 Known Issues 17
Administration Issues 17
Different User Interface When Cognos 8 Is Running on IBM WebSphere Application Server
Version 5.1 17
Drilling Through from a PowerCube to DMR Data Using the Time Dimension Members 17
A Validation Error Occurs in Cognos Connection When One of the Tabs in the Multi-page
Portlet Contains a Shortcut 17
Unable to View Past Activities in Cognos Administration with Cognos 8 Special Edition 18
Analysis Studio Issues 19
Readme 3

Table of Contents
Defining Languages for OLAP Data Sources 19
Crosstab Shows Percentage But Chart Shows Values 19
Cube Refresh in Data Analysis Studio Uses UTC/GMT Time 19
DB2 Data Sources Issues 20
Query Fails When Using DB2 OLAP Server 20
Unable to Open a Cube Using 8.2 DB2 OLAP or Essbase 7.1 21
Framework Manager Issues 22
Defining Repository Connections 22
Syntax of Macro Prompts 22
Oracle 10G Uses Zeroes Instead of Nulls for Non-Matching Values 22
Full Outer Joins Not Sent to Oracle 9i and 10GR1 23
Unable to Load DB2 OLAP Library in Framework Manager 23
Filter on SAP Attribute Is Ignored for Model Query Subjects If There Is No Business Key 24
Review Governors When Upgrading Models 24
Model Advisor Test Can Produce False Positive Results 24
Order of Transactions in Transaction History 25
BmtScriptPlayer Does Not Run Action Logs on UNIX Platforms 25
Changes to Transaction Log Files and the Transaction History List 25
Unable to Create Star Schemas, Merge Query Subjects, or Create Shortcuts Based on a
Read-only Project 26
Event Studio Issues 26
SQL Server Sample AssignStaff needs Modification 26
Go! Office Issues 27
bo:heap Buffer Overflow Error 27
Prompted to Log on For Each Imported Report 27
The Namespace Parameter is Case Sensitive 27
Cognos 8 Go! Office Automation Does Not Support SiteMinder Form-Based
Authentication 27
Installation and Configuration Issues 28
Cognos 8 Server May Fail to Start 28
Issues with IBM WebSphere 6.0 on AIX 5.3 28
Installation of WebSphere and IHS fails in Cognos 8 Special Edition 28
"db2 not found" error when installing Cognos 8 Special Edition 29
Cognos 8 does not Start on WebSphere 5.1 29
Gateway only Install of Cognos 8 Special Edition cannot access Cognos Connection
Portal 30
Application Tier only Install of Cognos 8 Special Edition does not Configure the Notification
Database 30
DB2 Server is not Registered after Install of Cognos 8 Special Edition 30
IBM WebSphere is not installed with Cognos 8 Special Edition 31
Non-ASCII Characters in Installation Directory Cause Run-time Errors 31
Copy Cognos 8 Go! Office Client Files to a Central LAN Location 31
Issues Affecting Multiple Components 32
Columns, Rows, or Data May Disappear Unexpectedly When Using SSAS 2005 32
Incorrect Values May Be Returned With Scoped Attribute Hierarchies in SSAS 2005 33
Changes to Decimals in Currency Formats 33
Metadata Change in Essbase Not Reflected in Studios 34
A Filter Definition Returns Character Set Mismatch Error Against Oracle Sample
Database 34
4

Table of Contents
Very Large Dimensions May Cause Denial of Service 34
Limited Support for Relational Functions When Used With OLAP Data Sources 35
Pivoting to a Crosstab Shows the Member of the Attribute 35
Report Layout Functions from SSAS 2005 Cubes Return Incorrect Values 35
Properties with Multiple Data Types Result in Missing Valid Data When Filtering 36
Red X Characters Appear in Data Tree When Using a PowerCube 36
Relationships Not Maintained in a Report With Overlapping Set Levels 37
Unexpected Results May Occur When Using Items from the Same Hierarchy on Multiple
Crosstab Edges 37
Metric Designer Issues 37
Adding Multiple IQD files to an Import Source 38
Previewed Scorecard Hierarchy Shows Blanks 38
Scorecard Exclusion Settings Lost 38
Metric Studio Issues 38
Metric Studio Reports Fail Because of an Oracle Internal Error 38
Metric Studio Errors Occur When Loading Data into an Oracle Database 39
Oracle Errors Occur When Using the cmm_uninstall Script 39
Length of Filter Expression is Limited for Cube Queries 39
Error When Attempting to Run Metric Studio on SQL Server 2005 40
Erroneous Re-assignment of Actions 40
Query Studio Issues 40
Report Studio Issues 40
OP-ERR-0231 Invalid Parameter Error 40
Aggregate of Minimum Returns Meaningless Results 41
Limited Calculated Member or Measure Expressions in Express Authoring Mode 42
Master-detail or Burst Reports with Charts May Generate Large Temporary Data Files
and Fail 42
Unexpected Summary Values in Nested Sets 43
Applying Filters to Dimensional Reports 43
Limitations When Using FOR Clause in Summary Functions 44
Running Totals Are Incorrect in Crosstab Reports 44
Ragged or Unbalanced Hierarchies Result In Unexpected Behavior 45
Different Results for List Reports and Crosstabs that Use the Same Set Expression 45
Key Transformation Validation Level Returns Partial Information 46
Slow SSAS 2005 Query Performance When Using the Key Attribute Hierarchy 46
Redrawing or Refreshing Issues with Prompt Controls 47
Error When Opening Hyperlink Button URLs in PDF Reports 47
Precision of Percentage Values Are Changed After Upgrading a Report 47
Bookmark Links in a Chart Legend Do Not Work in PDF Viewer 47
A Chart is Compressed in PDF When Margin Property is Changed 47
Chart Background Color Does Not Apply to Notes Area 47
SAP BW Data Sources Issues 48
Count Summaries in Query Calculations Include Nulls with SAP BW Data Sources 48
Incorrect Units of Measure in Calculations 48
Grouping Columns That Have the Count Summary 48
Missing Measures in Crosstab Reports 49
Crosstab with the Same Dimension on Both Edges Returns No Data 49
Custom Formatting for Empty Cells Does Not Appear in Cognos 8 49
Creating Sections on Reports That Access SAP BW Data Sources 49
Readme 5

Table of Contents
Summary Rows Return Incorrect Total Values 50
Calculated Key Figures Appear with the Non-aggregate Icon 50
Filter Expressions Using Report Items and Smart Prompts Do Not Return Values 50
Security Issues 50
Existing Passwords May not Work in an SAP Namespace 50
Users Are Repeatedly Prompted for Credentials When Trying to Log On to an SAP
Namespace 51
DPR-ERR-2079 Error When Using a Search Type of Migration in the New Job Wizard 52
Series 7 Integration Issues 52
Unsupported Cognos Planning 7.3 Features with Cognos 8 52
Third-Party Issues 53
Adobe Reader Displays Corrupted Characters in the Bookmarks Pane 53
Firefox Add-on Adblock Plus Prevents Cognos Connection Menus From Working 53
Importing a Large Content Store in Solaris using JRE 1.5 Fails 53
Cognos 8 Running under WebLogic Application Server on AIX Fails 53
Unable to View HTML Output in Internet Explorer When Running under WebLogic 9.1.0
53
Importing a Large Deployment in Windows Crashes the Java Virtual Machine 54
Transformer Issues 54
Content May Be Removed When Transformer 8.3 PowerCube Packages Are Republished 54
Support for Microsoft Excel 2007 55
Limitations on Using Reports in Transformer 56
Missing Values May Vary Results in PowerCubes 56
Queries Against Multiple Hierarchies in the Same PowerCube Dimension Do Not
Execute 56
Aggregate Values for Imported Query Items May Not Match the Source Package or
Report 57
Prompts Values in Multiple Queries 57
Prompts for Member Unique Names in SAP-BW Packages 57
Updated pcoptimizer Utility Included in Cognos 8.3 57
Transformer 8.3 Installation Download 58
Regular Columns cannot be Converted to Calculated Columns and Vice Versa 58
Framework Manager and Transformer may Display Different Locale Session Parameters
for Some Languages 58
An Error May Occur in Reports Created in a Different Language than that Used in the
Package Design Locale 59
Connection Error Occurs with Password-protected PowerCubes 59
Data Records that Support External Rollup Measure Data are Not Always Created 60
Building a PowerCube on an AIX Machine May Result in a Core Dump During Cube
Build 60
Unable to Open Sample Model, Great Outdoors Sales.mdl, and Generate Cubes 60
Chapter 2: Cognos 8 Documentation Updates 61
Cognos 8 Administration and Security Guide 61
Set Up the Essbase Cube Sample 61
Defining Global Filters 62
Data Sources and Connections 62
Samples 63
Secured Functions and Features 63
6

Table of Contents
Drill-Through Access 63
Cognos Portlets 63
Deploying Cognos Portlets to Microsoft SharePoint Portal Server 2003 and 2007 63
Reset Metrics for the System 64
Apply the Same Threshold Setting to Multiple Entries Using a Template 64
Enable Users to Open Series 7 PowerPlay Reports in Analysis Studio or Report Studio 64
New Tools in Global Customer Support 65
Cognos 8 Analysis Studio User Guide 65
Specify the Purpose of Your Output 65
Cognos 8 Analysis Studio Quick Tour 66
Cognos 8 Event Studio User Guide 66
Tutorial - Creating an Agent 66
Cognos 8 Installation and Configuration Guide 68
JDBC Driver Conflict for Oracle 68
Manually Changing the Installation Directory Name Affects Installations Running Under
an Application Server 68
Configuring file location for Cognos 8 Framework Manager or Cognos 8 Transformer 69
Cognos 8 Metric Studio User Guide 69
Changes to the Metric Model 69
Presentation View 71
Model View 72
Source View 72
Metric Functions 72
Compatibility Folder 73
The Linked Reports Query Subject 73
Guidelines for Reporting 74
Metric Studio Support Bundle 75
Add Email Notification for a Metric 76
History Charts 76
Specify Import Settings 76
Cognos 8 Transformer User Guide 77
Transformer Support for Prompts in Report Data Sources 77
Data Source Types: Cognos Package or Report 78
Command Line Syntax 78
Command Line Options 79
-c option 81
-n option 82
Cognos 8 Transformer Man Page 82
-h option 82
-i option 82
Cognos 8 Report Studio Professional Authoring User Guide 83
Nested List Report Containing a Data Item That is Grouped More Than Once Does Not
Run After Upgrade 83
Grouping by an Attribute is Not Supported 84
Limitations When Aggregating Measures in Dimensionally Modeled Relational (DMR) or
Relational Data Sources 84
Creating Expressions Using SAP BW Data Sources 85
Cognos 8 Framework Manager User Guide 85
When to Use Determinants 85
Readme 7

Table of Contents
Remap an Object to a New Source 86
Merge Projects 86
Publish a Package 87
Chapter 3: Deprecation Notices 89
Supported Environments 89
Framework Manager Security Filters for SAP BW: Notice of Intent to Change the Default
Setting 89
IQD Externalize Method 90
Transformer OLE Automation 90
Transformer Client/Server Synchronization 91
Transformer Data Source Support 91
Transformer .pyi Files 91
Transformer Menu Customization 91
Compressed PowerCubes 91
Cognos 8 Transformer Expression Editor Functions 92
Third Party OLAP Support 92
Secured PowerCubes 92
Cognos Viewer URL API (b_action=xts.run) 92
Index 95
8

Introduction
This Readme contains late-breaking information, including installation issues, limitations, and
known issues.
Visit the Cognos Global Customer Services Web site for
●
●
updates to this Readme and product documentation
the fix list, which is a list of the known issues that were addressed in this release
Updates to the software are made available on the Cognos Global Customer Services Web site (http:
//support.cognos.com). These updates contain the latest set of quality improvements that were
completed after the release of this software. We recommend that you review these updates and
apply them once you have completed the installation.
Readme 9

Introduction
10

Readme Updates By Date
This section contains links to Readme items that were updated after October 26, 2007.
Updated: February 6, 2008
The following Readme updates were made on February 6, 2008.
Known Issues - SAP BW Data Sources
● "Count Summaries in Query Calculations Include Nulls with SAP BW Data Sources" (p. 48)
Known Issues - Report Studio
●
"Ragged or Unbalanced Hierarchies Result In Unexpected Behavior" (p. 45) (topic updated)
Updated: January 18, 2008
The following Readme update was made on January 18, 2008.
Known Issues - Transformer
●
"Content May Be Removed When Transformer 8.3 PowerCube Packages Are
Republished" (p. 54)
Updated: January 10, 2008
The following Readme updates were made on January 10, 2008.
Known Issues - Issues Affecting Multiple Components
●
"Unexpected Results May Occur When Using Items from the Same Hierarchy on Multiple
Crosstab Edges" (p. 37)
Documentation Updates - Cognos 8 Administration and Security Guide
● "Enable Users to Open Series 7 PowerPlay Reports in Analysis Studio or Report Studio" (p. 64)
Readme 11

Readme Updates By Date
Updated: January 3, 2008
The following Readme update was made on January 3, 2008.
Documentation Updates - Cognos 8 Administration and Security Guide
● "Deploying Cognos Portlets to Microsoft SharePoint Portal Server 2003 and 2007" (p. 63)
Updated: December 21, 2007
The following Readme update was made on December 21, 2007.
Known Issues - Event Studio Issues
● "SQL Server Sample AssignStaff needs Modification" (p. 26)
Updated: December 13, 2007
The following Readme updates were made on December 13, 2007.
Known Issues - Report Studio Issues
● "OP-ERR-0231 Invalid Parameter Error" (p. 40)
Documentation Updates - Cognos 8 Administration and Security Guide
● "New Tools in Global Customer Support" (p. 65)
Updated: November 22, 2007
The following Readme updates were made on November 22, 2007.
Known Issues - Analysis Studio Issues
● "Cube Refresh in Data Analysis Studio Uses UTC/GMT Time " (p. 19)
Known Issues - Report Studio Issues
● "Bookmark Links in a Chart Legend Do Not Work in PDF Viewer " (p. 47)
● "A Chart is Compressed in PDF When Margin Property is Changed" (p. 47)
● "Chart Background Color Does Not Apply to Notes Area " (p. 47)
12

Readme Updates By Date
Updated: November 12, 2007
The following Readme updates were made on November 12, 2007.
Known Issues - Administration Issues
●
"A Validation Error Occurs in Cognos Connection When One of the Tabs in the Multi-page
Portlet Contains a Shortcut" (p. 17)
● "Unable to View Past Activities in Cognos Administration with Cognos 8 Special Edition" (p. 18)
Known Issues - Framework Manager Issues
● "Review Governors When Upgrading Models" (p. 24)
Known Issues - Installation and Configuration Issues
● "Installation of WebSphere and IHS fails in Cognos 8 Special Edition" (p. 28)
● ""db2 not found" error when installing Cognos 8 Special Edition" (p. 29)
● "Cognos 8 does not Start on WebSphere 5.1" (p. 29)
●
●
"Gateway only Install of Cognos 8 Special Edition cannot access Cognos Connection
Portal" (p. 30)
"Application Tier only Install of Cognos 8 Special Edition does not Configure the Notification
Database" (p. 30)
● "DB2 Server is not Registered after Install of Cognos 8 Special Edition" (p. 30)
● "IBM WebSphere is not installed with Cognos 8 Special Edition" (p. 31)
● "Non-ASCII Characters in Installation Directory Cause Run-time Errors" (p. 31)
● "Copy Cognos 8 Go! Office Client Files to a Central LAN Location" (p. 31)
Known Issues - Issues Affecting Multiple Components
● "Columns, Rows, or Data May Disappear Unexpectedly When Using SSAS 2005" (p. 32)
● "Report Layout Functions from SSAS 2005 Cubes Return Incorrect Values" (p. 35)
● "Properties with Multiple Data Types Result in Missing Valid Data When Filtering" (p. 36)
● "Red X Characters Appear in Data Tree When Using a PowerCube" (p. 36)
● "Relationships Not Maintained in a Report With Overlapping Set Levels" (p. 37)
Readme 13

Readme Updates By Date
Known Issues - Metric Studio Issues
● "Error When Attempting to Run Metric Studio on SQL Server 2005" (p. 40)
● "Erroneous Re-assignment of Actions" (p. 40)
Known Issues - Report Studio Issues
● "Aggregate of Minimum Returns Meaningless Results" (p. 41)
● "Slow SSAS 2005 Query Performance When Using the Key Attribute Hierarchy" (p. 46)
● "Redrawing or Refreshing Issues with Prompt Controls" (p. 47)
● "Error When Opening Hyperlink Button URLs in PDF Reports" (p. 47)
● "Precision of Percentage Values Are Changed After Upgrading a Report" (p. 47)
Known Issues - Transformer Issues
● "Regular Columns cannot be Converted to Calculated Columns and Vice Versa" (p. 58)
●
●
"Framework Manager and Transformer may Display Different Locale Session Parameters for
Some Languages " (p. 58)
"An Error May Occur in Reports Created in a Different Language than that Used in the Package
Design Locale" (p. 59)
● "Connection Error Occurs with Password-protected PowerCubes" (p. 59)
● "Data Records that Support External Rollup Measure Data are Not Always Created " (p. 60)
●
"Building a PowerCube on an AIX Machine May Result in a Core Dump During Cube
Build" (p. 60)
● "Unable to Open Sample Model, Great Outdoors Sales.mdl, and Generate Cubes" (p. 60)
Documentation Updates - Cognos 8 Administration and Security Guide
● "Reset Metrics for the System" (p. 64)
● "Apply the Same Threshold Setting to Multiple Entries Using a Template" (p. 64)
Documentation Updates - Cognos 8 Installation and Configuration Guide
● "Configuring file location for Cognos 8 Framework Manager or Cognos 8 Transformer" (p. 69)
Documentation Updates - Cognos 8 Metric Studio User Guide
● "Changes to the Metric Model" (p. 69)
14

Readme Updates By Date
● "Presentation View" (p. 71)
● "Model View" (p. 72)
● "Source View" (p. 72)
● "Metric Functions" (p. 72)
● "Compatibility Folder" (p. 73)
● "The Linked Reports Query Subject" (p. 73)
● "Guidelines for Reporting" (p. 74)
Documentation Updates - Cognos 8 Report Studio Professional Authoring User
Guide
● "Creating Expressions Using SAP BW Data Sources" (p. 85)
Deprecation Notices - Supported Environments
● "Supported Environments" (p. 89)
Readme 15

Readme Updates By Date
16

Chapter 1: Cognos 8 Known Issues
This section contains information about Cognos 8 BI known issues.
Administration Issues
This section contains known issues about administration.
Different User Interface When Cognos 8 Is Running on IBM WebSphere
Application Server Version 5.1
If Cognos 8 is running on WebSphere 5.1, the user interface for System on the Status tab in Cognos
Administration is not the same as documented in the Administration and Security Guide. There is
also no capability to select interactive activity for Current Activities on the Status tab. Instead, you
see a different user interface that lets you monitor and control your dispatchers and servers.
This is because the technology used to deliver the user interface in Cognos 8.3 is not fully supported
by WebSphere 5.1.
566356
Drilling Through from a PowerCube to DMR Data Using the Time Dimension
Members
This drill-through action does not support passing date values from a PowerCube time dimension
to a dimensionally modeled relational (DMR) time dimension.
A Validation Error Occurs in Cognos Connection When One of the Tabs in the
Multi-page Portlet Contains a Shortcut
When you click a tab in the Multi-page portlet in a dashboard and the tab contains a shortcut, a
validation error may appear in Cognos Connection. The problem occurs when the shortcut represents
a PowerPlay report or cube, a folder, a package, a URL, or a Microsoft document. Shortcuts to
other types of entries do not cause any problems.
As a workaround for this problem, do one of the following:
●
Disable the validation of portlet input parameters.
In the pf.properties file located in the c8_location\webapps\2pd\WEB-INF\classes directory,
change
enable.validation=true
to
Readme 17

Chapter 1: Cognos 8 Known Issues
enable.validation=false
Note: Typically, disabling the validation of portlet input parameters is not recommended. Before
you do this, ensure that this is the right solution for your environment.
●
Modify the validation.properties file in the c8_location\webapps\p2pd\WEB-INF\fragments\
validation directory.
Change
validator.page.targets=/cm,/pagelet
to
validator.page.targets=/pagelet.
579228
Unable to View Past Activities in Cognos Administration with Cognos 8 Special
Edition
If you click Past Activities in the Cognos Administration portal, the following error message is
displayed:
SOAPFaultException NAV-ERR-1001 Content Manager returned an error. A more
detailed error message will be logged.
The cogserver.log file contains the following error message:
SQL1585N A system temporary table space with sufficient page size does not
exist. SQLSTATE=54048
You can solve this problem by typing the following lines into the DB2 Command Line Processor,
replacing with the Cognos 8 installation directory:
CONNECT TO CM
CREATE BUFFERPOOL "CM_32KBP" IMMEDIATE SIZE 250 PAGESIZE 32K NOT EXTENDED STORAGE
DROP TABLESPACE TSN_SYS_CM
CREATE SYSTEM TEMPORARY TABLESPACE TSN_SYS_CM IN DATABASE PARTITION GROUP
IBMTEMPGROUP PAGESIZE 32K MANAGED BY SYSTEM USING ('/
IBM/DB2-91/CNT_SYS_CM') EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL CM_32KBP
ALTER TABLESPACE TSN_SYS_CM OVERHEAD 10.5 TRANSFERRATE 0.14
COMMIT
CONNECT RESET
Alternatively, if you have not yet installed Cognos 8 Special Edition you can preempt this problem
by editing the file C8SE/C8SE_template_DB2-91.db2 in the Cognos 8 source location. After the
line
C8SE_DB2_Command CREATE BUFFERPOOL "C8SE_C8_DB_Name_16KBP" IMMEDIATE SIZE 250
PAGESIZE 16K NOT EXTENDED STORAGE
add the line
18

Chapter 1: Cognos 8 Known Issues
C8SE_DB2_Command CREATE BUFFERPOOL "C8SE_C8_DB_Name_32KBP" IMMEDIATE SIZE 250
PAGESIZE 32K NOT EXTENDED STORAGE
Change the line
C8SE_DB2_Command CREATE SYSTEM TEMPORARY TABLESPACE TSN_SYS_C8SE_C8_DB_Name IN
DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 16K MANAGED BY SYSTEM USING
('C8SE_DB2_Dst/CNT_SYS_C8SE_C8_DB_Name') EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL
C8SE_C8_DB_Name_16KBP
to
C8SE_DB2_Command CREATE SYSTEM TEMPORARY TABLESPACE TSN_SYS_C8SE_C8_DB_Name IN
DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 32K MANAGED BY SYSTEM USING
('C8SE_DB2_Dst/CNT_SYS_C8SE_C8_DB_Name') EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL
C8SE_C8_DB_Name_32KBP
580675
Analysis Studio Issues
This section contains known issues about Analysis Studio.
Defining Languages for OLAP Data Sources
The first time you publish a cube definition to 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.
499296
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.
494291
Cube Refresh in Data Analysis Studio Uses UTC/GMT Time
There is a difference between Report Studio and Analysis Studio when displaying the cube refresh
timestamp. In Analysis Studio, the cube refresh timestamp is based on the UTC/GMT format, so
there may be several hours of difference between the timestamp and the actual time that the cube
was updated.
In Report Studio, you use report expressions to reference the cube refresh data. Users who access
the report output from Report Studio in Cognos Viewer are presented with the timestamp in local
time and based on user preferences.
Readme 19

Chapter 1: Cognos 8 Known Issues
You can view the timestamp in local time and based on user preferences by opening the analysis in
Report Studio and adding a layout calculation with the following expressions CubeDataUpdatedOn
(dimension) or CubeSchemaUpdatedOn(dimension) using any cube dimension for either expression.
575812
DB2 Data Sources Issues
The following issues were identified with software components of DB2 data sources. We are
managing the status of these problems with the vendor, but, at the time of this release, the following
issues are still unresolved in the product.
Query Fails When Using DB2 OLAP Server
When you run a query to retrieve metadata or data in a DB2 OLAP server, you may see an exception
window indicating that there is a problem with the query.
The error probably occurred because Windows did not have enough remote procedure call (RPC)
ports available. This lack of sufficient RPC ports can cause data retrieval from DB2 OLAP and
Essbase data sources to fail because of network communication errors.
To resolve this problem, you must increase the number of RPC ports that are available for program
use. Hyperion and Microsoft propose that you add two registry entries, MaxUserPort TCP/IP and
TcpTimedWaitDelay in Microsoft Registry Editor.
For more information about these parameters, see http://www.microsoft.com/resources/
documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/
Windows/2000/server/reskit/en-us/regentry/58811.asp.
Important: Use Registry Editor at your own risk. Incorrect use may cause problems that require
you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems
that result from using Registry Editor incorrectly.
We also recommend that you edit the Cognos 8 qfs_config.xml configuration file.
Steps to Add Entries in Microsoft Registry Editor
1. From the Start menu, click Run.
2. Type regedit and then click OK.
3. In the Registry Editor window, click the following directory:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
4. From the Edit menu, click New, DWORD Value.
The new value appears in the list of parameters.
5. Type MaxUserPort and then press Enter.
Double-click MaxUserPort.
6. In the Edit DWORD Value window, do the following:
20

Chapter 1: Cognos 8 Known Issues
●
Click Decimal.
● Type a value between 30000 and 65534.
Tip: We recommend the maximum value, 65534.
●
Click OK.
7. From the Edit menu, click New, DWORD Value.
The new value appears in the list of parameters.
8. Type TcpTimedWaitDelay and then press Enter.
9. Double-click TcpTimedWaitDelay.
10. In the Edit DWORD Value window, do the following:
●
●
Click Decimal.
Type a value between 30 and 300 seconds.
The default is 240 seconds (4 minutes).
●
Click OK.
11. Close the Registry Editor window.
12. Restart the Microsoft CRM server or reboot your computer for these settings to take effect.
Steps to Edit the Cognos qfs_config.xml Configuration File
1. Open the qfs_config.xml configuration file from the configuration directory.
2. Add the following parameters under the appropriate provider section, such as .
●
●
The RecoveryWait value is in milliseconds.
Note: DB2OlapODP and Essbase are synonymous and are used interchangeably in Cognos 8.
476181
Unable to Open a Cube Using 8.2 DB2 OLAP or Essbase 7.1
If you are using 8.2 DB2 OLAP or Essbase 7.1, you cannot open a cube which has been designed
to use Aggregate Storage.
When the Aggregate Storage Option (ASO) cube package is loaded into one of the Cognos 8 Studios,
the metadata is not shown.
Readme 21

Chapter 1: Cognos 8 Known Issues
To ensure that you have the run-time library required to access the ASO feature, perform the
following additional steps when installing your DB2 OLAP 8.2 client software.
Steps to Access the Run-time Library
1. In the DB2 OLAP 8.2 client installation wizard, select the Custom installation type, and then
click Next.
2. Select the Essbase API for Windows 32 option if it has not already been selected, and then
proceed through the remaining pages of the installation wizard.
3. When the installation is finished, locate libdb42.dll in the folder db2olap_installation_location\
api\redist, and copy this file to the client installation folder db2olap_installation_location\bin.
4. Restart your system.
Note: If you apply a Fix Pak to your DB2 OLAP 8.2 client, remember to also recopy libdb42.
dll (as explained above), to ensure that your \bin folder always contains the most up-to-date
version of this required file.
483570
Framework Manager Issues
This section contains known issues about Framework Manager.
Defining Repository Connections
Parsing errors occur when attempting to define a repository connection via Connection Manager
version 1.11.22 in Framework Manager.
Use UNC paths when defining repository connections through Connection Manager. Do not specify
a mapped drive letter.
nbna
Syntax of Macro Prompts
When default values are specified in the syntax of macro prompts, you may see the following error:
Error: QE-DEF-0261 QFWP - Parsing text: [mssql_gosales].[COUNTRY].[COUNTRY]
= Canada
Use prompt syntax such as where Country = ?Enter Country?
566354
Oracle 10G Uses Zeroes Instead of Nulls for Non-Matching Values
On a left outer join, Oracle 10G fills in non-matching values with zeroes instead of NULLS.
For example, you have two tables:
Table 1 (T1)
22

Chapter 1: Cognos 8 Known Issues
a x
1 r
2 v
3 NULL
Table 2 (T2)
b x
7 r
8 v
9 NULL
With a left outer join between these tables (T1 LEFT OUTER JOIN T2 (T1.x = T2.x)), the result
is:
a T1.x | b T2.x
1 r | 7 r
2 v | NULL NULL
3 NULL | NULL NULL
The left side table (T1) is preserved and NULLs are used to fill in non-matching values in T2. For
Oracle 10G, zeroes appear instead of NULLs.
530475
Full Outer Joins Not Sent to Oracle 9i and 10GR1
By default, Cognos 8 will not send full outer joins to ORACLE 9i and 10GR1 due to Oracle bug
#2874433. This requires using limited local processing in Cognos 8.
To enable full outer joins with Oracle, you must
●
●
ensure that you have the required patch sets, which include the fix for Bug#2874433
modify the cogdmor.ini file to turn on full outer joins (Full_outer_join=T)
Because any manual edits to the ini settings are overwritten by the next installation, you must
manually replicate them on all machines where you installed Cognos 8 or Framework Manager.
nbna
Unable to Load DB2 OLAP Library in Framework Manager
You installed the DB2 OLAP 8.1 or 8.2 client and cannot load the DB2 OLAP library into
Framework Manager.
You receive the following message:
DB2-ERR-0028 Unable to load the following Essbase/DB2
OLAP library: "essapinu.dll"."
To resolve the problem, you must edit the qfs_config.xml file and rename the library for Version
8.1 or 8.2.
Readme 23

Chapter 1: Cognos 8 Known Issues
All current DB2 OLAP client versions are supported for Cognos 8.3: "doodp81", "doodp82".
The default configuration in qfs_config is Hyperian Essbase version 9.3.1 "essodp93".
Steps
1. In the c8_location\configuration directory, edit the qfs_config.xml file.
2. Find the following code:
3. Change the library name from essodp93 to doodp81 or doodp82 and save the changes.
574849
Filter on SAP Attribute Is Ignored for Model Query Subjects If There Is No
Business Key
If the model query subject contains only attributes and if your user filters on an attribute, the filter
is ignored.
Add the business Key (identifier) to the model query subject and filter on the business key instead.
This is the recommended way to filter because captions and other attributes are not unique. Filtering
on non-unique attributes can create performance problems.
578916
Review Governors When Upgrading Models
If you have a segmented or linked model that was created with a previous version of Framework
Manager, you must review the governor settings for each child and parent model before and after
upgrade. The governor settings for the top-level parent model are the settings that are applied when
publishing.
The Shortcut Processing governor is new in Cognos 8.3. By default, this governor evaluates the
shortcut objects in the model and creates an explicit value for the Treat As property of each shortcut
that represents the current behavior. No change in behavior is expected if the governor is set to
Automatic.
Part of the upgrade process is that the Shortcut Processing governor is set to Automatic, which
preserves behavior from previous versions of Framework Manager. If you run a script that was
created in a previous version of Framework Manager, the script bypasses the upgrade process.
Review the governor settings before and after running the script to ensure that the settings are what
you want.
579031, 580784
Model Advisor Test Can Produce False Positive Results
If you run the Determinants that conflict with relationships test in the Model Advisor, you may
receive a false positive result.
24

Chapter 1: Cognos 8 Known Issues
In certain circumstances, the Model Advisor indicates that a relationship key conflicts with a
determinant if the key is a participant in a multiple-part key even when the relationship key does
match the key of another determinant in the query subject. In other circumstances, the Model
Advisor correctly notes the mismatch as a potential issue that requires investigation by the modeler.
Review the determinants of the query subject to confirm that the keys of one determinant match
the keys of a relationship.
578864
Order of Transactions in Transaction History
The order of transaction could appear out of sequence when you view the transaction history for
a project that has not been saved. Scripts that have been created against an unsaved project may
fail to run successfully.
Save the project and the order of transactions is restored.
579383
BmtScriptPlayer Does Not Run Action Logs on UNIX Platforms
When running the BmtScriptPlayer executable, you may encounter errors on UNIX, such as the
following error messages:
BME-SP-0007 An unknown error occurred during execution.
BME-SP-0028 All applied changes will be saved.
To resolve this problem, do the following:
1. Disable the multiuser feature by adding the following section in the configuration/bmt.ini file:
Off
2. Delete the project directories created without this entry in bmt.ini. They might contain wrong
579180
log files.
Changes to Transaction Log Files and the Transaction History List
In previous releases of Framework Manager, transactions were captured in a log file. One log file
was generated per session. Each log file name included timestamp information. When viewing the
transaction history list for a project, it was possible to search the transaction list by the time-stamped
log file names to locate a set of transactions.
In the current release of Framework Manager, each transaction is captured with timestamp
information and saved to a single file named log.xml. From the transaction history list, you are
required to click a individual transaction to display the timestamp information.
579572
Readme 25

Chapter 1: Cognos 8 Known Issues
Unable to Create Star Schemas, Merge Query Subjects, or Create Shortcuts
Based on a Read-only Project
You are unable to create star schemas, merge query subjects, or create shortcuts based on a read-only
project. Read-only projects are often used as linked segments in projects where change protection
of the metadata needs to be rigidly enforced.
This limitation affects only those who implemented the Distribution by Layers methodology for
sharing metadata as documented in the Framework Manager User Guide.
522986
Event Studio Issues
This section contains known issues about Event Studio.
SQL Server Sample AssignStaff needs Modification
The AssignStaff stored procedure in the SQL Server GOSALES database, relating to Event Studio
samples, needs to be modified in order to have the Event Studio sample agents work as planned.
Steps to Correct the AssignStaff Stored Procedure
1. Locate the file \webcontent\samples\datasources\sqlserver\
Event_Studio_ELM_Stored_Procedure.txt and change the line
@ORDER_DETAIL_CODE_IN varchar(6),
to
@ORDER_DETAIL_CODE_IN varchar(8),
2. In SQL Server, delete the gosales.AssignStaff stored procedure from the GOSALES database.
3. In SQL Server, run the modified Event_Studio_ELM_Stored_Procedure.txt script against the
GOSALES database.
4. Launch Framework Manager and open the model \webcontent\samples\
Models\great_outdoors_sales\great_outdoors_sales.cpf.
5. In the Project Viewer, expand go_sales, followed by Filters and calculations, and then
double-click AssignStaff.
6. In the Query Subject Definition window, click the ... box in the @ORDER_DETAIL_CODE_IN
row and change the value in the Precision field of the Edit Argument window from 6 to 8.
7. Select the Test tab in the Query Subject Definition window, and click Test Sample.
8. In the Value column of the Prompt Values window, type the values 1000013 for
ORDER_DETAIL_CODE_IN and 406 for SALES_STAFF_CODE_IN, and click OK.
9. Click OK in the Query Subject Definition window.
26

Chapter 1: Cognos 8 Known Issues
10. Publish the GO Sales (analysis) and GO Sales (query) packages.
Go! Office Issues
This section contains known issues about Cognos 8 Go! Office.
bo:heap Buffer Overflow Error
After long sessions, Microsoft Office may stop responding by generating a bo:heap Buffer Overflow
error.
This error may be falsely identified as a potential virus by some virus-monitoring programs.
557292
Prompted to Log on For Each Imported Report
When refreshing all data in a document before logging on to the required servers, you are
automatically prompted to log on for each report in the document even if the reports originate from
the same server.
To log on only once to each server, use the Log On toolbar button to log on to the required servers
before refreshing report data.
573884
The Namespace Parameter is Case Sensitive
When logging on to a server using automation, you must match the namespace exactly. The
namespace parameter is case sensitive.
573749
Cognos 8 Go! Office Automation Does Not Support SiteMinder Form-Based
Authentication
Cognos 8 Go! Office does not support Siteminder form-based authentication when using automation.
If SiteMinder is used as authentication, the SiteMinder logon page appears before Microsoft Excel
loads Cognos 8 Go! Office, and this logon page cannot be bypassed by Cognos 8 Go! Office
automation.
You must use the Cognos Go! Office menu commands and options instead of the application
programming interface (API) to automate the refreshing or publishing of workbook, document,
and presentation content.
574640
Readme 27

Chapter 1: Cognos 8 Known Issues
Installation and Configuration Issues
This section contains known issues about installation and configuration.
Cognos 8 Server May Fail to Start
A Cognos 8 server may fail to start after an upgrade or new installation, but no error message
appears. This may occur when a previously running or new Cognos 8 server is configured to use a
large amount of memory.
If the server on which Cognos 8 is installed contains version 1.0 of Microsoft security update
921883, there may be an issue when a lot of contiguous memory is requested by an application.
This is a known issue with version 1.0 of Microsoft security patch 921883. Microsoft distributed
a second version of the patch to fix the problem. As a workaround, uninstall the first security patch,
or install version 2.0 of the patch. Alternatively, you can configure the Cognos 8 server to use less
memory.
For more information, see the Microsoft knowledge base article about programs using a lot of
contiguous memory failing, at http://support.microsoft.com.
nbna
Issues with IBM WebSphere 6.0 on AIX 5.3
Cognos testing has found difficulties with IBM WebSphere 6.0 on AIX 5.3. Cognos recommends
upgrading to AIX 5.3 Technology Level 4, Service Pack 2.
nbna
Installation of WebSphere and IHS fails in Cognos 8 Special Edition
After installing Cognos 8 Special Edition, WebSphere and IHS are not installed and the installation
log has the following error message.
"Process, com.ibm.ws.install.ni.ismp.actions.MaintenancePrereqCheckAction, err, CWUPI0037E:
A supported operating system architecture was not detected. Support for your operating system
architecture might have been added after the release of the product. You can continue with the
installation, but the installation might not succeed. See the WebSphere Application Server supported
hardware and software Web pages at http://www.ibm.com/software/webservers/appserv/doc/latest/
prereq.html for more information about supported operating systems."
Check that you are at or above the maintenance level required for WebSphere (http://www-1.ibm.
com/support/docview.wss?rs=180&uid=swg27007624).
If you are at or above the required maintenance level, the OS check is incorrectly reporting an error,
and you can install WebSphere and IHS by following these steps.
1. Bypass the operating system checks by editing the install source files C8SE/C8SE_install_WAS-61.
sh and C8SE/C8SE_install_IHS-61.sh and uncommenting the following line in each file by
removing the #.
28

Chapter 1: Cognos 8 Known Issues
#echo -OPT disableOSPrereqChecking="true">>${RESPONSE_FILE}
2. Uninstall the installed Cognos 8 Special Edition products by running the appropriate uninstall
programs.
3. Reinstall Cognos 8 Special Edition.
580216
"db2 not found" error when installing Cognos 8 Special Edition
When installing Cognos 8 Special Edition, the following error is displayed in the console and
reproduced in the install logs:
/home/db2user/C8SE_config_DB2-91_DB_setup.sh: db2: not found
The DB2 database instance is not correctly configured and Cognos 8 does not start.
You can solve this problem by following these steps.
1. When creating the db2user account, create a profile that sources sqllib/db2profile from the
user’s home directory. This file does not exist before you install Cognos 8 Special Edition but
is used during the DB2 configuration phase.
An example of such a profile is:
if [ -f /home/db2user/sqllib/db2profile ]; then
./home/db2user/sqllib/db2profile
fi
2. Uninstall the installed Cognos 8 Special Edition products by running the appropriate uninstall
programs.
3. Reinstall Cognos 8 Special Edition.
566356
Cognos 8 does not Start on WebSphere 5.1
The Cognos 8 service does not start and the following error message is written to the cogserver.log.
sealing violation: package javax.management is sealed
You can solve this problem by recreating the Cognos 8 application file and redeploying to the
WebSphere application server.
1. In the file /webapps/p2pd/WEB-INF/p2pd_deploy_defaults.properties, uncomment
the line
#noJMX=true
2. Move the mx4j*.jar files from the /webapps/p2pd/WEB-INF/lib directory to a
location outside the /webapps directory.
3. Start Cognos Configuration and use the Build Application Wizard to recreate the Cognos 8
application file.
4. Using the WebSphere Administration console, undeploy the Cognos 8 application, save the
new configuration, and then deploy the new Cognos 8 application file.
Readme 29

Chapter 1: Cognos 8 Known Issues
566356
Gateway only Install of Cognos 8 Special Edition cannot access Cognos
Connection Portal
The Cognos 8 Special Edition installation ends prematurely and the following error message is
written to the C8SE_install.log file.
{date} {Time} FATAL: C8: Unable to locate "\java\jre\lib\ext\bcprov-jdk14-134.
jar"
You can solve this problem by following these steps.
1. Start Cognos Configuration and, under Environment, enter the Dispatcher URI for gateway
information. Save the configuration and close Cognos Configuration.
2. Restart the IBM HTTP server.
580318
Application Tier only Install of Cognos 8 Special Edition does not Configure the
Notification Database
Cognos 8 cannot connect to the Content Manager and the following error message is written to
the cogserver.log.
CNC-SDS-0256 Unable to connect to the database using jdbc:JSQLConnect://
localhost:1433/cm
You can solve this problem by following these steps.
1. Start Cognos Configuration.
●
●
If a notification database exists as a sub-node of the Notification node, enter the database
information in the Properties window of the database.
If a notification database does not exist, in the Explorer window, right-click Notification
and select New resource, Database. Type the database name, select the database type, and
enter the database information in the Properties window of the database.
The notification database must point to the content store used by Content Manager. This
may require additional database-specific tasks.
2. Save the configuration and close Cognos Configuration.
3. Restart the WebSphere application server instance.
580312
DB2 Server is not Registered after Install of Cognos 8 Special Edition
The DB2 log file shows the following error.
ADM12026W The DB2 server has detected that a valid license for this
product has not been registered.
30

Chapter 1: Cognos 8 Known Issues
You can solve this problem by manually registering the IBM DB2 Workgroup Server Edition.
1. Copy the file db2wse_c.lic (available from Cognos Customer Support) to the following location:
●
●
for Windows, the \bin directory
for UNIX, source sqllib/db2cshrc and go to the /adm directory
2. Run the following command to import the license.
580811
db2licm -a db2wse_c.lic
IBM WebSphere is not installed with Cognos 8 Special Edition
After installing Cognos 8 Special Edition on Linux, IBM WebSphere is not installed.
You can solve this problem by following these steps.
1. Uninstall the installed Cognos 8 Special Edition products by running the appropriate uninstall
programs.
2. Edit the install source file C8SE/C8SE_install_WAS-61.sh by changing the line
./install -options ${RESPONSE_FILE} -is:javahome ${JAVA_HOME} -silent>>$
{C8SE_logfile}
to
./install -options ${RESPONSE_FILE} -is:javaconsole -silent>>${C8SE_logfile}
3. Reinstall Cognos 8 Special Edition.
580959
Non-ASCII Characters in Installation Directory Cause Run-time Errors
On all operating systems, if you use non-ASCII characters in the installation directory for Cognos 8,
it causes run-time errors. It also causes some product functions, such as report execution, to fail.
To resolve this issue, install Cognos 8 in the default directory or use a directory name that contains
only ASCII Latin-1 characters.
Copy Cognos 8 Go! Office Client Files to a Central LAN Location
Before users can deploy Cognos 8 Go! Office to their computer, you must copy the setup.exe and
other installation files to a central location on the LAN or Web site. By default, the setup.exe and
installation files are in the c8_location\webcontent\coc directory.
Step
●
From the c8_location\webcontent\coc directory, copy the following components to the LAN
location:
●
●
the KB908002 folder
the setup.exe file
Readme 31

Chapter 1: Cognos 8 Known Issues
●
the CognosOfficeSetup.msi file
Users can then run the setup.exe file from the LAN location to deploy Cognos 8 Go! Office. For
instructions, see “Deploying Cognos 8 Go! Office Client” in the Installation and Configuration
Guide.
Issues Affecting Multiple Components
This section contains general known issues. This includes issues that affect more than one Cognos 8
component, such as Query Studio and Report Studio. Issues that affect just one component are
described in the section for that component.
Columns, Rows, or Data May Disappear Unexpectedly When Using SSAS 2005
When using a Microsoft SQL Server 2005 Analysis Services (SSAS) cube, if the default member of
a hierarchy is a member that doesn't also exist in all other hierarchies in the dimension, and if you
query members from different hierarchies in the same dimension, you may encounter unexpected
results.
For example a Report Studio crosstab includes the following (using the Adventure Works cube):
●
Rows: Generate([Adventure_Works].[Account].[Accounts],set([Balance Sheet],[Units]))
nested with
children([Adventure_Works].[Department].[Departments]->:[YK].[[Department]].[Departments]
].&[1]]])
●
●
Column: [Adventure_Works].[Account].[Account Number].[Account Number]
Measure: [Adventure_Works].[Measures].[Amount]
You run the report and notice that the query renders with some blanks cells. You then apply the
simple detail filter [Amount]>1 and run the report. Only row labels are displayed and all data and
columns are missing.
In the Adventure Works cube, the [Account].[Accounts] attribute has a default member set to [Net
Income]. When evaluating the GENERATE set expression, SSAS looks in the entire cube space and
looks at all coordinates for the [Account] dimension. These coordinates include both [Account]
[Account Type].&[] and [Account].[Accounts].[Net Income]. Because these two coordinates don't
exist within the same hierarchy, SSAS returns an empty set.
To avoid this problem the SSAS administrator must set the default member in the cube to a member
that exists in all other hierarchies.
569506
32

Chapter 1: Cognos 8 Known Issues
Incorrect Values May Be Returned With Scoped Attribute Hierarchies in SSAS
2005
In Microsoft SQL Server 2005 Analysis Services (SSAS), you can now set the granularity for each
dimension in measure groups.
If a query refers to members below the granularity, attribute hierarchies are used, and no data exists
in the fact table, non-NULL values are returned when they shouldn’t. The data returned is the sum
of the scoped level against the hierarchy.
This applies to calculated measures or members that use a level or measure that is out of scope in
the calculation.
For example, a crosstab contains an August 2005 column from the Calendar Month attribute
hierarchy ([Time YQMD].[Calendar Month].&[2005]&[8]). You then select a measure from a
measure group whose granularity of the Time YQMD dimension is set to Calendar Year (which is
higher than Calendar Month). Assume that no data exists for that year. This crosstab will return
data when no data exists.
This problem is currently logged as SSAS 2005 problem number 491857 (Query contains a set
using a user hierarchy with members below the granularity attribute returns wrong results).
To avoid this problem and properly return NULL values, use a user-defined hierarchy instead of
the attribute hierarchy.
549157
Changes to Decimals in Currency Formats
When you open a PowerCube in a Cognos 8.3 Web studio or in 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
Readme 33

Chapter 1: Cognos 8 Known Issues
● $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
Metadata Change in Essbase Not Reflected in Studios
When there is a metadata change on the Essbase server, the change is not immediately reflected in
the metadata tree in the studios.
To view the new structure, you must restart both the Essbase server and the Cognos Content
Manager server.
545114
A Filter Definition Returns Character Set Mismatch Error Against Oracle Sample
Database
A filter definition may return a character set mismatch error when run against the Oracle version
of a sample database.
The following Oracle error appears:
ORA-12704: character set mismatch
To fix this error, the modeler must fix the filter definition in Framework Manager. In Framework
Manager, cast the item you want to filter as nvarchar, and then republish the package to Cognos
Connection.
Very Large Dimensions May Cause Denial of Service
When working with very large cubes, query results can be much larger than what can be held in
memory. For example, if you insert the lowest level of four hierarchies that each contain 1000
members, the report can contain 1000,000,000,000 cells. At best, this query will take a very long
time to run. While this large query executes, all other queries for the same BIBusTKServerMain
process will likely be blocked. For most data sources, the query will likely fail due to insufficient
memory or timing out. Then the memory is released and normal services resume.
However, when using a Microsoft SQL Server 2005 Analysis Services (SSAS) cube, the memory
consumed by the SSAS client is not always released in a way that other queries can effectively re-use.
The server continues to run with insufficient memory, causing new queries to either run very slowly
or fail completely. You may encounter an error and to continue, the system administrator must
manually stop and restart the Cognos 8 service.
To avoid these problems, consider the size of hierarchy levels and sets when creating reports and
avoid combining them in ways that create large queries. To determine the size of a set, create and
run a very small report that includes only that set.
34

Chapter 1: Cognos 8 Known Issues
544245
Limited Support for Relational Functions When Used With OLAP Data Sources
When working with an OLAP data source, if you use a relational function in a Query Studio or
Report Studio report that contains a measure with the rollup aggregation function set to Calculated
or Automatic, all summaries are calculated using the Minimum function instead of the aggregate
function derived from the individual query items. For example, you create a Query Studio report
that contains the data items Product line and Gross margin. The footer summary is set to Calculated.
You then insert a calculated column that returns the first three characters of the Product line item.
The footer summary now shows the lowest gross margin value.
For more information about aggregation functions, see the Query Studio User Guide or the Report
Studio User Guide.
There is no workaround.
541657
568989
562768
541664
Pivoting to a Crosstab Shows the Member of the Attribute
When working with a dimensional data source, if you have a list report created in either Query
Studio or Report Studio that contains an attribute, and you pivot the list into a crosstab, the member
captions appear instead of the attribute. For example, a list report contains the items Beverages,
Ounces, and Profit, where Ounces is an attribute of Beverages. You pivot on Beverages to create a
crosstab that has Ounces as rows, Beverages as columns, and Profit as the measure. When you run
the report, you see beverages in both the rows and columns.
This issue also occurs in crosstabs that contain a grouped calculation whose expression is an
attribute.
To resolve the issue, create a crosstab report from scratch using the attribute.
555435
Report Layout Functions from SSAS 2005 Cubes Return Incorrect Values
When using a Microsoft SQL Server 2005 Analysis Services (SSAS) cube, values displayed for the
CubeDataUpdatedOn and CubeSchemaUpdatedOn layout report functions are incorrect.
For example, in the SQL Server Management Studio you see the following timestamp values:
●
●
Last Schema Update 9/13/2006 10:49:31 AM
Last Processed 10/1/2007 9:53:29 AM
In your report, the CubeDataUpdatedOn and CubeSchemaUpdatedOn layout report functions may
show different values, as follows:
Readme 35

Chapter 1: Cognos 8 Known Issues
●
●
CubeSchemaUpdatedOn 9/13/2006 9:49:44 AM (This timestamp should be similar to the Last
Schema Update timestamp.)
CubeDataUpdatedOn 10/2/2007 8:53:29 AM (This timestamp should be similar to the Last
Processed timestamp.)
This problem is logged with Microsoft as problem #506693.
There is currently no workaround for this problem.
551810
Properties with Multiple Data Types Result in Missing Valid Data When Filtering
In a Microsoft SQL Server 2005 Analysis Services (SSAS) cube, attributes can have a NameColumn
and KeyColumn property specified.
An example is in the Product dimension from the SSAS 2005 sample cube named Adventure Works.
For the [Product].[End Date] attribute, the NameColumn property is associated with the
SimpleEndDate column (Char) of the DimProduct table. The KeyColumn property is associated
with the EndDate column (DateTime) of the DimProduct table. Where the SimpleEndDate column
equals "Active", the EndDate column equals null. Where the SimpleEndDate column equals "June
30, 2002", the EndDate column equals 2002-06-30 00:00:000. Therefore, this property has two
different datatypes. It can return either a DateTime or a string (Char).
This can result in missing valid data when filtering.
For example, create the following list report in Query Studio using the Adventure Works sample
cube and the Adventure Works DW catalog.
Create the following list report in Query Studio:
Product/Product Categories/Product Name
Product/Product Categories/Product Name/End Date
Measure: Resellers Gross Profit
Apply the following simple detail filter: End Date: June 30, 2003. Notice that a blank page is
rendered; it is missing all valid filtered data.
To avoid this problem, when modeling properties in SSAS 2005, avoid specifying both the
NameColumn and ValueColumn properties. You can also avoid filtering on properties that have
both the NameColumn and ValueColumn attributes specified.
557127
Red X Characters Appear in Data Tree When Using a PowerCube
In Report Studio and Analysis Studio, when you use a Cognos PowerCube and expand the metadata
tree, you may see a red x and you may encounter the following error messages:
●
●
ANS-MES-0007
DPR-ERR-2065 The response from Report Server is not well formed.
36

Chapter 1: Cognos 8 Known Issues
This problem occurs most commonly when using the control codes x01-x1F, which are used to
represent graphics in DOS.
To avoid this problem, edit the cube to remove all characters that are not supported by XML
Version 1.0 when using the Windows-1252 encoding.
561249.1
Relationships Not Maintained in a Report With Overlapping Set Levels
In a report, the relationship between nested or parallel sets at overlapping levels in the same
dimension may not always be maintained.
For example, a named set in the data source that contains members from both a Year and Month
member is nested under Year, but is not properly grouped by year.
In another example, an error message such as this appears: "OP-ERR-0229 The following projected
data items (at least one of them has more than one level) have overlapping levels and the results
may not be what you expect: 'dataItem="Set1"; dataItem="Products"' , '{1}'".
This problem occurs in the following scenarios involving non-measure data items X and Y, that
overlap in the same dimension:
●
●
●
X and Y together as ungrouped report details
Y nested under X
Y appended as an attribute of a group based on X
When using named sets, or sets that cover more than one level of a hierarchy, do not use sets from
the same dimension in more than one place in the same report. They should appear on only one
level of one edge.
567492
Unexpected Results May Occur When Using Items from the Same Hierarchy on
Multiple Crosstab Edges
A crosstab that contains items from the same hierarchy on more than one edge may have
unpredictable results, and may change from release to release. For example, in an analysis that uses
items from Years on rows and Quarters on columns, unexplainable More values and Totals, and
unexpected blank cells may appear. Also, expected results may be difficult to read because the useful
numbers are distributed over a large area of mostly blank cells.
For best results, ensure that items from the same hierarchy are on the same crosstab edge before
saving.
565201,571084, 480409
Metric Designer Issues
This section contains known issues about Metric Designer.
Readme 37

Chapter 1: Cognos 8 Known Issues
Adding Multiple IQD files to an Import Source
When you add multiple IQD files to an import source, Metric Designer creates an outer join between
the first pair of non-numeric, non-date columns with matching names. The join approach is designed
to work with a single fact IQD file and with multiple dimension IQD files.
Metric Designer does not recognize joins where more than one column is required for a join
condition. In this case, enter the IQD files into Metric Designer as separate import sources or
combine into a single IQD using Impromptu.
440049
Previewed Scorecard Hierarchy Shows Blanks
If you use if () then () else () statements in an expression for level attributes, you will see blank
entries when you preview the scorecard hierarchy.
The workaround is to change the expression to cast the query item to VARCHAR. For example:
if (cast([great_outdoors].[Locations].[Locations].[Country].[PPDS_CODE],VARCHAR(1000)) =
'Canada') then ('Craig') else ('George')
if ( cast([great_outdoors].[Locations].[Locations].[Country].[Country] ,VARCHAR(1000)) =
'Canada') then ('Craig') else ('George')
To eliminate duplicates for items other then Canada' you can add a level filter expression. For
example
[great_outdoors].[Locations].[Locations].[Country].[Country] = 'Canada' or [great_outdoors].
[Locations].[Locations].[Country].[Country] = 'China'
508879
Scorecard Exclusion Settings Lost
In OLAP extracts, after setting exclusions and clicking Refresh, some excluded members are still
included. This occurs when the Append Scorecard ID to Parent ID level attribute is set to No for
scorecards with duplicate IDs.
As a workaround, in the mapping dialog box, always set the Append Scorecard ID to Parent ID
attribute to True.
492546
Metric Studio Issues
This section contains known issues about Metric Studio.
Metric Studio Reports Fail Because of an Oracle Internal Error
Some reports that are included with Metric Studio fail to run because of an Oracle internal error.
This occurs when you are using 10.2.0.x releases of Oracle.
38

Chapter 1: Cognos 8 Known Issues
The reference bug for Oracle is 5864217.
If you encounter this error, you can resolve it by installing Oracle 10.2.0.3, Patch 5 which is officially
named 5946186. This patch can be obtained from the Oracle Support's Metalink site which is
available through your existing support agreement.
Apply the patch as directed by the instructions included with the download from Oracle Support.
567585
Metric Studio Errors Occur When Loading Data into an Oracle Database
The application is disconnected from Oracle with ORA-07445 and ORA-3113 errors. You can see
these errors in the database alert log. The database errors then cause errors in Metric Studio.
This is a known issue with Oracle (Bug 5026836 - Ora-7445 [Kxccres()+3052] Updating View
With Instead Of Trigger)
The workaround is for the database administrator to run the following command while logged in
as SYS:
If an SPFILE is in use ALTER SYSTEM SET optimizer_features_enable='10.1.0' SCOPE=BOTH
If an SPFILE is not in use, ALTER SYSTEM SET optimizer_features_enable='10.1.0'
If an SPFILE is not in use, the database administrator should also add this setting to the init.ora
file for the database instance.
530992
510492
Oracle Errors Occur When Using the cmm_uninstall Script
Oracle internal errors occur when clearing an Oracle schema using the cmm_uninstall script. The
errors occur if using the undocumented FORCE option
The errors are caused by an existing Oracle bug that is scheduled to be fixed in version 11. Details
can be found in Oracle Note 338953.1
The errors can be avoided by disabling the recycle bin using one of the following methods:
●
●
In the init.ora file, add the line _recyclebin = false and restart the database
Run the command SQL> alter system set "_recyclebin" = false scope=spfile; and restart the
database
531440
Length of Filter Expression is Limited for Cube Queries
Filter expressions have length limitations. Expressions that are longer than the limitations are
truncated and do not work when referenced.
The current limitations, by platform, are as follows:
●
SQL Server is 4000 characters
Readme 39

Chapter 1: Cognos 8 Known Issues
●
●
Oracle is 2000 characters
DB2 is 1350 characters
There is no workaround if the filter expression is longer than the maximum length indicated.
A future release will increase the limit for all platforms.
561356
Error When Attempting to Run Metric Studio on SQL Server 2005
When clicking a scorecard, a SQL Server error appears:
Msg 169, Level 15, State 1, Line 3 - A column has been specified more than once in the order by
list. Columns in the order by list must be unique.
This has been identified by Microsoft as bug #484681 and occurs in Microsoft SQL Server 2005
RTM (Build 9.00.1399). The problem was resolved by Microsoft in Microsoft SQL Server SP1.
If you encounter this error, you can resolve it by installing Service Pack 1 for SQL Server 2005 (or
later).
577840
Erroneous Re-assignment of Actions
If you create a scorecard and a metric with the same identification code, add an action on the metric,
export all data, then import and transfer the exported files into the metric store, the action appears
in the Project tab on the scorecard.
Similarly, the problem may happen on the project. If a project was added on the scorecard, after
export and import it appears in the Action tab on the metric.
To resolve this problem, use unique identification codes for the scorecards and the metrics if the
scorecards have projects or the metrics have actions.
576895
Query Studio Issues
This section contains known issues about Query Studio.
Report Studio Issues
This section contains known issues about Report Studio.
OP-ERR-0231 Invalid Parameter Error
In Report Studio, if you provide a value expression instead of a member parameter when you use
certain functions (for example, Union), the query fails with an error message such as the following:
40

Chapter 1: Cognos 8 Known Issues
OP-ERR-0231 Invalid parameter '[GetMore+0]' provided for 'union' at position '2' for
'dataItem="union"'. This parameter is expected to be one of the following: 'memberSet'
In previous releases of Report Studio, this action did not result in an error.
To restore Report Studio to the previous behavior, use the Member function to assign the value
expression to the hierarchy required by the context where it is used.
For example, if your original value expression is union([Year],[Calc1]), where the data item Calc1
is [2001]+1, the result is the following error message:
OP-ERR-0231 Invalid parameter '[Calc1]' provided for 'union' at position '2' for
'dataItem="union"'. This parameter is expected to be one of the following: 'memberSet'
As a workaround, place Year and Calc1 side-by-side on the row or column edge (as opposed to
nesting Year and Calc1 under each other) to avoid the union.
However, if you must have Year and Calc1 in the same set, the union function requires that the
parameters be sets or members in the same hierarchy. For this example, you can accomplish this
in one of the following ways:
●
●
Create Calc1 as a calculated member instead of a query calculation, and specify the hierarchy
that Year belongs to.
Use the advanced function member: member([Calc1], hierarchy([Year]).
582613
Aggregate of Minimum Returns Meaningless Results
In the Report Studio Express authoring mode, if you select the Always create extended data items
options (from the Tools menu, Options, Report tab), and if your report includes a minimum
aggregate, the values that are returned may be meaningless.
For example, the following report includes a minimum aggregate for the nested set set(1996 Q1,1996
Q2) and for the set set(OutdoorsProducts,Environmental Line). However, both these aggregates
are incorrect. They do not show the minimum value.
To avoid this problem, you can
●
●
swap the rows and columns in the crosstab
change the solve order using the Report Studio Professional authoring mode
Give Minimum a higher solve order than Aggregate. For more information, see the Report
Studio Professional Authoring User Guide.
●
change the aggregate to use an explicit aggregation function such as Min or Total
576441
If you use this option, you must be familiar with the data because there may still exist situations
in which you could receive a meaningless result. The most common such case is when using
measures that have unknown rollup rules.
Readme 41

Chapter 1: Cognos 8 Known Issues
Limited Calculated Member or Measure Expressions in Express Authoring Mode
The Report Studio Express authoring mode contains a limited number of expressions that you can
use in calculations. You should use only the expressions and functions available in the user interface,
and follow their syntax. We do not recommend that you build calculations or summaries on top
of other calculations that were authored in the Professional authoring mode.
In the Report Studio Express authoring mode, minimal checking exists for calculations. If a calculated
member or measure uses an invalid expression, your report results may contain unexpected values.
In addition, when defining member summaries, you should limit your expressions to one of the
following:
●
summary_function (currentMeasure within set set_reference)
where set_reference is a level or set inserted from the Source or Query tabs of the Insertable
Objects pane.
Unless otherwise required, summary_function should be aggregate. If you use an explicit summary
function, you may encounter problems with measures and scenario or account dimension members
(such as profit margin, distinct count, and so on) that have complex rollup rules, or members that
do not roll up.
Know your data, and confirm with the owner of the cube where overriding the automatic aggregation
is safe.
Because of the above limitations, summaries of calculations may not provide reliable values. For
convenience, you may have to build reports where row summaries and calculated member columns
intersect. In such reports, these intersections may contain unexpected values. In contrast, row
calculations intersecting with column aggregates using the aggregate function is safe because the
calculation is performed on the reliably summarized values.
If you need to create expressions that are more complex, use the Report Studio Professional authoring
mode.
549157
Master-detail or Burst Reports with Charts May Generate Large Temporary Data
Files and Fail
When running a master-detail or burst report that includes charts and maps, disk space exhaustion
may cause the report or other requests to fail.
A large set of burst keys or master rows may produce one or more charts per detail, resulting in
many master-detail executions. This may cause the "\temp" folder to accumulate many gigabytes
of temporary files containing data required for successful chart rendering.
To avoid this issue, we recommend that you test large master-detail or burst reports that include
charts to determine the potential peak disk requirements for the report.
576267
42

Chapter 1: Cognos 8 Known Issues
Unexpected Summary Values in Nested Sets
If a report contains nested sets, summaries other than the inner set summaries may contain
unexpected values. For example, a crosstab contains a set with years in the rows and you insert a
summary. You then nest a product line set within years but the summary value does not change to
represent the total of the new values.
This occurs because the within set aggregation that Report Studio uses with dimensional packages
does not take into account sets that are nested below the set that is summarized.
To show the correct summary values and if the nested sets are from different dimensions, you can
nest a copy of the inner summary item under the outer summary item.
You can also drag the members in the inner set to the Context filter area. This forces the inner set
to be taken into account in all parts of the report, regardless of which dimensions the members are
from.
For more information, see the knowledge base document number 1036319.1 on the Cognos Global
Customer Services Web site (http://support.cognos.com).
576832
Applying Filters to Dimensional Reports
Dimensional data sources do implicit rollup at all levels of each dimensional hierarchy. Detail filters,
summary filters, and slicers with more than one member invalidate any precomputed rollup of
members at hierarchy levels above the level at which the filter applies. Because of this, we recommend
that you avoid combinations of filters and slicers with members at these hierarchy levels.
You can apply the following filters to a dimensional report:
●
●
●
Detail filters and summary filters in list reports with no dimensional expressions other than
level references.
Detail filters and summary filters in crosstabs with no dimensional expressions other than level
references, optionally combined with the aggregation type within detail or within
aggregate.
Dimensional expressions that use the filter function, provided that the condition is independent
of context.
The condition in the filter function must be written so that it returns the same value regardless
of what it intersects with elsewhere in the report. One way to do this is to use the
completeTuple function.
For example, you may have one of the following expressions:
filter([Products], [Revenue]>1000)
filter([Products], tuple([Revenue], currentMember(hierarchy([Products]))) >1000)
If you do, change it to the following expression:
filter([Products], completeTuple([Revenue], currentMember(hierarchy([Products]))) >1000)
Readme 43

Chapter 1: Cognos 8 Known Issues
This ensures that the default member of all other dimensions is used in the condition, which
returns the same result at all intersections.
●
Slicers with a single member per dimension.
When you use any of these filters with a calculated fact or measure, you may see #Error! as values
for some or all of the cells in the report that represent an aggregate that is calculated in the database
(aggregate function is set to Automatic). This means that the data source is unable to compute these
values. You can work around this by using an explicit rollup rule or aggregation function such as
Total. However, do this only if you are familiar with the data and absolutely certain that this is the
correct answer for that report.
nbna
Limitations When Using FOR Clause in Summary Functions
A summary function that uses a FOR clause may yield unexpected results. These may include error
messages, warnings, incorrect numbers, and more or fewer than expected rows, columns, or chart
points and lines.
To avoid these problems, ensure that the parameters that follow the FOR clause adhere to the
following constraints:
●
●
●
●
●
●
Parameters must be simple data item references.
All data items in the parameter list must appear on every list, crosstab, or chart that uses that
summary.
For any edge used in the FOR clause, data items listed in the FOR clause must start with the
first data item on that edge.
Data items must be listed in the order in which they appear on each edge of the report, with
no gaps.
In crosstabs and charts, there must be no sibling data items that are considered details. Summaries
are normally not considered details.
Section headers must not be included in the parameter list.
If following these constraints does not resolve the problems, and your report uses dimensional data
with no detail or summary filters, consider using the WITHIN SET clause instead of the FOR clause.
Running Totals Are Incorrect in Crosstab Reports
Running totals are not calculated correctly when they are summed across a dimension. This is
because Cognos 8 does not currently support queries with both dimensional functions and running
totals. For example, when you drill down in a report, the query contains the dimensional function
children, which is not compatible with running totals. Running totals are supported only for the
overall level of a dimension.
Currently, there is no workaround.
546796
44

Chapter 1: Cognos 8 Known Issues
Ragged or Unbalanced Hierarchies Result In Unexpected Behavior
In ragged or unbalanced hierarchies, some members that are not at the lowest level of the hierarchy
may have no descendants at one or more lower levels. Support for these hierarchy gaps in relational
sources is limited. For OLAP sources, more complete support is provided, but some reports may
result in unexpected behavior.
●
●
●
●
Groups corresponding to missing members may appear or disappear when grouped list reports
are pivoted to a crosstab. This happens with set expressions using the filter function, and detail
filters on members.
Ragged and unbalanced sections of the hierarchy are suppressed when set expressions in that
hierarchy are used on an edge.
When a crosstab is sectioned or is split into a master-detail report, sections corresponding to
missing members become empty.
Members that have no parent at the level under which they are nested do not summarize
correctly.
Some of these behaviors may be corrected in a future release, while others may be codified as
supported behavior. To avoid these behaviors, avoid the scenarios above.
The following scenarios are believed to be safe:
●
●
●
●
One or more nested level references on an edge, with no modifying expression.
A hierarchy reference on only one level of one edge.
One or more explicit members or sets of explicit members as siblings on only one level of one
edge.
Summaries of the previous three scenarios.
In all cases, reports based on ragged and unbalanced hierarchies should be tested to confirm that
hierarchy gaps are handled correctly.
529310
536799
536813
539603
582784
Different Results for List Reports and Crosstabs that Use the Same Set Expression
In a list report, a set expression such as TopCount produces fewer rows than the corresponding
crosstab report.
For example, in a list report with Year in the first column, followed by a column containing an
expression that returns the top three months by revenue, there will be only three rows in the report,
corresponding to the top three months across all years. If you group by Year, the report still shows
only three months. However, in a crosstab report, you will see three months for each year.
Readme 45

Chapter 1: Cognos 8 Known Issues
This behavior is a change from ReportNet, which delivered the same results for crosstabs as for list
reports.
In crosstab reports in Cognos 8, set evaluation is always done in the context of what the set is nested
under in the report. However, in list reports set evaluation is done independently of the grouping.
For example, if the first column contains Country instead of Year, you see the top three months
for each country (across all years) in both cases.
In the case of different dimensions, Report Studio authors can force context independence by
replacing [Revenue] in the TopCount expression with the Tuple( [Revenue], X ), where X is the
default member of the hierarchy containing Month.
However, for nested levels in the same hierarchy, there is no such workaround at this time.
This behavior may change in a future release. At that time, a mechanism will be provided to upgrade
existing reports for both ReportNet and Cognos 8 in a way that preserves their current behavior.
537122, 537143
Key Transformation Validation Level Returns Partial Information
In Report Studio, if you revalidate a report using Validate with Options, and select the Key
Transformation validation level, you will get back all errors and warnings, but you may get little
or no information back regarding the transformation steps from the report specification to the
native query sent to the data source.
While the documented description for the Key Transformation validation level is correct, the feature
is only partially implemented at present.
Slow SSAS 2005 Query Performance When Using the Key Attribute Hierarchy
When using a Microsoft SQL Server 2005 Analysis Services (SSAS) cube, you may experience slow
performance when the query accesses the key attribute members in a parent-child dimension through
the key attribute hierarchy. You may encounter the following error:
Memory error: Allocation failure: Not enough storage is available to process this command.
This problem is more apparent when the query contains a large number of calculated members.
From the SSAS performance monitor log, you may see that the Analysis Services process uses a
large volume of memory. You may also see a large number of subcube requests when the query is
executed.
As a result, the Analysis Services service may run out of memory and crash, which requires that the
administrator restart it. Or that service may require a high memory usage, and affect the performance
of all future queries.
To avoid this problem, in the SSAS 2005 cube, make all the key attribute hierarchies of the
parent-child dimensions invisible by setting their AttributeHierarchyVisible property to false. Report
authors do not see these hierarchies and cannot insert them. For more information, see the Microsoft
knowledge base article 938495 (http://support.microsoft.com/kb/938495).
548723
46

Chapter 1: Cognos 8 Known Issues
Redrawing or Refreshing Issues with Prompt Controls
In the report viewer, if a prompt uses radio buttons and you select to reprompt, the prompt controls
may flicker or dynamically resize depending on the complexity of the report page and on the number
of prompt controls that are embedded within the page.
The prompts still work as expected.
531880
Error When Opening Hyperlink Button URLs in PDF Reports
If a PDF report includes hyperlink buttons that open a URL constructed from expressions that use
data item values, you cannot launch the URL and you encounter a page not found error.
To avoid this problem, run the report in HTML format.
573940
Precision of Percentage Values Are Changed After Upgrading a Report
When you upgrade a report to from Cognos 8 version 8.2 to version 8.3, percentage values lose
two decimal places, which affects the precision of the values. For example, 0.15% becomes 0%.
This problem occurs because the data format on the Text Item object is removed and instead is
placed on the cell (List Column Body object). This also happens in the summary row.
To avoid this problem, manually reapply the data format.
579608
Bookmark Links in a Chart Legend Do Not Work in PDF Viewer
You create a chart on page 1 of a multipage report, with a bookmark drill through to a data item
label, then you create an embedded chart in a list with a master detail relationship on page 2 and
a bookmark object referencing the bookmark drill through.
When you run the report in PDF and try the report legend bookmark links, the links do not work.
To avoid this issue, we recommend that you run the report in HTML.
572593
A Chart is Compressed in PDF When Margin Property is Changed
A chart whose margin property has been changed may appear compressed when you run the report
in PDF.
To avoid this issue, we recommend that you run the report in HTML.
572959
Chart Background Color Does Not Apply to Notes Area
The note area does reflect the same background colour as the rest of the chart.
Readme 47

Chapter 1: Cognos 8 Known Issues
You can change the background colour of the note after you create it.
572999
SAP BW Data Sources Issues
The following issues were identified with software components of SAP BW data sources. We are
managing the status of these problems with the vendor, but, at the time of this release, the following
issues are still unresolved in the product.
Count Summaries in Query Calculations Include Nulls with SAP BW Data Sources
When using an SAP BW data source in Report Studio, null values in the database are returned in
the result set and the Count summary function includes the empty cells in the following scenarios:
●
●
A query calculation includes an arithmetic calculation where one or more NULL operands and
an aggregation is performed on the calculation.
The result of a query calculation is a constant, such as current_time() and current_date().
The Count summary function should normally exclude NULL values.
To avoid this problem, for the first scenario, ensure that both operands do not return null values.
For example, the original expression is [num1]+[num2]. Instead, use the following expression:
if([num1] is null) then ( 0 ) else ([num1])
if([num2] is null) then ( 0 ) else ([num2])
There is no workaround for the second scenario.
564890, 570900, 568001
Incorrect Units of Measure in Calculations
When creating calculations in Report Studio and Query Studio, you may encounter problems with
the units of measure. For example, the calculation Cost*Cost returns the unit of measure CAD^2
in BEx but * in Cognos 8.
Change the format of the corresponding column to obtain the desired unit of measure.
421591
Grouping Columns That Have the Count Summary
If you add the Count summary to a non-fact column in a list and then group the column, the column
will not be grouped when you run the report.
To resolve this issue, group the column first before adding the Count summary.
435017
48

Chapter 1: Cognos 8 Known Issues
Missing Measures in Crosstab Reports
If you have a crosstab with multiple measures (multiple summary types and semi-additive
aggregations), one measure may not render if the default aggregation function for the measures is
set to Automatic.
To resolve this issue, set the default aggregation function to None.
437751
Crosstab with the Same Dimension on Both Edges Returns No Data
If you run a crosstab report that has the same dimension on both edges, the report will not return
any data.
To resolve this problem, specify that data not be suppressed for the query that is driving the crosstab.
Steps to Specify That Data Not Be Suppressed
1. In the report layout, right-click the crosstab and click Go to Query.
2. In the Properties pane, click the Suppress property and click None.
3. Save the report.
545657, 545661
Custom Formatting for Empty Cells Does Not Appear in Cognos 8
If the SAP BW server administrator configures custom formatting for empty cells on the SAP BW
server, the custom format does not appear in Cognos 8 reports.
Administrators should configure the formatting of empty cells in Cognos 8.
425064
Creating Sections on Reports That Access SAP BW Data Sources
SAP BW data sources may have problems with sections in reports under different circumstances:
If a section in a report uses the lowest-level query item in a ragged hierarchy, such as the children
of the "not assigned" node, the following BAPI error may appear:
BAPI error occurred in function module BAPI_MDDATASET_SELECT_DATA. Value
for characteristic unknown
If you create a section in a report using conformed multicubes with SAP variables, an SAP error
message may appear.
Lowest-level Query Item in a Ragged Hierarchy
The solution is to remove the section from the lowest-level query item.
443696
Readme 49

Chapter 1: Cognos 8 Known Issues
Several Multicubes with SAP Variables
The solution is to use one multicube when creating sections in reports.
437613
Summary Rows Return Incorrect Total Values
When the rollup summary function of a measure is minimum, summary rows return incorrect total
values.
Currently, there is no workaround for this problem.
409532
Calculated Key Figures Appear with the Non-aggregate Icon
Calculated key figures appear with the non-aggregate icon in the Key Figures folder.
To solve this, edit the variable in SAP BW and set the TIME OF CALCULATION to Before
Aggregation.
nbna
Filter Expressions Using Report Items and Smart Prompts Do Not Return Values
If you create a filter expression such as the following, no data is returned.
[ ] = ?prompt?
To resolve the problem, do one of the following:
●
●
Fully qualify the item by using items from the metadata tree instead of the report item tree
Build smart prompts in the report instead of hand coded prompts
495958496340
Security Issues
This section contains known issues about security.
Existing Passwords May not Work in an SAP Namespace
When you log on to Cognos Connection using an SAP namespace, some previously functional
passwords may no longer work. The following error message may appear: "Unable to authenticate
a user. Please contact your security administrator. Please type your credentials for authentication".
This is because of a policy change in SAP software. In previous versions of SAP software, passwords
were not case sensitive. All password characters were automatically converted to uppercase. In SAP
RFC 6.40, password characters are not automatically converted to uppercase and so passwords
are case sensitive.
50

Chapter 1: Cognos 8 Known Issues
To address the password policy change, the SAP BAPI interface introduced a new configuration
parameter named bapiPasswordConv. Using this parameter, you can enable or disable the
functionality that automatically converts all password characters to uppercase. To ensure that all
previously created passwords can still provide successful logon to Cognos Connection, set the value
of the bapiPasswordConv parameter to true.
Steps to Change the Setting of the bapiPasswordConv Parameter
1. Open the file bapiint_config.xml.
This file is located in the c8_location\bin directory.
2. Change the value of the bapiPasswordConv parameter to true, as shown in the following
fragment of code:
3. Save the file.
4. Restart the Cognos 8 service.
For more information, see the following SAP Notes:
●
792850 - Preparing ABAP systems to deal with incompatible passwords
● 862989 - New password rules as of Web AS ABAP 7.0/NetWeaver 2004
nbna
Users Are Repeatedly Prompted for Credentials When Trying to Log On to an
SAP Namespace
When users whose user IDs or passwords contain special characters try to log on to an SAP
namespace, they are repeatedly prompted for credentials and may not be granted access.
This is because SAP BW systems, version 3.5 and older, by default use a non-Unicode code page.
Newer SAP systems use a Unicode code page. As a result, the default SAP server code page was
modified for the SAP authentication provider to use a Unicode code page, which is SAP CP 4110.
To avoid this issue, in Cognos Configuration, modify the default SAP BW Server Code Page
parameter for the SAP authentication provider to use a non-Unicode code page, such as SAP CP
1100.
nbna
Readme 51

Chapter 1: Cognos 8 Known Issues
DPR-ERR-2079 Error When Using a Search Type of Migration in the New Job
Wizard
If you start a search from the New Job wizard in Cognos Connection and you select Migration as
the Search type, when you click Search, the following error appears:
DPR-ERR-2079 Firewall Security Rejection - Your request was rejected by the security firewall.
CAF rejection details are available in the log. Please contact your administrator.
If you reference the cogserver.log file in the c8_location\logs directory, it will include log messages
similar to the following:
Audit.dispatcher.caf Request Failure invalid variable: name => search_type
Audit.dispatcher.caf Request Failure invalid value: decoded value => migration
Audit.dispatcher.caf Request Failure value does not match pattern: pattern => ^(agents|all|consistency|
dataMovements|deployment|distribution|documents|groups(AndRoles)?|indexUpdate||jobs
(AndAgents)?|metricsTasks|package|pagelet|planning(Macro)?Tasks|reports|users|user(s)?Groups
(AndRoles)?|urls)$
Audit.dispatcher.caf Request Failure invalid variable: value => migration
Migration type searches are not supported in this release. Select another search type.
564868
Series 7 Integration Issues
This section contains known issues about Series 7 integration.
Unsupported Cognos Planning 7.3 Features with Cognos 8
The following Planning - Contributor 7.3 (or later) features are unsupported with Cognos 8.
●
Publish to Cognos Metrics Manager admin extension
If you do not have PowerPlay Enterprise Server, the following features are also unsupported.
●
●
Publish to PowerPlay Enterprise Server admin extension - All unpublished data source tasks
View in PowerPlay Web client extension
nbna
52

Chapter 1: Cognos 8 Known Issues
Third-Party Issues
Adobe Reader Displays Corrupted Characters in the Bookmarks Pane
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.
Firefox Add-on Adblock Plus Prevents Cognos Connection Menus From Working
Installing Adblock Plus with Firefox blocks the java script for all menus in Cognos Connection.
To unblock the Cognos Connection menus, uninstall Adblock Plus.
Importing a Large Content Store in Solaris using JRE 1.5 Fails
If you export a content store that is greater than 2 GB when exported, and then attempt to import
it in Solaris using JRE 1.5, the import fails with the error message "CM-SYS-5001 A Content
Manager internal error occurred."
This is due to a bug in JRE 1.5 on Solaris. Use JRE 1.4.2 instead.
560146
Cognos 8 Running under WebLogic Application Server on AIX Fails
The Cognos 8 server instance may go into a FAILED_NOT_RESTARTABLE state in the WebLogic
Administration Console. Numerous core files and Java core files are written to the Cognos 8 domain
directory. Cognos 8 terminates and is not accessible via the portal.
This behavior occurs only when the Cognos 8 Managed Node is started with the WebLogic
Administration Console. Start the Cognos 8 Managed Node using the WebLogic startup scripts
instead.
575696
Unable to View HTML Output in Internet Explorer When Running under WebLogic
9.1.0
A new Cognos Viewer configuration parameter, htmlOutputDataEncoding, that defaults to
MIMECompressed has been added to resolve performance problems when viewing large HTML
reports. However, this encoding makes it impossible to view HTML reports in Internet Explorer
when Cognos 8 is running on WebLogic 9.1.0.
Customers using WebLogic 9.1.0 must edit the file /webapps/p2pd/WEB-INF/
classes/viewerconfig.properties and change the line
htmlOutputDataEncoding=MIMECompressed
Readme 53

Chapter 1: Cognos 8 Known Issues
to
htmlOutputDataEncoding=MIME
577823
Importing a Large Deployment in Windows Crashes the Java Virtual Machine
The Java virtual machine under Windows crashes under the following circumstances.
1. The maximum Java memory setting is Medium (1152MB) or higher.
2. You are importing a large archive from a previous release of Cognos 8.
3. The archive contains large models that require upgrading.
To resolve this issue, set the maximum Java memory setting to Small (768MB).
576426
Transformer Issues
This section contains known issues about Cognos 8 Business Intelligence Transformer 8.3.
Content May Be Removed When Transformer 8.3 PowerCube Packages Are
Republished
If your version of Transformer 8.3 has a version number that is lower than 8.3.821.0, and you
replace an existing PowerCube package in Cognos Connection, the content under the package,
including reports and folders, will be removed. To confirm the version number of your installed
Transformer 8.3 component, open Transformer and then, from the Help menu, click About
Transformer.
This problem occurs when you publish a PowerCube package, and the following conditions exist
together:
●
A package with the same name already exists in Cognos Connection.
When this situation occurs in the Transformer user interface, you receive the following warning:
"(TR0165) The name ’package name’ already exists. You can replace the existing entry or
create a new name."
●
You choose to replace the existing entry when publishing the package.
This action can be performed in the Transformer user interface or using the command line
options in a batch script.
When a PowerCube package in Cognos Connection is replaced, you can only recover the missing
reports and folders by restoring the content store from a backup copy.
This problem will not occur when you use the publishing features in Framework Manager or Cognos
Administration.
In Transformer 8.3, you can publish PowerCubes using three different methods:
54

Chapter 1: Cognos 8 Known Issues
●
●
●
using the Publish wizard
publishing the cube using the current settings
creating a publish specification
A publish specification allows publishing options to be used in the Transformer command line
for batch jobs after cube builds.
When you rebuild and republish PowerCubes, you do not have to replace the package in Cognos 8.
This is because you only need to update the data source connection to enable the refreshed cube.
Therefore, cubes that are rebuilt and refreshed will not be impacted by this problem unless the
Transformer user or batch script explicitly specifies that the package be replaced.
Cognos recognizes this problem as a product defect. To install a downloadable fix for this problem,
●
●
●
go to the Cognos Global Customer Services Web site (http://support.cognos.com)
click Support to open the Cognos Support Services home page
under Support Home, click Product Information/Advisories
Logon credentials are available either from your administrator or by request from support.
login@cognos.com.
●
Under Product Advisories, click the link for Cognos Enterprise Business Intelligence Products,
and then search for the entry for Cognos 8 Business Intelligence 8.3 dated January 16, 2008
entitled "Content may be removed when publishing PowerCube Packages from Transformer
8.3".
Until you install the downloadable fix for this problem, we strongly recommend that you follow
these practices:
●
●
When you publish a PowerCube package and data source from the Transformer 8.3 user
interface and you are prompted to either replace the existing entry or enter a new name for the
package, always choose to enter a new name for the package.
When you script cube builds and deployment scenarios in a batch file, do not alter the default
value of the package overwrite parameter in the command line specification.
When the package overwrite parameter is false, the publish action fails when a package with
the same name exists in Cognos Connection. As a result, the existing package cannot be
overwritten. However, if you change the default value of the package overwrite parameter to
true, published PowerCube packages having the same name will be overwritten in Cognos
Connection, resulting in lost content.
●
Maintain a current backup of your Cognos 8 content stores.
583153
Support for Microsoft Excel 2007
Transformer 8.3 does not support Microsoft Excel 2007 XLSX files as a data source.
Readme 55

Chapter 1: Cognos 8 Known Issues
Limitations on Using Reports in Transformer
Transformer does not support Cognos 8 reports that run against OLAP data sources (Microsoft
Analysis Services (MSAS), SAP BW, PowerCubes, Essbase). DMR-based list reports are supported
in Transformer.
Missing Values May Vary Results in PowerCubes
When your data contains missing values, the data values in PowerCubes created with Cognos 8
Transformer 8.3 may be different from the data values in PowerCubes created with previous versions
of Transformer.
Transformer uses default measure settings for missing values to determine how null results are
handled. In previous releases of Transformer, the default setting for missing values was zero; when
the default setting was used, zeros were inserted for the missing values. In Cognos 8 Transformer
8.3, the default setting for missing values is NA; when the default setting is used, NA is inserted
for the missing values.
The default setting can also affect the values that are stored and shown for calculated measures.
When a calculated measure is based on a measure for which the missing value default setting is
zero, and there is no data for this second measure, the calculation result will be valid because the
missing information is treated as a zero. However, when the missing value default setting is NA,
the calculation result will be NA because the missing information is treated as a null value and not
a zero.
Upgraded models are not impacted and the model will continue to use the value of either zero or
na as set in the Series 7 model; upgraded models will preserve their Series 7 behavior.
Queries Against Multiple Hierarchies in the Same PowerCube Dimension Do Not
Execute
In Cognos 8.3, when you run a query against a PowerCube requesting data from more than one
hierarchy in the same dimension, you receive an error message indicating that the action is not
supported. As a result, the report does not execute.
Your request fails to execute because, in Cognos 8 studios, any grouping of categories from the
same dimension that disregards the primary hierarchical organization, such as relative time categories,
special categories, or categories from an alternate drill path, is interpreted in Cognos 8 as a distinct
new hierarchy in that dimension.
To avoid errors and inconsistencies, if you must support a query containing multiple hierarchies
from a single dimension, one possible solution is to manually create new special categories in the
Transformer model, and then move the existing categories you require to the new special categories.
For this approach to work, you must retain at least one of the previously existing categories in the
original structure, for example, the convergence level of a multiple drill hierarchy.
Note: When you create the new special categories, you can accept the default property values.
For information about creating special categories, see the Transformer online help.
529184
56

Chapter 1: Cognos 8 Known Issues
Aggregate Values for Imported Query Items May Not Match the Source Package
or Report
When you import a Report Studio, Query Studio or package data source, and the Regular Aggregate
rule is something other than Sum, the aggregate value for the dimension will not match the value
in the original report.
In Transformer 8.3, measures imported from packages or reports will default to the Transformer
Sum rollup rule.
To maintain the same rollup rule defined in the source package or report, set the Transformer
measure definition to use the same rollup rule as defined in the source package or report.
568940
Prompts Values in Multiple Queries
When you use a Query Studio or Report Studio report as a data source and the report contains
prompts, and you attempt to add another query to that data source in Transformer 8.3, you will
not be reprompted for new values. This means that your newly added query will return data using
the same prompt values as your first query.
To avoid this situation, when you add the new query, click the Refresh Source button. You will be
reprompted to enter new values for the prompts in your report data source.
nbna
Prompts for Member Unique Names in SAP-BW Packages
When you use a SAP-BW package as a dimensional metadata source and the package contains
prompts for members (Member Unique Names), the prompt interface is not the same in
Transformer 8.3 as in the Cognos 8 Web studios.
Transformer will present a similar interface that allows you to the select the MUN. However, when
you edit the prompt at a later time, Transformer will restart at the beginning rather than from the
previous value.
nbna
Updated pcoptimizer Utility Included in Cognos 8.3
The pcoptimizer utility adds metadata to a previously built PowerCube to speed up Cognos 8
PowerCube query performance. This utility was delivered with previous releases of Cognos 8 and
Transformer, but it has been updated in Cognos 8.3 to allow for increased metadata caching in
cubes.
In Transformer 8.3, pcoptimizer is enabled by default. As a result, there is no need to use pcoptimizer
with Cognos 8.3 PowerCubes.
If you are using a PowerCube built in a previous version of Transformer and you optimized the
cube either by using the optimization setting in the trnsfrmr.ini file during the cube build or by
Readme 57

Chapter 1: Cognos 8 Known Issues
running the pcoptimizer utility on the cube after it was built, ensure that you update the cube
optimization by using the new Cognos 8.3 pcoptimizer.exe utility.
The Cognos 8.3 pcoptimizer.exe utility is located in the installation_location\bin directory.
Note: PowerCubes that were created with Series 7 Transformer without the pcoptimizerini setting
enabled will work in any version of Cognos 8. While these cubes do not need to be optimized to
be queried in Cognos 8, performance may suffer.
nbna
Transformer 8.3 Installation Download
Transformer can now be made available more easily for business specialists who want to design
models and build PowerCubes for their own use. For example, IT departments can provide business
specialists or Transformer modelers with a Web-based, downloadable installation program from
a corporate or secured portal, allowing for easy distribution of the installation files.
For installers and administrators, see the topic "Create a Network Installation Location for
Transformer Modelers" in the Installation and Configuration Guide. For business specialists and
Transformer modelers, see the topic "Deploying Cognos 8 Transformer for Modelers" in the
Installation and Configuration Guide.
Note for Transformer modelers: The Installation and Configuration Guide is available from a link
on the Welcome page of the Transformer installation wizard. When you run the c8transformerinstall.
exe file from the Web or LAN location that an installer or administrator sets up, the installation
files are extracted to a temporary location on your computer and then the installation wizard
launches automatically.
Regular Columns cannot be Converted to Calculated Columns and Vice Versa
When you attempt to convert a regular column to a calculated column by opening the Column
property sheet, the Calculated button is unavailable.
In Transformer 8.3, you can no longer convert an existing regular column to a calculated column
by changing the column properties. Similarly, existing calculated columns cannot be converted into
regular columns by changing the column properties.
In Transformer 8.3, you can only create calculated columns using the Insert Column feature. For
more information, see "Define a Calculated Column" in the Transformer User Guide.
This change in functionality does not affect how calculated columns are imported from a Series 7
model into Transformer 8.3. Existing calculated columns originally created in Series 7 will be
imported correctly.
Framework Manager and Transformer may Display Different Locale Session
Parameters for Some Languages
Transformer 8.3 may not return data in the expected locale during test or cube build when the
following conditions are encountered:
58

Chapter 1: Cognos 8 Known Issues
●
●
The locale shown in the File/Session information in Transformer is not included in the
Framework Manager parameter map for session parameters.
The modeler attempts to create a data source in Transformer using a query subject from the
package where the locale does not exist.
When this is encountered, the locale of the modeler’s session parameter does not exist in the
Framework Manager parameter map. As a result, the data returned will not be the locale of the
Session information shown in Transformer.
To avoid this problem, add the locale string that is displayed in the Transformer File/Session
information to the Framework Manager parameter list so that Transformer can retrieve the expected
data when accessing the data source. However, the model metadata will still be shown in English,
or in the Framework Manager design language.
An Error May Occur in Reports Created in a Different Language than that Used
in the Package Design Locale
If you create a report in a language that is different from the language specified in the Framework
Manager package design locale, you may get an error that an object does not exist.
This error may occur when both of the following situations are true:
●
●
The locale of any expressions in a report are designed in a value other than the design locale
of the underlying package.
Any objects in a hierarchical structure have the same name.
For example, a dimension containing hierarchy, levels, and query items of the same name would
cause this problem.
To avoid this situation, change the locale of the report to match the design locale of the package.
580003
Connection Error Occurs with Password-protected PowerCubes
When you attempt to use a password-protected PowerCube in Cognos 8 applications, you may get
the following error:
Connection Failed: Attempts to connect to the data source failed. There may be a configuration
issue with the database. The system administrator may need to test and reconfigure the connection.
This error occurs when the password checkbox was selected in the data source connection, but a
password was not supplied.
Loading the PowerCube metadata in any Cognos studio will invoke a password prompt. The prompt
is cleared when you type the password. The error occurs when you attempt to re-type the cube
password.
To avoid this situation, type and save the password in the PowerCube data source connection
sign-on defined in Cognos Connection.
580407
Readme 59

Chapter 1: Cognos 8 Known Issues
Data Records that Support External Rollup Measure Data are Not Always Created
When PowerCubes are built, data records that support External Rollup Measure data are not
created in certain circumstances.
Please contact customer support to receive a software update. After you apply the update, you can
rebuild the PowerCube with the expected results.
579654
Building a PowerCube on an AIX Machine May Result in a Core Dump During
Cube Build
When you build a PowerCube on an AIX machine, a core dump may occur. By default, AIX
applications have a maximum of approximately 250 MB of virtual memory, regardless of the
available memory on the target machine.
To avoid this problem, set the environment variable as follows:
setenv LDR_CNTRL MAXDATA=0x80000000
577355
Unable to Open Sample Model, Great Outdoors Sales.mdl, and Generate Cubes
If your setup information for the Great Outdoors Sales.mdl is incorrect, you will be unable to open
the sample model for Transformer, Great Outdoors Sales.mdl, or generate cubes.
To avoid this problem set up the Great Outdoors Sales.mdl as follows:
1. Modify the C7g.ini to contain [Databases] connections.
2. Open ODBC Data Source Administrator and create a new ODBC data source named
great_outdoors_warehouse to connect to the SQL server database, GOSALESDW, which is
provided with the sample installation.
3. Connect using a valid User Id and password for SQL Server authentication.
4. Open the model.
60

Chapter 2: Cognos 8 Documentation Updates
This section contains information about Cognos 8 BI documentation updates.
Cognos 8 Administration and Security Guide
This section contains additions and corrections that will appear in the next version of the Cognos 8
Administration and Security Guide.
Set Up the Essbase Cube Sample
Note: This topic will replace the topic "Set Up the DB2 Cube Sample" in a future release.
To set up the Essbase cube sample, you must have Hyperion Essbase and Essbase Integration Services
Console installed.
Steps
1. Go to the c8_location\webcontent\samples\datasources\cubes\Essbase\Outlines_and_Raw_Data
directory.
This directory contains zip files for the different languages, such as EN.zip or JA.zip for English
and Japanese, respectively.
2. Unzip the file for your language.
Each zip file contains the following two files:
●
●
languageU_Data.txt, such as ENU_Data.txt or JAU_Data.txt.
GODWlanguageU.otl, such as GODWENU.otl or GODWJAU.otl.
3. Using block storage in Essbase, create a Unicode application.
4. Within the application, create a new database.
You can use GODWlanguageU, such as GODWENU or GODWJAU, as your database name,
or use the name of your choice.
5. Copy and paste the GODWlanguageU.otl file in your database directory.
6. If the database name specified in step 4 is different than GODWlanguageU, rename the
GODWlanguageU.otl file to match the database name that you created.
Confirm that you want to overwrite the .otl file.
7. In Essbase Administration Services console, open your database outline and save it.
Confirm that you want to save the outline even if it was not changed.
Readme 61

Chapter 2: Cognos 8 Documentation Updates
8. Copy the languageU_Data.txt file and paste it in the same directory as the .otl file.
9. In Essbase Administration Services console, right-click the database you created and select Load
Data.
10. Browse to the languageU_Data.txt file in your database directory, select the file, and click OK.
11. After the data loads successfully, right-click the database and select Execute Calculation.
12. Select the default calculation, and click OK.
The calculation process may take up to 5 hours, depending on the computer where Essbase
OLAP Server is installed.
You can now create a data source connection to the cube.
Defining Global Filters
Note: The following information will be added to this topic in a future release.
Using Metrics as Global Filters
You can use metrics as global filters in a page or in a dashboard with multiple tabs. The page must
contain a Metric List portlet and a Cognos Viewer portlet configured to show reports associated
with the metrics. You must also set up communication between the Metric List and the Cognos
Viewer portlets using the channel property in both portlets. When a user clicks a metric name in
the Metric List portlet, the Cognos Viewer portlet dynamically updates the associated reports based
on the parameters of the clicked metric. For this functionality to work, the names of the metric
parameters must match the names of the report prompt parameters. Currently, the following
parameters are supported by the Metric List portlet:
●
●
●
●
●
●
scorecard_extid
scorecard_sid
strategy_sid
metric_sid
metric_extid
time_period_sid
Data Sources and Connections
Note: The following information will be changed in this chapter in a future release.
●
The following sentences contain errors.
"You can make more than one data source connection available by combining them, along
with other elements, in packages created in Cognos Connection (for OLAP data sources) or
created and published using Framework Manager."
The sentences should read:
62

Chapter 2: Cognos 8 Documentation Updates
"You can make more than one data source connection available by combining them, along
with other elements, in packages created and published using Framework Manager. You can
also make a Cognos PowerCube data source connection available by creating a package and
publishing it from Cognos Connection."
●
In the following sentence in the section "Create a Data Source", step 7, replace the phrase “If
you created an OLAP data source" with "For Cognos PowerCubes ".
If you created an OLAP data source, a confirmation appears and you are given the option to
create a package using your new data source.
Samples
Note: The following information will be changed in this chapter in a future release.
The name of the sample model go_sales will be changed to great_outdoors_sales, and the name of
the sample model go_data_warehouse model will be changed to great_outdoors_warehouse.
Secured Functions and Features
Note: The description of the Drill Through Assistant secured function in this topic, chapter “Securing
Functions and Features “, is incorrect. The description should read as follows:
This secured function controls access to the drill-through debugging functionality in Cognos 8.
Drill-Through Access
Note: The following information will be added to the topic "Conformed Dimensions"in this chapter.
Dimensionally Modelled Relational Data Sources
In addition to ensuring that each level contains a business key that has values that match your
PowerCube or other DMR models, you must also ensure that the Root Business Key property is
set and using the business key of the first level in the hierarchy. This helps to ensure that you have
a conformed member unique name when attempting to drill through using members from this
dimension.
Cognos Portlets
Note: The following information will be changed in a future release of the Administration and
Security Guide and Cognos Connection User Guide:
The name of the portlet group Metric Studio Portlets is changed to Cognos Metrics.
Deploying Cognos Portlets to Microsoft SharePoint Portal Server 2003 and 2007
Note: The topic "Changes in the web.config File" must be updated in the following way:
●
Add the following information to the section of the web.config file under
the , element:
Readme 63

Chapter 2: Cognos 8 Documentation Updates
●
Correct an error in the code example in the section "Specify the Cognos Configuration
Parameters". The SoapLog element in this example does not include a closing tag.
The code must read as follows:
Reset Metrics for the System
Note: This topic will be added to the section System Performance Metrics in the Cognos 8
Administration and Security Guide in a future release.
You can reset all metrics for the system at the same time. Some metrics cannot be reset. An example
is the JVM metrics that are calculated since the last reset time.
Steps
1. Start Cognos Connection.
2. In the upper-right corner, click Launch, Cognos Administration.
3. On the Status tab, click System.
4. In the Scorecard pane, click Actions, Reset all metrics of the system.
Apply the Same Threshold Setting to Multiple Entries Using a Template
Note: The following information is removed from this topic because the functionality is not available
in Cognos 8.
You can set metric thresholds to change the state of a metric score. In this release, you can not
apply the same threshold to multiple entries using a template.
Enable Users to Open Series 7 PowerPlay Reports in Analysis Studio or Report
Studio
Note: This topic will be removed from the Administration and Security Guide in a future release.
64

Chapter 2: Cognos 8 Documentation Updates
This topic is outdated. For relevant information, see the 8.3 version of the "Migration Tools User
Guide", chapter 5 "Migrating PowerPlay Reports Published to Cognos 8".
New Tools in Global Customer Support
Cognos Customer Support now uses a new web application, called Cognos Insight!, for logging
product and account inquiries. The appearance and terminology have changed. For example, "cases"
are now called service requests.
As well, the primary contact for each customer uses Cognos Insight! to maintain all support contacts
and web logins for users in their organization.
Cognos 8 Analysis Studio User Guide
This section contains additions and corrections that will appear in the next version of the Analysis
Studio User Guide.
Specify the Purpose of Your Output
Note: This topic will be added to the Analysis Studio User Guide in a future release.
You can specify the output of your analysis to suit your purpose. Differences may exist between
an Analysis Studio analysis and a report created to be run in Cognos Viewer in such areas as
●
●
●
performance optimization
drill-up and drill-down behavior
preservation of items such as subtotals, More values, and so on
Steps
1. From the Run menu, click Report Options.
2. On the Output Purpose tab, specify the purpose of the output:
●
To create a report featuring the current state of the analysis that is as close as possible to
the original created in Analysis Studio, select View as analysis.
This option is best if the output must be printed, or if the output must be consistent whether
it is launched from Analysis Studio or run from Cognos Connection.
Note: This option makes unavailable the drill-up and drill-down capability in Cognos
viewer.
●
To create a report that you can explore by drilling up or down in Cognos Viewer, select
Use as interactive report.
3. Click OK.
This output may be modified by the drill rules of Cognos Viewer, and may have some
visual differences from the analysis as seen in Analysis Studio.
Readme 65

Chapter 2: Cognos 8 Documentation Updates
Cognos 8 Analysis Studio Quick Tour
The next version of the Analysis Studio Quick Tour will include the following corrections.
●
The suppress button shown on the toolbar is incorrect. The correct icon appears in Analysis
Studio.
Cognos 8 Event Studio User Guide
This section contains additions and corrections that will appear in the next version of the Event
Studio User Guide.
Tutorial - Creating an Agent
Note: This topic will include the following corrections in the next version of the Event Studio User
Guide.
To create this example agent, perform the following tasks:
❑
❑
❑
Start Event Studio and select the Go Sales (query) package.
Define a parameter named total_return_value_for_item.
Define a calculation named order_item_return_value_calc.
Example - Define a Parameter
Note: This topic will include the following correction to step 2 in the next version of the Event
Studio User Guide.
In the Parameter name box, type total_return_value_for_item.
Example - Define a Calculation
Note: This enhanced topic will appear in the Event Studio User Guide in a future release.
You want to define a calculation named order_item_return_value_calc that you can insert into an
event condition. This calculation must determine the value of each order item returned.
Steps
1. From the Insert menu, click Calculation.
2. In the Name box, type
order_item_return_value_calc
3. In the Expression box, do the following:
●
●
In the Insertable Objects area, click the source tab and expand Returned items (query).
Under Returned items (query), expand Returned items.
66

Chapter 2: Cognos 8 Documentation Updates
●
●
Click the Return quantity measure item, and drag it to the Expression box.
After the source item you just inserted, type an asterisk:
*
●
●
●
Expand Sales (query).
Under Sales (query), expand Sales.
Click the Unit sale price measure item, and drag it to the end of the expression.
The calculation expression is defined as follows:
Returned items (query)].[Returned items].[Return quantity]*[Sales (query)].[Sales].[Unit sale
price]
4. Click OK.
The calculation appears as a calculation icon on the data items tab.
Example - Specify an Event Condition
Note: This topic will include the following correction to step 7 in the next version of the Event
Studio User Guide.
On the data items tab, click the order_item_return_value_calc calculation that you defined previously,
and drag it to the end of the expression.
Example - Add a Report Task
Note: This topic will include the following correction to step 6 in the next version of the Event
Studio User Guide.
Specify the prompt values that you want:
●
●
●
In the Method column, click Use an item.
In the Insertable Objects area, click the source tab and expand Retailer site.
Click Retailer name, and drag it to the Value box.
Example - Change the Task Execution Rules for a Report Task
Note: This topic will include the following additional step following step 3 in the next version of
the Event Studio User Guide.
Click Include only selected items.
In addition, the last three bullets in step 7 will be deleted.
Example - Add an Email Task
Note: This topic will include the following correction to step 9 in the next version of the Event
Studio User Guide.
In the second cell, type Value of items returned.
Readme 67

Chapter 2: Cognos 8 Documentation Updates
Note: This topic will include the following corrections to the last bullet of step 11 in the next version
of the Event Studio User Guide.
Expand Sales (query), then expand Retailer site, and click Retailer name and drag it to the fourth
cell.
Example - Add a News Item Task
Note: This topic will include the following correction to step 4 in the next version of the Event
Studio User Guide.
In the Headline box, type Preventable Returns for Large Value Individual Items.
Cognos 8 Installation and Configuration Guide
This section contains additions and corrections that will appear in the next version of the Cognos 8
Installation and Configuration Guide.
JDBC Driver Conflict for Oracle
If you use Oracle for data source, import source, logging database, or the content store database,
you must ensure that there is no conflict with the JDBC driver file. In earlier releases of Cognos 8,
Oracle databases required a classes12.jar file. In Cognos 8 Version 8.2, Oracle databases require
an ojdbc14.jar file.
To ensure that there is no conflict, check the c8_location\webapps\p2pd\WEB-INF\lib directory on
each computer where Content Manager, the Application Tier, Framework Manager, or Metric
Studio is installed. If both the classes12.jar file and the ojdbc14.jar file are present, you must delete
the obsolete classes12.jar file.
547145
Manually Changing the Installation Directory Name Affects Installations Running
Under an Application Server
You installed Cognos 8 using the installation wizard and later renamed the installation directory
or manually copied the contents to another directory. When you attempt to run Cognos 8 within
an application server, you may have one of the following problems:
●
●
●
Cognos 8 does not start.
Log directories are empty.
Logs contain a linkage error or unsatisfied link error.
When you manually change the installation directory, the information in the Cognos 8 root directory
becomes invalid. To resolve the problem, you must either update the Cognos 8 root directory before
68

Chapter 2: Cognos 8 Documentation Updates
you create the Cognos 8 application file to deploy to the application server or you must reinstall
Cognos 8 in the original location. If you reinstall Cognos 8, follow the process for upgrading.
Steps
1. In the new or renamed installation directory, open c8_location/webapps/p2pd/WEB-INF/classes/
cogroot.link in a text editor.
2. Replace the path with the new location of the installation directory and save the file.
3. To build the application file to be deployed to the application server, in Cognos Configuration,
from the Actions menu, select Build Application Files.
4. If you built and deployed an application file to the application server before updating the
cogroot.link file, undo the deployment.
5. Deploy the new application file to the application server.
For more information about configuring Cognos 8 for a third-party application server, see the
Installation and Configuration Guide.
538629
Configuring file location for Cognos 8 Framework Manager or Cognos 8
Transformer
Note: This topic will include the following correction in the next version of the Installation and
Configuration Guide.
If you install Cognos 8 in a Windows Vista environment, you must specify the file location relative
to the /bin directory for Cognos 8 Transformer and Cognos 8 Framework Manager. Step 4 in the
procedure, Update File Location, is corrected. For the Windows Vista environment, leave the relative
path element ".. " and add the appropriate environment variable.
For example, if you install Cognos 8 in the directory C:/Programs Files/Cognos/c8, and you want
a path to C:/Users/Public/c8, enter ../../../../Users/Public/c8 as the path.
Cognos 8 Metric Studio User Guide
This section contains additions and corrections that will appear in the next version of the Metric
Studio User Guide.
Changes to the Metric Model
The metric model has been enhanced to improve performance and to better expose the metric objects
for report authors.
Model Structure
The structure of the metric model is different from the previous release in the following ways:
Readme 69

Chapter 2: Cognos 8 Documentation Updates
●
●
●
●
●
●
●
●
●
●
●
Some query names and query item names have been changed to be more intuitive.
While all valid relationships between metric objects are persisted in the model, some relationships
between query subjects have been changed.
Star schema groups have been created for each subject of interest.
As groups have been replaced by strategies, the related query subjects have also been changed.
The strategy query subject exposes the strategies hierarchy, where the strategy is the root level
object and there are two child levels allowed: Strategy Elem1 (on level 1) and Strategy Elem2
(on level 2).
All query subjects have been revised to ensure that useful reporting information (through query
items) is available to the report authors.
Two query subjects have been added to support relative time (year to date, quarter to date, and
month to date periods).
The time dimension was added. Its hierarchy (with a maximum of 9 levels) is created or changed
whenever the calendar is created or changed.
Image URLs were added to query subjects containing comment priority, execution status, trend
status, and metric status.
The metrics included in the watch lists were exposed.
Support for user defined columns was added. For each user defined column, the following query
items are available: name, description, unit code, and number decimal places.
Predefined Filters
There are now two types of predefined filters: content filters, which can be used in reports to filter
on a selected metric item, and time filters, which can be used to specify the reporting period.
The time filters further subdivide into:
●
●
●
Relative time filters, which can be used to specify the relative period or the rollup grain for the
relative period.
Filters that provide support for the most recent period associated with a metric's history.
Filters that specify which type of time periods are used when reporting on the metric history:
regular time periods (from the time dimension) or relative time periods: Include Only Relative
Time Periods, Exclude Relative Time Periods.
Model Version Control
The metric package upgrade process has been modified so that if the model did not change, the
reports are not copied to the backup folder.
70

Chapter 2: Cognos 8 Documentation Updates
Status Lists
Status lists are now available for project and action execution status, metric status, and trend status.
These query subject lists are located in the Status Lists folder and have no relationships with other
query subjects in the model.
Linked Reports
This query subject lists all the reports linked, in Metric Studio, to metric objects. It has no
relationships to other query subjects in the model.
Metric Functions Folder
It contains functions that provide useful information for report authors.
Model Segmentation
The Compatibility namespace is contained in a segment of the metric model.
Presentation View
This view contains objects that are exposed to report authors.
Relational Namespace
This is the namespace that exposes metric objects to the report authors. All the query subjects in
this namespace are shortcuts to the query subjects contained in the Model namespace. This namespace
contains star schema groups, filters, and lists.
Star Schema Groups
The Relational namespace is a business view containing star schema groups that make the model
more intuitive for the users. In a star schema design, numeric transactional data is contained in a
central fact query subject with related dimension query subjects radiating out from the fact query
subject.
The following star schema groups have been created: Scorecards, Projects, Project Comments,
Metrics, Metric Comments, Actions, Action Comments, Impacting Metrics and Strategies. Each
star schema group may contain some specific filters.
Filters
The Relational namespace contains the predefined filters associated to the query subjects it contains,
grouped in the following folders.
●
Content Filters
These filters can be used to filter the appropriate query subjects based on the object id (or SID
from the database).
●
Time Filters
These filters can be used to filter the time dimension based on a selected time period id (or SID
from the database): Select Time Period; a selected fiscal year value: Select Fiscal Year; or a
Readme 71

Chapter 2: Cognos 8 Documentation Updates
named time level code (for year, quarter, month, week, day): Year Level, Quarter Level, Month
Level, Week Level, Day Level. These filters work only if the calendar contains the selected time
level.
●
Relative Time Filters
These filters can be used to filter the relative time query subject based on a selected time level:
Year To Date Level, Quarter To Date Level or a selected rollup grain: Quarter Grain Rollup,
Month Grain Rollup, Day Grain Rollup. These filters work only if the calendar contains the
selected time level (year, quarter, month) or grain (quarter, month, day).
Lists
The Relational namespace contains query subjects that have no relationships with other query
subjects (and do not belong to a star schema group) in the model, but may be useful for the report
authors. These are grouped in two folders. The Status Lists folder contains the Execution Status
List, the Metric Status List, and the Trend Status List. The Linked Objects folder contains the Linked
Reports.
Staging Namespace
The Staging namespace contains two folders: Stage and Rejects. The Stage folder contains query
subjects that return data from the staging area, therefore access to this folder should be restricted
to Metric Administrators. By default, it is just hidden from the user. The Rejects folder is available
to all users and exposes the tables containing the rejected data.
Model View
Hidden from the user, the Model view encapsulates the business logic. Query subjects from the
Relational namespace are only shortcuts to the query subjects contained in the Model view. This
namespace also contains the relationships between the query subjects and defines the calculations
for some of the query items.
Source View
Hidden from the user, the Source view contains the metric store import views. It uses the database
views to import metric metadata.
The database view names are prefixed with MOD_ and have been revised to improve performance.
Metric Functions
Predefined functions are now available to report authors:
●
●
Functions that return model versions: getMajorModelVersion, getMinorModelVersion.
Functions that return image locations: getBaseImageLocation, getRelativeImageLocation. These
are absolute, respective relative paths to the metric images and can be used to construct the
image URLs. The values returned by these functions are based on parameters whose values are
updated when the metric package is created (based on the location of the webcontent folder).
72

Chapter 2: Cognos 8 Documentation Updates
●
Functions that return the 'no data' image: getNoDataImage, getNoDataImageURL. These
return the image name, that is, the image URL, which can be used for report image objects
when the data item associated to that object contains no information (that is, is null or is
missing).
Compatibility Folder
The Compatibility folder contains the model released in versions 8.1 and 8.2. Views from this folder
are exposed to report authors only for compatibility reasons with reports written against those
model versions. It also contains the Printing namespace which is used by the Metric Studio printing
facility. The Compatibility folder is contained in a segment (named Compatibility) of the metric
model.
The Compatibility model contains groups, which have been replaced by strategies in the current
model.
The Linked Reports Query Subject
All the reports linked to metric objects are listed in the Linked Reports query subject. This query
subject is based on a database-stored procedure and can receive the following parameters:
●
time_period_sid int
● recent_data char (1)
●
●
●
period_start dateTime
period_end dateTime
date dateTime
● rollup varchar (5)
●
period_nr int
● period_level_cd char (1)
●
fiscal_year int
● currency varchar (5)
●
scorecard_sid int
● scorecard_extid nvarchar (255)
●
metric_sid int
● metric_extid nvarchar (255)
●
metric_type_sid int
● metric_type_extid nvarchar (255)
●
strategy_sid int
Readme 73

Chapter 2: Cognos 8 Documentation Updates
● strategy_extid nvarchar (255)
●
strategyelem_sid int
● strategyelem_extid nvarchar (255)
●
project_sid int
● project_extid nvarchar (255)
● scorecard_mun varchar (255)
● measure_mun varchar (255)
● filter_mun varchar (255)
● time_period_mun varchar (255)
For each parameter that is passed, the calculated report URL appends the parameter name and its
value.
One way to use this information while authoring a report is to create a master-detail report where
the master contains the metric object information and the detail contains the reports linked to that
object. The parent object id of the linked report is the id of the object to which that report is linked.
Setting the Linked Report Parameters
As long as the report parameter names can be found in the above list, a link can be established
between the context of the metric object (within the master report) and its associated report and
the linked report may be executed without the necessity to prompt for the report's parameters.
However, the user will be prompted for the parameter values if any of the parameters expected by
the linked report did not receive one.
Another way to provide values for the linked report parameters is to create report prompts whose
parameter names match the names of the linked report parameters.
If the linked report has parameters that are not contained in the list above, its calculated URL value
must be changed in Report Studio by appending (to the value provided in Linked Reports) the
following string:
'p_' + [other_param_name] + '=' + [other_param_value]
The Framework Manager metric model has defaults for all the report parameters. It cannot accept
null values. The report server will prompt for the parameters with null values.
Guidelines for Reporting
These are some things to consider when writing reports of the metric model.
●
●
●
Do not include in the same query data from two facts if they are not supposed to be linked by
time, as the generated query will link them by time.
The query plan starts first with dimensions from within the first star group.
If possible, use query items from the same star group where the fact data resides.
74

Chapter 2: Cognos 8 Documentation Updates
●
●
●
A query containing data from two facts will produce a stitched query.
Use the Actions star schema grouping when reporting on actions. If only metrics related to
existing actions are required, then use Metrics from the Metrics group.
Use the Scorecard Groups star grouping for queries that contain Metric, Scorecard and Strategy
query items. Use the Scorecards star grouping for queries that contain Metric and Scorecard
query items only (no Strategy information).
Metric Studio Support Bundle
If you must contact customer support for assistance, attaching the support bundle will help expedite
your case. This support bundle is a zip file generated by a tool called cmm_support_bundle.
The command is located in installation_location/bin and is invoked as follows:
cmm_support_bundle databaseServer databaseName databaseUser databasePassword databaseType
output_filename
where
●
●
●
●
●
●
databaseServer is the hostname of the database server (default: localhost). For Oracle you can
add an optional port by appending ':port' to the hostname (default = 1521). For example:
localhost:1234. The databaseServer parameter is ignored for database type 'db2'
databaseName is the name of the database (default: cmm). This is the 'database file' entry for
database type 'db2'
databaseUser is the database user name (default: sa)
databasePassword is the database password (default: cmm)
databaseType is the database type. Values can include sqlserver, oracle, db2 (default: sqlserver)
output_filename is the fully qualified name of the zip file to create (defaults to the
_SUPPORT_FILES directory)
For example, if a SQL Server database contains your metric store, issue a command such as
cmm_support_bundle dbserver1 prod_db sa topsecret sqlserver
or on UNIX
sh cmm_support_bundle.sh dbserver1 prod_db sa topsecret sqlserver
By default, this will create output in the installation location/_SUPPORT_FILES directory.
Readme 75

Chapter 2: Cognos 8 Documentation Updates
Add Email Notification for a Metric
By default, email notification about changes to a metric in the watch list is not selected when you
add a metric to the watch list. However, you can override the default. You must be logged on to
the namespace to add email notification.
Steps
1. At the bottom of the left pane, click My Folders.
Your watch list and accountability scorecard appears in the left pane.
2. Click Watch List and click the metric for which you want to add email notification.
3. In the right pane, click the button named click to turn on email alerts for this metric.
History Charts
A history chart is a graph that appears for each metric. You can use the history chart to analyze
the relationships between target values and actual values.
The history chart shows target values, actual values, target tolerance, and any specified user-defined
columns. Tolerance is the acceptable range that a result can deviate from the target. In the history
chart, a green diamond represents the target value, and yellow lines represent the tolerance.
A user-defined column is a comparative measurement for a metric. For example, revenue per month
is a metric that you monitor. Although this is an important metric, you are also interested in
comparing revenue to analyst forecasts. To compare revenue to analyst forecasts, the Metric Studio
author creates a user-defined column for analyst forecasts and then adds the column to the Revenue
metric type.
You can choose to view actual values and user-defined columns as line graphs or bar graphs.
A history chart shows the business calendar level that you selected.
The previous arrow shifts the graph one business calendar level left. The next arrow shifts the graph
one business calendar level right. For example, if months and quarters are shown along the bottom
of the graph, the previous arrow shifts the graph left by one month. The fast-previous arrow shifts
the graph one quarter to the left. The fast-next arrow shifts the graph one quarter to the right.
Specify Import Settings
You must specify the metric deployment location for the metric store. The metric deployment
location is the location of all the import source directories or folders for the current metric store.
You also select the import sources that are used by this metric package. You must define an import
source before you can select it.
Steps
1. In the Tools list, click Import Sources.
76

Chapter 2: Cognos 8 Documentation Updates
2. Specify the metric deployment location by clicking Change the deployment location and then
one of the following
●
Use the default deployment location
Choose this option if the location of your import source is installation _location\cognos\
c8\deployment.
This option should only be used in a single-server installation. In distributed installations,
a deployment location that is available on all servers should be specified using the Specify
another location option.
●
Specify another location
Choose this option if the location of your import source is not installation _location\cognos\
c8\deployment.
In a distributed installation, a deployment location that is available on all servers must be
specified.
In a Windows environment, you use a UNC path pointing to a share accessible by all
servers. You must use a UNC path and not a mapped drive to specify the metric deployment
location.
In Unix environments, an identical mount must be created on all servers.
3. Click OK.
4. Select the check box next to the import sources for this package.
Tips:
●
●
●
You can exclude import sources by selecting the check box under the Exclude from the
import column.
You can choose all import sources by selecting the check box next to Name.
You can exclude all import sources by selecting the check box next to Exclude from the
import.
5. Click OK.
Cognos 8 Transformer User Guide
These sections contain additions and corrections that will appear in the next version of the
Transformer User Guide.
Transformer Support for Prompts in Report Data Sources
You can use a Cognos 8 report created in Query Studio or Report Studio, or a Cognos 8 package
as a data source for a model in Transformer. These reports or packages may include prompts. When
executing queries, Transformer uses values you provide for the prompts.
Readme 77

Chapter 2: Cognos 8 Documentation Updates
When using a report with prompts as a data source, the user interface presented by Transformer
for prompts may be different than the user interface presented when running the report in the
Cognos studio. For example, a report with a prompt page defined to contain a single select
drop-down list may be presented in Transformer as a multi-value select list. This behavior occurs
because Transformer does not process any information from prompt pages of reports. Ensure that
you understand the purpose of each prompt when using a report as a data source.
For more information about Transformer support for prompts, see the Transformer User Guide.
562800
Data Source Types: Cognos Package or Report
In the next version of the Cognos 8 Transformer User Guide, Chapter 3: Data Sources for Your
Model, Data Source Types, the topic "Cognos Package or Report" will include the following
correction.
You can import query items from relational or dimensionally modeled relational packages and
reports, and the associated filters and prompts, by choosing the Cognos Package or Cognos Report
option and browsing and selecting from the available metadata. Note that:
●
●
●
When importing packages, Transformer ignores any zero suppression settings.
Transformer cannot view or override Framework Manager governor settings.
Query items that are calculated appear as regular query items. You should review the rollup
rules in Transformer when you use these calculated items as measures to avoid incorrect rollup
results. For example, a rollup rule of SUM should not be applied to a measure that uses a
calculated item when the value is expressed as a percentage.
Command Line Syntax
Note: This corrected topic will appear in the Transformer User Guide in a future release.
To use command line options, you must start the Transformer executable, cogtr.exe, from the
directory in which it is installed.
The syntax for using command line options with optional arguments is as follows:
cogtr -option[argument] filename.py?|filename.mdl
Notes:
●
On Windows, you can use -n with some options to run Transformer in batch mode.
● The option in the command line always starts with a dash (-).
●
●
●
Command line options are case-insensitive. Arguments are case-sensitive.
If there are spaces inside any argument, you must enclose the argument in double quotation
marks, for example
cogtr -n -k"field three=CarlosR/pw462" Field3.mdl
For .py? files, the question mark (?) is replaced by the character that is used in your version of
Transformer.
78

Chapter 2: Cognos 8 Documentation Updates
●
●
You can use more than one option in a command line. If an option that is used in a command
line is incompatible with an option that appears earlier in the command line, the earlier option
is ignored.
The filename.py? and filename.mdl files apply to Windows only.
Command Line Options
Note: This corrected topic will appear in the Transformer User Guide in a future release.
Transformer supports the following Windows and UNIX/Linux command line options. Detailed
explanations are provided in the subsections that follow.
Command line options are case-insensitive.
● -a
Runs AutoDesign then creates a cube, opens PowerPlay (Windows), and displays the report.
cogtr -a data_source
Restriction: Use on Windows only, with -d, -f, -r, and -nologo options.
● -c
Generates categories and creates cubes.
-c -pfilename.py?|-mfilename.mdl
Restriction: Use with -i, -m, or -p. On Windows, use with -n.
● -d
Overrides the specified user preference setting.
-dpreference_var=setting -pfilename.py?|-mfilename.mdl
● -e
Updates the model structure but not the data.
-e -pfilename.py?|-mfilename.mdl
Restriction: Cannot be used with -c. On Windows, use with -n. On Windows, UNIX, and
Linux, use with -o.
● -f
Specifies the user-defined preference file.
Can be used to publish PowerCubes in batch mode and include prompts in an XML command
file using the XML schema for preference files.
-fpreference_file -pfilename.py?|-mfilename.mdl
● -i
Opens the specified .py? model and restarts a failed process from the beginning.
-i -pfilename.py?
Restriction: On Windows, use with -n. On UNIX and Linux, cannot be used with -s.
● -h
Readme 79

Chapter 2: Cognos 8 Documentation Updates
Displays help for the command line.
cogtr -h
● -k
Specifies database signon information for Series 7.
-ksignon=userid/password -pfilename.py?|-mfilename.mdl
● -l
Specifies user authentication information for Cognos 8.
-lsignon=userid/password -pfilename.py?|-mfilename.mdl
● -m
Opens the specified .mdl file or accepts Model Definition Language (MDL) statements.
-mfilename.mdl
● -n
Runs cogtr in batch mode.
-ndisplay_state -pfilename.py?|-mfilename.mdl
Restriction: Use on Windows only.
●
-nologo
Omits splash screen display when opening Transformer.
-nologo -pfilename.py?|-mfilename.mdl
Restriction: Use on Windows only.
● -o
Turns off various model and cube creation actions.
-o -pfilename.py?|-mfilename.mdl
●
-ox
Disables category creation and cube rebuild.
-ox -pfilename.py?|-mfilename.mdl
Restriction: Use on Windows only.
● -p
Opens the specified binary model file, .py?, where the question mark (?) is replaced by the
character that is used in your version of Transformer
-pfilename.py?
Restriction: Not valid with an MDL file.
● -r
Specifies the level of detail for error-logging reports.
-rlog_level -pfilename.py?|-mfilename.mdl
Restriction: Valid levels are 0, 1, 2, 3, and 4.
● -s
Saves the model.
80

Chapter 2: Cognos 8 Documentation Updates
-s -pfilename.py?|-mfilename.mdl
Restriction: On Windows, use with -n; cannot be used with -i or -p.
● -t
Sets the current period.
-tcategory_code -pfilename.py?|-mfilename.mdl
Restriction: On Windows, use with -n.
● -u
Gets the partition status for previously generated cubes.
-upowercube_name -pfilename.py?|-mfilename.mdl
Restriction: Cannot use this option with secured cubes. On Windows, use with -n.
● -v
Specifies the number of records for the test cube.
-vdata_subset_number
Restriction: Use with -c, -m, or -p. On Windows, use with -n.
● -x
Updates the column and measure scales based on the data source.
-x -mfilename.mdl
● -y
Specifies how Series 7 user-class security conversion is performed.
●
●
Use -y1 to preserve both the Series 7 user classes and custom views associated with the
Series 7 model.
-y1namespaceName=username/password
Use -y2 to preserve only the custom view associated with the Series 7 model.
cogtr.exe -n2 -ox -s -y2 -mfilename.mdl
● Use -y3 to discard the Series 7 user classes and custom views associated with the Series 7
model.
cogtr.exe -n2 -ox -s -y3 -mfilename.mdl
-c option
Note: This corrected topic will appear in the Transformer User Guide in a future release.
This option loads a model file, interprets MDL statements, generates categories, and creates cubes.
Use this option with the applicable file-opening option: either -p, -m, or -i. On Windows, use this
option with -n.
The syntax for using the -c option is as follows:
cogtr -c -pfilename.py?|-m
filename.mdl
Readme 81

Chapter 2: Cognos 8 Documentation Updates
The following UNIX/Linux example uses -c and -p options together to open the binary model file
go_sales.pyj and process it as described.
cogtr -c -pgo_sales.pyj
The following UNIX/Linux example uses the -c and -m options together to open the equivalent
full model definition (the .mdl text file for go_sales), and process it as described.
cogtr -c -mgo_sales.mdl
577343
-n option
Note: This corrected topic will appear in the Transformer User Guide in a future release.
This Windows-only option runs Transformer in batch mode, creates the cubes identified in the
model, and then closes Transformer.
You can also specify a window display state of 1 to minimize the Transformer window, or 2 to
hide the window. There is no space between -n and the display_state argument.
The syntax for using the -n option is as follows:
cogtr -ndisplay_state -p
filename.py?|-mfilename.mdl
The following example opens the model file, Roofing.mdl, without displaying an application
window, creates its defined cubes, and then saves the model file.
cogtr -n -sRoofing.mdl
The following example opens the model file, Roofing.mdl, and creates its defined cubes:
cogtr -n2 -mRoofing.mdl
Cognos 8 Transformer Man Page
This section contains additions and corrections that will appear in the next version of the Transformer
Man Page.
-h option
Note: This corrected topic will appear in the Transformer Man Page in a future release.
This option displays help for the command line. Help is also displayed if you do not provide any
command options.
The basic syntax for using the -h option is as follows:
cogtr -h
-i option
Note: This corrected topic will appear in the Transformer Man Page in a future release.
This option opens a saved model, regardless of the existence of a checkpoint file. You cannot use
the -i option with the -s option.
82

Chapter 2: Cognos 8 Documentation Updates
A checkpoint file is automatically created when a model is suspended due to a general system failure,
such as that caused by a power outage. The next time the model is opened in interactive mode,
users can open either the checkpoint file or the last-saved version of the model file. In batch mode,
you can use the -i option to bypass the prompt and force Transformer to open the original model
file instead of the checkpoint file.
The basic syntax for using the -i option is as follows:
cogtr -i filename.py?
Note: Checkpoint files have a .qy? extension. As with .py? files, the ? (question mark) in the extension
is replaced by the character that is used in your release of Transformer, such as .qyj.
The following example opens the model file, Sales.py?, discarding any existing checkpoint file, then
runs the process in batch mode to create all defined cubes:
cogtr -i Sales.py?
Cognos 8 Report Studio Professional Authoring User Guide
This section contains additions and corrections that will appear in the next version of the Report
Studio Professional Authoring User Guide.
Nested List Report Containing a Data Item That is Grouped More Than Once Does
Not Run After Upgrade
Note: This topic will be added to the Troubleshooting appendix in the Report Studio Professional
Authoring User Guide and the Administration and Security Guide in a future release.
When you upgrade a nested list report that contains a data item that is grouped in both lists, the
report does not run and an error such as the following appears:
OP-ERR-0199: The query is not supported. The dimensions on the edge are inconsistent. The
dataItems from dimension="[Product line]" must be adjacent.
This error occurs when the report is run against a dimensional data source and both lists are using
the same query. This error does not occur if the report is run against a relational data source.
For example, you have a list that contains the grouped items Product line and Product type and a
nested list that contains the data items Year, Quarter, and Unit sale price. Year, Quarter, and
Product line are grouped items in the nested list.
To resolve the issue, delete the data item that is grouped in both lists from the inner list.
Steps to Delete a Grouped Data Item From an Inner List
1. Click anywhere in the report.
2. In the Properties pane, click the select ancestor button and click the List link that represents
the inner list.
3. Double-click the Grouping & Sorting property.
4. In the Groups pane, select the data item that you want and click the delete button.
Readme 83

Chapter 2: Cognos 8 Documentation Updates
Grouping by an Attribute is Not Supported
Note: This topic will be added to the Report Studio Professional Authoring User Guide, the Report
Studio Express Authoring User Guide, and the Query Studio User Guide in a future release.
When working with dimensional data sources, grouping by attributes is not supported. If you group
by an attribute, the corresponding member is grouped instead, and there may be duplicate rows.
For example, a list report contains the columns Color and Product Code, where Color is an attribute
of Product Code. When you run the report, some colors, such as black, appear multiple times
because several products are available in black. Each product is available in only one color, so the
list has only one row for each product. Grouping the Color column does not change the output
because the grouping is done on the Product Code column, and there is only one row for each
product in the list. If the Product Code column is deleted, the output shows duplicate rows for some
colors, such as black.
Limitations When Aggregating Measures in Dimensionally Modeled Relational
(DMR) or Relational Data Sources
Note: This topic will be added to the Report Studio Professional Authoring User Guide, Report
Studio Express Authoring User Guide, and the Query Studio User Guide in a future release.
There are limitations when aggregating DMR measures, semi-additive measures, and relational
facts in crosstabs using the aggregation function count distinct, median, standard-deviation,
or variance. The following limitations can cause error cells when the report is run:
●
●
The aggregation function must apply to all members of a level or all children of a member.
You cannot use certain OLAP functions in detail filters that are applied to a dimension that is
not in the report or is at a level below what is being reported.
The supported OLAP functions are children, level, members, roleValue, and rootMembers.
●
●
●
●
●
●
You cannot define detail filters that reference one or more measures and are set to After auto
aggregation.
You cannot define slicers that have more than one member from a dimension that does not
appear in the report.
Slicers that have more than one member from a dimension that appears in the report produce
errors in all cells that are ancestors of the slicer members.
If a crosstab has a row that is a set of members from one dimension (dimension A) and another
row that is a set of members from another dimension (dimension B), and a slicer containing
members from dimension A is defined, error cells are produced in the row that contains members
from dimension B.
If a slicer is composed of members from a dimension, and a crosstab has a row that is a set of
members from a higher level than the slicer members, error cells are produced for that row.
Error cells are produced when drilling down on a crosstab that has two nested levels.
84

Chapter 2: Cognos 8 Documentation Updates
If any of these limitations are not taken into consideration in a calculation, the report will not run.
If there is a non-measure calculation that returns a constant or contains a summary function, and
the calculation has a lower solve order than the measure being aggregated, error cells are returned
for the aggregated measure.
In list reports, error cells are produced as a result of these limitations if the list uses an OLAP
function other than children, filter, level, members, roleValue, and rootMembers.
Creating Expressions Using SAP BW Data Sources
Note: The following information will be changed in a future release of the Report Studio Professional
Authoring User Guide:
You must consider the following when creating expressions using an SAP BW data source, or you
may not get the results you expect:
●
The case and if/then/else constructs are not supported in filters.
Cognos 8 Framework Manager User Guide
The Framework Manager User Guide includes procedures, examples, notes, tips, and other
background information to help you create a project, prepare a model for reporting, and create
and publish a package.
Additions and corrections will appear in the next version of this document.
When to Use Determinants
Note: This topic will include the following addition in the next version of the Guidelines for Modeling
Metadata and the Framework Manager User Guide.
While determinants can be used to solve a variety of problems related to data granularity, you
should always use them in the following primary cases:
●
A query subject that behaves as a dimension has multiple levels of granularity and will be joined
on different sets of keys to fact data.
For example, Time has multiple levels, and it is joined to Inventory on the Month Key and to
Sales on the Day Key.
●
There is a need to count or perform other aggregate functions on a key or attribute that is
repeated.
For example, Time has a Month Key and an attribute, Days in the month, that is repeated for
each day. If you want to use Days in the month in a report, you do not want the sum of Days
in the month for each day in the month. Instead, you want the unique value of Days in the
month for the chosen Month Key. In SQL, that is XMIN(Days in the month for Month_Key)
.
There is also a Group by clause in the Cognos SQL.
There are less common cases when you need to use determinants:
Readme 85

Chapter 2: Cognos 8 Documentation Updates
●
You want to uniquely identify the row of data when retrieving text BLOB data from the data
source.
Querying blobs requires additional key or index type information. If this information is not
present in the data source, you can add it using determinants. Override the determinants
imported from the data source that conflict with relationships created for reporting.
You cannot use multiple-segment keys when the query subject accesses blob data. With summary
queries, blob data must be retrieved separately from the summary portion of the query. To do
this, you need a key that uniquely identifies the row and the key must not have multiple segments.
●
A join is specified that uses fewer keys than a unique determinant that is specified for a query
subject.
If your join is built on fewer columns than what is stored in Framework Manager within the
determinants, there will be a conflict. Resolve this conflict by modifying the relationship to
fully agree with the determinant or by modifying the determinant to support the relationship.
●
You want to override the determinants imported from the data source that conflict with
relationships created for reporting.
For example, there are determinants on two query subjects for multiple columns but the
relationship between the query subjects uses only a subset of these columns. Modify the
determinant information of the query subject if it is not appropriate to use the additional
columns in the relationship.
Remap an Object to a New Source
Note: This topic will be updated with the following information in the next version of the Framework
Manager User Guide.
The Set as Default check box was removed from the Remapping Options dialog box. When you
change the matching criteria for remapping, you are specifying the criteria that will be used to
remap subsequent objects.
Merge Projects
Note: The first four steps in this topic will be updated with the following information in the next
version of the Framework Manager User Guide.
Steps
1. Open the project into which you want to merge a branch.
2. From the Project menu, click Merge from.
3. In the Select Project to Merge From dialog box, click the Files of Type list and click All Files
(*.*).
4. Locate the log.xml file for the branch to be merged, and click Open.
86

Chapter 2: Cognos 8 Documentation Updates
The Perform the Merge window opens, showing a list of transactions. The transactions that
you selected are run.
Framework Manager requires only the log.xml and the IdLog.xml files, not the entire set of
project files to populate the transaction history list. If you do open the .cpf file directly when
prompted, Framework Manager locates and opens the log.xml file. The advantage of directly
opening the log.xml file is to reduce the number of large files that may need to be distributed
in a multiuser environment.
Publish a Package
Note: The first three steps in this topic will be updated with the following information in the next
version of the Framework Manager User Guide.
Steps
1. Select the package you want to publish.
2. From the Actions menu, click Package, Publish Packages.
3. Choose where to publish the package:
●
●
To publish the package to the report server, click Cognos 8 Content Store, click open, and
select an existing folder or create a new folder in the Content Store.
To publish the package to a network location, click Location on the network. Ensure that
you select a different location than the directory where the project files are stored. In general,
avoid saving to the same location as a model as the model could be overwritten.
579753
Readme 87

Chapter 2: Cognos 8 Documentation Updates
88

Chapter 3: Deprecation Notices
This section contains information about Cognos 8 BI deprecation notices.
Supported Environments
The following list describes important information related to Cognos 8 supported environments:
●
●
●
●
SAP ended mainstream maintenance support for SAP BW versions 3.1c and 3.0b in December
2006. Cognos will continue compatible support for these versions in this Cognos 8 release.
Cognos will deprecate support for SAP BW 3.1c and 3.0b in the next major release of Cognos 8.
Informix ended support for Dynamic Server version 9.3 in April 2005. Cognos has deprecated
support for this version in this Cognos 8 release.
Informix ended support for Dynamic Server version 9.4 in April 2006. Cognos will continue
compatible support for this version in this Cognos 8 release. Cognos will deprecate support for
Dynamic Server version 9.4 in the next major release of Cognos 8.
Informix ended support for Red Brick Decision Server version 6.2 in April 2006. Cognos will
continue compatible support for this version in this release. Cognos will deprecate support for
this version in the next major release of Cognos 8.
● Cognos will discontinue support for Netscape browsers in the next major release of Cognos 8.
●
●
●
Sun ended support for Sun ONE Directory Server version 5 in June 2004. Cognos will continue
compatible support for this version in this Cognos 8 release. Cognos will deprecate support for
Sun ONE Directory Server version 5 in the next major release of Cognos 8.
Cognos support for SAP NetWeaver Portal 7.0 (SAP NetWeaver 2004s) is pending in this
Cognos 8 release.
IBM ended support for DB2 V9.1 on PA-RISC. Cognos has deprecated support for this platform
(HP PA-RISC) in this release of Cognos 8 Special Edition.
nbna
Framework Manager Security Filters for SAP BW: Notice of
Intent to Change the Default Setting
In all shipped versions of Cognos ReportNet and Cognos 8 including Cognos 8.2, the following
behavior has been enabled by default.
Multiple security filters defined within Framework Manager on metadata imported from SAP BW
sources are combined using 'AND' logic, effectively an intersection of a particular user's permissions.
Readme 89

Chapter 3: Deprecation Notices
This behavior is contradictory to corresponding behavior on relational data sources where similar
filters are combined using 'IN' and 'OR' (union) logic to facilitate cases where users belong to one
or more group and require a union of their permissions. The current default behavior for SAP BW
datasources has been determined to be a product defect and will be changed in the Cognos 8.3
release to align with the behavior of relational data sources. In the Cognos 8.1 Mr2 and Cognos 8.
2 releases, it will be possible to get the union of filters behavior by modifying the following switches
in the qfs_config.xml configuration file. Under , add the following new element:
Effect
When multiple security filters are defined in the Data Security setting in Framework Manager for
a query subject, if a user belongs to more than one user group associated with these filters, the effect
of this switch is to perform a union of these filters instead of an intersection. For example, if a user
Joe belongs to a corporate group allowing him to see data for Asia, Europe, and America, and also
belongs to a regional group allowing him only to see data for Europe, the effect of the switch will
be to let Joe see data for Asia, Europe, and America (as compared to just Europe) when logging on
Cognos 8 and authoring or running a report. Note that security filters that are based on other
security filters in the Data Security settings for a query subject continue to be intersected, just as
before, independent of whether or not the new switch is activated.
As of Cognos 8.3, this behavior will become the new default for SAP BW metadata in Framework
Manager. There will be no change to the behavior of security filters applied on relational sources.
The switch will continue to be available and can be set to false by your administrator if required
to maintain existing application behavior.
IQD Externalize Method
IQD's generated by Framework Manager will continue to be supported in this Cognos 8 release,
but will not be enhanced. Cognos will deprecate support for IQD's generated by Framework Manager
in the next major release of Cognos 8. Cognos 8 Transformer will continue to support IQD's
generated by Impromptu in the next major release.
Transformer OLE Automation
Previous versions of Transformer provided OLE automation support using a program language
interface as an alternative to the Transformer user interface. Product features introduced in version 7.
3 and higher were not supported using OLE automation.
In this Cognos 8 Transformer release, support for OLE automation in Transformer has been
deprecated. Transformer Model Definition Language (MDL) supports all Transformer features up
to and including version 8.3. MDL will continue to be the supported Cognos method for automating
Transformer models.
90

Chapter 3: Deprecation Notices
Transformer Client/Server Synchronization
Previous versions of Transformer included two different installations: the UNIX Server installation
and the Windows Client installation. This Cognos 8 release provides one version of Transformer.
This one version can be installed on the appropriate platform.
In this Cognos 8 Transformer release, client/server synchronization, including the PowerGrid
Network daemon and NetInfo, has been deprecated.
Transformer Data Source Support
In this Cognos 8 Transformer release, support for the following data source types has been
deprecated:
●
●
●
●
●
●
dBase table
Paradox table
Lotus 1-2-3 crosstab or database
FoxPro table
Clipper table
Architect models
Transformer .pyi Files
In Transformer 8.3, models saved in binary format now use the .pyj file extension. In Transformer 7.
x, models saved in binary format used the .pyi file extension.
Before upgrading Transformer 7.x models to Transformer 8.3, you must save your .pyi models in
the .mdl (text) file format. We strongly recommend that you keep a .mdl file backup of all Series 7
models that you upgrade to Transformer 8.3.
Transformer Menu Customization
Previous versions of Transformer allowed users to customize the menu options. This functionality
is not included in Transformer 8.3.
Compressed PowerCubes
Previous versions of Transformer allowed users to compress PowerCubes. This functionality is not
included in Transformer 8.3.
Readme 91

Chapter 3: Deprecation Notices
Cognos 8 Transformer Expression Editor Functions
Transformer 8.3 continues to use the expression editor included with previous Transformer releases.
However, the following expressions are no longer supported:
●
●
●
●
Pack
Spread
Substitute
Phdatetodate
Third Party OLAP Support
Cognos 8 Mobile Analysis is intended for disconnected data exploration and reporting using
PowerCubes.
In the next maintenance release of Cognos 8, support for third party OLAP data access will be
discontinued.
Secured PowerCubes
Cognos 8 Mobile Analysis is intended for disconnected data exploration and reporting on
PowerCubes that have not been secured with either Series 7 or Cognos 8 security sources. In the
next maintenance release of Cognos 8, support for disconnected secured PowerCubes will be formally
discontinued.
Cognos Viewer URL API (b_action=xts.run)
In previous releases of Cognos 8, the b_action parameter specified a value of xts.run and a
number of additional parameters to support launching Cognos Viewer using a customized URL
instead of using Cognos Connection. This parameter value is now deprecated and will be removed
in a future release of Cognos 8. A new value, cognosViewer, is available that provides the same
functionality. Continuing to use the deprecated parameter value will still work, but may result in
reduced performance.
The xts.run value is still valid, and is not deprecated, for components other than the Cognos
Viewer, such as Report Studio and Analysis Studio.
You can map xts.run parameters to cognosViewer parameters as shown below.
xts.run parameter -> cognosViewer parameter
ui.tool -> Not applicable
ui.action (default="view") -> ui.action (default="objectDefault")
ui.object -> ui.object
92

Chapter 3: Deprecation Notices
ui.header -> cv.header
ui.spec -> ui.spec
run.outputFormat -> run.outputFormat
run.outputLocale -> run.outputLocale
run.prompt -> run.prompt
run.xslURL -> run.xslURL
run.outputEncapsulation -> run.outputEncapsulation
async.primaryWaitThreshold -> async.primaryWaitThreshold
async.secondaryWaitThreshold -> async.secondaryWaitThreshold
run.version -> No equivalent
ui.toolbar -> cv.toolbar
Readme 93

Chapter 3: Deprecation Notices
94

Index
Symbols
.otl files, 61
.pro files, 66
-c option in Transformer, 81
-h option in Transformer, 82
-i option in Transformer, 82
-n option in Transformer, 82
A
accessing data sources, 20, 48
action logs
BmtScriptPlayer, 25
actions erroneously re-assigned
Metric Studio, 40
Administration and Security Guide
updates, 61
Administration portal
unable to view Past Activities, 18
Adobe Reader
corrupt text in bookmarks pane, 53
aggregates
minimum, 41
aggregate values in Transformer, 57
aggregating measures
limitations, 84
AIX
version, IBM WebSphere, 28
Analysis Studio
troubleshooting, 37
Analysis Studio quick tour, 66
Analysis Studio User Guide, 65
analyzing
metrics history, 76
ANS-MES-0007 errors, 36
application servers
problems running Cognos 8, 68
applying
filters to dimensional reports, 43
ASCII
requirements for installation directory, 31
as percentage
values, 19
AssignStaff stored procedure, 26
attributes
filters, 24
problems when pivoting lists to crosstabs, 35
B
BmtScriptPlayer
action logs, 25
bo heap Buffer Overflow error, 27
business keys
model query subjects, 24
C
c8transformerinstall.exe, 58
calculated column
converting to regular column, 58
calculated key figures, 50
calculations
SAP BW data sources, 48
changes to decimal formats, 33
character sets
Oracle mismatch and filters, 34
chart color
notes, 47
checkpoint bypass
-i command line option, 82
classes12.jar file, 68
client/server synchronization in Transformer, 91
cmm_support_bundle, 75
CM-SYS-5001 A Content Manager internal error
occurred, 53
Cognos 8
does not start on an application server, 68
integration with Cognos Planning, 52
Cognos 8 Go! Office
known issues, 27
Readme 95

Index
location of setup.exe file, 31
multiple logon prompts, 27
Cognos 8 service
does not start on WebSphere 5.1, 29
Cognos 8 Special Edition
cannot connect to Content Manager, 30
db2 not found, 29
DB2 Workgroup is not registered, 30
does not create application tier, 30
IBM WebSphere not found, 31
installation of WebSphere and IHS fails, 28
Cognos Connection
missing reports and folders, 54
validation error for portlet parameters, 17
Cognos Connection menus
blocked, 53
Cognos Connection User Guide
updates, 62, 63, 85
Cognos Metrics
adding to pages and dashboards, 63
Cognos Metrics portlets, 63
Cognos Planning
integration with Cognos 8, 52
Cognos portlets, 63
deploying to SharePoint Portal Server, 63
Cognos PowerCubes, 62
cogroot.link file, 68
command line options, 79
-c, 81
-h, 82
-i, 82
-n, 82
command line syntax in Transformer, 78
Compatibility folder
Metric Studio, 73
compressed PowerCubes in Transformer, 91
conformed dimensions
drill-through access, 63
corrupt text
Adobe Reader, 53
creating
calculated columns in Transformer, 58
crosstabs
incorrect running totals, 44
no data returned when same dimension used on both
edges, 49
troubleshooting, 37
cubes
compressed in Transformer, 91
secured, 92
cube update data, 19
custom formatting
not appearing for empty cells, 49
customized menu options in Transformer, 91
D
dashboards
adding metrics, 62
issues with shortcuts, 17
databases
Oracle character set mismatch, 34
data disappearing
SSAS 2005 cubes, 32
data files
large, 42
data sources
Cognos PowerCubes, 62
prompt support in Transformer, 77
unable to open a cube using 8.2 DB2 OLAP, 21
unable to open a cube using Essbase 7.1, 21
data source support in Transformer, 91
data source types
package or report, 78
DB2
incorrect average value, 48
incorrect count value, 48
DB2 data sources
problems accessing, 20
db2 not found
installation with Cognos 8 Special Edition fails, 29
DB2 OLAP
query failure using DB2 OLAP Server, 20
unable to open a cube using 8.2 DB2 OLAP, 21
DB2 OLAP library, 23
decimal formats
changes, 33
defining a calculation
example, 66
determinants
keys, 24
dimensional data sources
grouping by attributes, 84
96

Index
pivoting lists to crosstabs, 35
dimensionally modeled relational data sources
limitations when aggregating measures, 84
dimensions
overlapping named set levels, 37
disk space, 42
documentation
Administration and Security Guide, 61
Analysis Studio quick tour, 66
Analysis Studio User Guide, 65
Cognos Connection User Guide, 62, 63
Event Studio User Guide, 66
Framework Manager User Guide, 85
Installation and Configuration Guide, 68
Metric Studio User Guide, 69
Query Studio User Guide, 66
Report Studio Professional Authoring User
Guide, 83, 85
Transformer Man Page, 82
Transformer User Guide, 77
DPR-ERR-2065 errors, 36
DPR-ERR-2079 error, 52
drill-through access
conformed dimensions, 63
Drill Through Assistant secured function, 63
limitations, 17
PowerCube to DMR, 17
Drill Through Assistant
description, 63
E
email
watch lists, 65, 76
email notification
Metric Studio, 65, 76
environments
supported, 89
error cells
troubleshooting in reports, 84
errors
DPR-ERR-2079, 52
Essbase
cube sample, 61
incorrect average value, 48
incorrect count value, 48
Essbase 7.1
unable to open a cube, 21
Essbase changes, 34
Event Studio User Guide, 66
expressions
limited in Report Studio Express authoring mode, 42
externalize methods
IQD, 90
F
files
adding multiple IQD, 38
filter expressions
no data, 50
filtering
and Oracle character set mismatch, 34
missing data, 36
filters
applying to dimensional reports, 43
attributes, 24
for clauses
limitations when using in summary functions, 44
formats
changes to decimals, 33
form-based authentication
using SiteMinder, 27
Framework Manager
issues, 22
security filters change for SAP BW, 89
Framework Manager User Guide
documentation updates, 85
full outer joins
Oracle, 23
G
global filters
Cognos Metrics portlets, 62
grouped data items
troubleshooting, 83
grouping by attributes, 84
grouping columns
SAP BW data sources, 48
guidelines for reporting
Metric Studio, 74
Readme 97

Index
H
help
-h option in Transformer, 82
history charts
Metric Studio, 76
hyperlink buttons
errors in PDF reports, 47
I
IBM WebSphere
AIX version, 28
installation with Cognos 8 Special Edition fails, 28
version 5.1 and user interface in Cognos 8, 17
IBM WebSphere not found
installation with Cognos 8 Special Edition fails, 31
import settings
Metric Studio, 76
specify, 76
incorrect average value using DB2 or Essbase, 48
incorrect count value using DB2 or Essbase, 48
Informix Dynamic Server
supported environments, 89
Informix Red Brick Decision Server
supported environments, 89
installation
requirements for directory name, 31
Installation and Configuration Guide, 68
installation directory
problems after renaming or moving, 68
installing
Transformer, using an .exe file, 58
IQD externalize method, 90
IQD files
adding multiple, 38
J
Java virtual machine
crashes when importing deployment, 54
joins
Oracle, 23
K
key figures, 50
keys, 24
known issues
administration, 17
Analysis Studio, 19
Cognos 8 Go! Office, 27
Cognos 8 Transformer, 54
Cognos Connection, 20
DB2 data sources, 20
Event Studio, 26
Framework Manager, 22
general, 32
installation and configuration, 28
Metric Studio known issues, 38
Query Studio, 40
Report Studio, 40
SAP BW data sources, 48
security, 50
Series 7 integration, 52
software development kit, 27
L
languages
OLAP data sources, 19
limitations
drill-through access, 17
linked models
upgrading, 24
Linked Reports
Metric Studio, 73
list reports
grouping by attributes, 84
loading
DB2 OLAP library, 23
log files, 25
logon problems
Cognos 8 Go! Office, 27
SAP namespace, 50, 51
M
macro prompts, 22
measures
SAP BW data sources, 49
memory errors
using SSAS 2005 cubes, 46
menus
blocked in Cognos Connection, 53
98

Index
merging projects, 86
metadata query failure with DB2 OLAP server, 20
Metric Designer
known issues, 37
scorecard hierarchy, 38
scorecards, 38
metric functions
Metric Studio, 72
metric model
Metric Studio, 69
metrics
adding to pages and dashboards, 62
history, 76
Metric Studio
actions erroneously re-assigned, 40
additional columns in Project tab-delimited file, 66
cmm_uninstall script, 39
Compatibility folder, 73
email notification, 65, 76
errors, 39
failed reports, 38
filter expressions, 39
guidelines for reporting, 74
history charts, 76
import settings, 76
Linked Reports, 73
metric functions, 72
metric model, 69
model view, 72
presentation view, 71
source view, 72
SQL Server 2005 error, 40
Support Bundle, 75
Metric Studio Portlets, See Cognos Metrics
Metric Studio User Guide, 69
Microsoft
security patch causes server failure, 28
Microsoft Excel 2007 support in Transformer, 55
Microsoft Office, 27
Microsoft SharePoint Portal Server
deploying Cognos portlets, 63
migrating PowerPlay reports, 64
migration
not supported as search type in New Job wizard, 52
mimimum aggregates, 41
missing data when filtering, 36
missing reports and folders
Cognos Connection, 54
missing values in Transformer, 56
Model Advisor
false positive, 24
model query subjects
filters, 24
model view
Metric Studio, 72
Multi-page portlet
shortcut issues, 17
MUNs, prompts in DMR report packages, 57
N
named sets
nested or parallel sets overlapping, 37
namespaces
case-sensitive issues, 27
Nested list reports
does not run after upgrade, 83
nested reports
changes to SAP BW rules for set expression
evaluation, 45
nested sets
unexpected summary values, 43
Netscape
supported browsers, 89
notes
chart color, 47
nulls
included in count summaries, 48
nulls not shown, 22
null values
not appearing with SSAS 2005, 33
O
objects
remapping, 86
ojdbc14.jar file, 68
OLAP data sources
languages, 19
limitations when relational functions are used, 35
OLAP support, third party, 92
OLE automation, 90
Readme 99

Index
Oracle
driver file conflict, 68
filters and character set mismatch, 34
full outer joins, 23
nulls not shown, 22
order of transactions, 25
outer joins
Oracle, 23
P
package data source, 78
packages
publishing, 87
pages
adding metrics, 62
passwords
SAP namespace, 50
pcoptimizer utility, 57
performance issues
using SSAS 2005 cubes, 46
pivoting lists to crosstabs, 35
portlets, 63
ports
setting the maximum number for program use, 20
PowerCube packages
republishing, 54
PowerCubes
compressed in Transformer, 91
multiple hierarchies, 56
secured, 92
PowerPlay reports
migrating to Cognos 8, 64
presentation view
Metric Studio, 71
problems
SAP namespace, 51
problems accessing DB2 data sources, 20
problems accessing SAP BW data sources, 48
projects
merging, 86
read-only, 26
prompts
flickering, 47
macros, 22
prompts for MUNs in DMR report packages, 57
prompt support in Transformer, 77
prompt values for multiple queries, 57
publishing
packages, 87
PYI files in Transformer, 91
Q
queries
do not execute, 56
prompt values, 57
query calculations
nulls included in count summaries, 48
query failure with DB2 OLAP server, 20
Query Studio User Guide, 66
query subjects
unable to merge, 26
quick tours
documentation update, 66
R
ragged hierarchies
Report Studio, 45
read-only projects, 26
red x in data tree, 36
regular column
converting to calculated column, 58
relational data sources
limitations when aggregating measures, 84
relational functions
limitations when used with OLAP data sources, 35
relationships
keys, 24
remap objects, 86
report data source, 78
report data sources
prompt support in Transformer, 77
ReportNet 1.1 documentation updates
Framework Manager User Guide, 85
ReportNet 1.1 issues
Framework Manager issues, 22
reports
applying filters to dimensional reports, 43
flickering prompt controls, 47
limitations in Transformer, 56
limitations when relational functions used with
OLAP data sources, 35
100

Index
no data returned when same dimension used on both
edges of crosstab, 49
troubleshooting error cells produced, 84
Report Studio
Key Transformation validation level returns partial
information, 46
limitations when using for clauses in summary
functions, 44
limited expressions in Express authoring mode, 42
no data returned when same dimension used on both
edges of crosstab, 49
nulls included in count summaries, 48
OP-ERR-0231 invalid parameter error, 40
ragged hierarchies, 45
troubleshooting, 42, 47
unbalanced hierarchies, 45
unexpected summary values when using nested
sets, 43
Report Studio Professional Authoring User Guide, 83
repository connections, 22
republishing
Powercube packages, 54
requirements
installation directory, 31
resetting
system metrics, 64
running
scripts, 24
running totals
incorrect in crosstabs, 44
S
samples
Essbase cubes, 61
model names, 63
SAP
password policy, 50
SAP BW
filters, 24
key figures, 50
security filter change in Framework Manager, 89
set expression evaluation rules changes, 45
supported environments, 89
SAP BW data sources
calculations, 48
grouping columns, 48
measures, 49
problems accessing, 48
query calculations, 48
sectioning reports, 49
summary rows, 50
SAP namespace
logon problems, 50, 51
repeated prompts for authentication, 51
SAP NetWeaver Portal
supported environments, 89
scorecard
exclusion settings, 38
scorecard hierarchy
blank entries, 38
search
migration type search is not supported, 52
sectioning reports
SAP BW data sources, 49
secured functions
Drill Through Assistant, 63
secured PowerCubes, 92
security
filter change in Framework Manager for SAP
BW, 89
Microsoft update causes server failure, 28
problems logging on to an SAP namespace, 50
segmented models
upgrading, 24
servers
failing to start, 28
set expressions
changes to SAP BW rules, 45
sets
nested or parallel sets overlapping, 37
setup.exe file
location in Cognos 8 installation directory, 31
SharePoint Portal Server
deploying Cognos portlets, 63
shortcuts
dashboard issues, 17
unable to create, 26
SiteMinder
form-based authentication, 27
Solaris
JRE 1.5, 53
Readme 101

Index
source view
Metric Studio, 72
specify
import settings, 76
SQL Server 2005 error
Metric Studio, 40
SSAS 2005
data disappearing, 32
incorrect values for report layout functions, 35
incorrect values with scoped attribute hierarchies, 33
SSAS cubes
problems with very large dimensions, 34
star schemas
unable to create, 26
stored procedure
AssignStaff, 26
studios
Essbase changes, 34
summary functions
limitations when using for clauses, 44
summary rows
SAP BW data sources, 50
summary values
unexpected when using nested sets, 43
Sun ONE Directory Server
supported environments, 89
Support Bundle
Metric Studio, 75
supported environments, 89
syntax of macro prompts, 22
system metrics
resetting, 64
T
third-party data sources
8.2 DB2 OLAP, 21
Essbase 7.1, 21
third party OLAP support, 92
thresholds
applying to multiple entries, 64
total values
SAP BW data sources, 50
transaction history, 25
transaction history list, 25
transaction log files, 25
Transformer
.pyi files, 91
aggregate values, 57
client/server synchronization, 91
command line options, 79
command line syntax, 78
-c option, 81
creating calculated columns, 58
data source support, 91
data source types, 78
expression editor functions, 92
-h option, 82
installing from an .exe file, 58
-i option, 82
limitations on using reports, 56
menu customization, 91
Microsoft Excel 2007 support, 55
missing values, 56
-n option, 82
OLE automation, 90
pcoptimizer utility, 57
prompts for MUNs, 57
prompt support in report data sources, 77
prompt values for multiple queries, 57
queries against multiple hierarchies, 56
troubleshooting
Analysis Studio, 37
grouped data items in nested list reports, 83
pivoting lists to crosstabs, 35
Report Studio, 42, 47
U
unable to view HTML output, 53
unbalanced hierarchies
Report Studio, 45
unexpected results
crosstabs, 37
UNIX
BmtScriptPlayer, 25
UNIX/Linux processing
-c command line option, 81
unsupported Cognos Planning 7.3 features, 52
upgrading
Cognos 8 fails to start, 28
models, 24
segmented models, 24
102

Index
URLs
errors in PDF reports, 47
V
values
as percentage, 19
W
watch lists
email notification, 65, 76
web.config file
documentation error, 63
Weblogic 9.1.0
unable to view HTML output, 53
WebLogic Application Server
Cognos 8 fails, 53
WebSphere 5.1
Cognos 8 does not start, 29, 30
Windows processing
-n command line option, 82
Z
zeroes and Oracle, 22
Readme 103