rdm_cr

COGNOS (R) 8 BUSINESS INTELLIGENCE
README
Cognos 8 Readme
08-15-2005
Cognos 8
8.1
Cognos(R) 8 Business Intelligence Readme
README
THE NEXT LEVEL OF PERFORMANCE TM

Product Information
This document applies to Cognos (R) 8 Version 8.1 and may also apply to subsequent releases. To check for newer versions of this document,
visit the Cognos support Web site (http://support.cognos.com).
Copyright
Copyright (C) 2005 Cognos Incorporated.
Portions of Cognos(R) 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.
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
Cognos 8 Known Issues 9
Installation and Configuration 9
Unable to Load DB2 OLAP Library in Framework Manager 9
Accented or Double-Byte Characters May Not Display Correctly When Installing
Cognos 8 on Linux 9
Cannot Load Apache Module into Server When Using Cognos 8 and Cognos Series 7
Applications on the Same Web Server 10
Non-ASCII Characters in Install Directory Will Cause Run-Time Errors 10
Japanese Characters Corrupted When Running issetup 11
Yen and Won Characters Appear as Backslashes 11
Upgrading ReportNet 1.1 to Cognos 8 Using Oracle 10g Application Server 11
Cannot Publish Series 7 Cubes to Cognos 8 Following Upgrade 12
Choosing Only One Language When Installing Cognos 8 Transformer and
PowerPlay 13
Series 7 Integration 13
Publish to Cognos 8 Fails if a Different Format is Used to Identify the Series 7 Directory
Server 13
Unsupported Cognos Planning 7.3 Features with Cognos 8 13
Cannot Open PowerPlay 7 Reports Published to Cognos Connection 13
Transformer Errors Using Excel Data Sources on Windows 2000 SP4 14
Security 14
Issues with Integrated Windows Authentication 14
A Namespace Configured with LDAP SSL Is Not Available 14
Error When Using the SDK Custom Authentication JDBC Provider Sample 14
Charts do Not Appear When Internet Explorer 6.x Security Level Set to High 15
Testing SQL Server Datasource Connection When Using External Namespace
Authentication 15
Administration 15
Unable to Connect to a Cognos Planning - Contributor Data Source 15
Index Update Options Appear When Selecting Default Options For a Job 16
A Report Does Not Run as Scheduled 16
General 16
CMM Strategy Maps Not Rendered to Excel 16
Problems When Printing PDF 16
Text Does Not Appear Properly in Quick Tours 17
Documentation CD not Included in the Cognos 8 Package 17
Broken Links in Documentation 17
Unable to Launch Toolbar Buttons in Cognos Viewer When Using Jaws Screen Reading
Software 17
Drill-Through Performance Slower 17
Adobe Reader Versions for Server Printing on Windows 17
Server Printing on AIX 17
DB2 Data Sources 18
Query Fails When Using DB2 OLAP Server 18
Unable to Open a Cube Using 8.2 DB2 OLAP or EssBase 7.1 18
Incorrect Average Value if Using DB2 OLAP/Essbase 19
Incorrect Count Value if Using DB2 OLAP/Essbase 19
Member Attributes Are not Supported for DB2 OLAP/Essbase 19
SAP BW Data Sources 19
Readme 3

4
Incorrect Units of Measure in Calculations 19
Grouping Columns That Have the Count Summary 19
Missing Measures in Crosstab Reports 19
Custom Formatting for Empty Cells Does Not Appear in Cognos 8 20
Default Value Is Not Highlighted for SAP BW Hierarchy Node Prompt 20
Creating Sections on Reports That Access SAP BW Data Sources 20
Calculation Displays Incorrect Unit Format 20
Summary Rows Return Incorrect Total Values 20
Calculated Key Figures Appear with the Non-Aggregate Icon 20
Query Studio 21
Limitation Using Custom Groups and Drill Down Features in Query Studio 21
Cannot Use Hierarchies from Dimensionally Modeled Relational Models 21
Text and Border Styles Are not Applied to Empty Reports 21
Unable to Run a Report After Cognos 8 is Restarted 21
Background Color Is not Applied to Empty Crosstab Cells 21
Functions not Available 21
Unable to Insert Data Items from Two Hierarchies of a Single Dimension 21
Background Color in Template Does not Appear 22
Drilling on Measures 22
Grouping on an Attribute 22
Subtotals in Grouped Lists 22
Adding a Filter to a Crosstab with a Currency and a Calculation 22
Filters May Not Work in Some Sectioned Reports 22
Unable to Filter on Multiple Currencies at Once 22
Summary Values of Non-additive Measures May Be Incorrect 23
Report Studio 23
Style Properties not Supported 23
Bursting on MOLAP Data 23
Aggregate Values Are Not Appearing in Crosstabs 23
Connecting Queries Between Different Data Sources 23
Creating a Chart from an Existing Query 24
Key Transformation Validation Level Returns Partial Information 24
Extra Rows Appear in a Grouped List 24
Pivoting to a Crosstab Shows the Member of the Attribute 24
Event Studio 24
Tasks Do Not Run According to Execution Rules 25
Agent Run Fails 25
Analysis Studio 25
Analysis Studio Limitations 25
Filter by Label or Attribute is Case Sensitive 25
Cells with '- -' are Represented as NULLS in Export to Excel 26
Context Filter Limitations 26
Defining Languages for OLAP Data Sources 26
Crosstab Shows Percentage But Chart Shows Values 26
Analysis Studio Does Not Reflect Package Configuration Settings 26
Analysis Studio Ignores Changed Package Reference in Cognos Connection 26
Server Error When Sorting a Selection-Based Set by Attribute 26
Suppress Items when Accessing MS Analysis Services Cubes May Produce Unexpected
Results 26
Metric Studio 27
Default Import Source Expects a Folder in the Deployment Directory 27
Test Data Source in Cognos Connection Fails for Security Reasons 27
Recommended Patches for Oracle 10g 27
"To-Date" Comparisons are Not Available 27
Concurrent Tasks May Corrupt Metric Store 27
Oracle 9.2 Package Initialization Error if NLS_LANG Environment Variable is Not Set
Appropriately Before Starting Up Cognos 8 Tomcat Server 27

User Permissions for the Metric Store Database (MS SQL Server) 28
Metric Type Settings Lost When a Calendar is Cleared 28
Equations Using Only Constants are not Allowed in Calculated Metrics Types 28
Default Report and Diagram Setting not Exported 28
When Migrating a CMM 2.2 Application With Translated Units to Metric Studio 8.1,
Metric Values are not Migrated 28
Data Format for Specifying Security on Groups and Group Types has Changed 29
Group-type Names Display as Unreadable Characters (SQL Server Only) 29
Multilingual Characters May not Print Correctly When Using an Oracle Metric Store 29
Imports and Exports May Fail in a Distributed Installation 29
Content that uses double-byte characters displays as unreadable characters (Oracle) 29
Removing Periods From a Calendar That Contains Weeks May Remove the First Week of
the First Remaining Year 30
Errors During the Import of a Custom Calendar Are Not Shown in the Calendar Creation
Wizard 30
Oracle Database Created but Not Configured as Expected 30
Unexpected Date Format in the User Interface 30
Initializing an Oracle Metric Store Which Does Not Have the NLS_LANG Environment
Variable Set Properly Has Unexpected Results 30
Some Characters Cannot Be Loaded When the Database Has a Non Unicode Dataset 31
Extending a Calendar That Has No Year-Level Fails If the Number of Periods of the
Initial Calendar Contains a Partial Year 31
Calculation Fails When the Decimal Period Is Not a Period 31
The start_time_cd and created_dt Columns of the .cmn Tab-Delimited File Must Be
Formatted as yyyy-mm-dd hh:mm:ss (DB2) 31
Imports and Exports May Fail in a Distributed Installation 31
Printing a List of Scorecard Projects or Metric Actions Can Result in an Empty List 32
Calendars Including Weeks Contain More Years and Start One Year Earlier than
Expected 32
Metric Lists Do Not Display When Using DB2 32
Non-Integer Values Using a Character Other Than a Period as the Decimal Point Are Not
Imported When Using DB2 32
When Running the Metric Maintenance Task, Clear Metric History and Calendar Data,
Some Calendar Properties May Be Lost 33
Data Removed From Metric Data Store 33
List View Displays Incorrect Week 33
Metric Designer 33
Metric Designer Does not Warn the User if the Metrics Extract Mapping do not Match
the Metric Type Rollup Properties 34
Error UDA-SQL-0564 When Executing a Notes Object Extract 34
Metric Type Settings Lost When a Calendar is Cleared 34
Framework Manager - Import Source and Anonymous User Language Preference 34
Framework Manager - Import Source Connections and Credentials 34
Metric Designer delivers unreadable values from Japanese Microsoft SQL Server Import
Sources when writing to files 34
Japanese Extracts to Oracle via Metric Studio Staging files Fails 35
Cognos 8 Package Import Source - "No Accessible Views" Error 35
Create Date Field for Object Extracts 35
Metric Filters are Still Invalid After Upgrading a Model and Retargeting Broken
References 35
Unrecognized Vendor-Defined Japanese Characters in Cube Extracts 35
Problem Trying to Execute an Extract Created Against a Framework Manager Model
Going Against a Teradata Database 35
IQD Import Source - Error Reading IQD file that Contains the Oracle 'Replace'
Function 36
Adding Multiple IQD files to an Import Source 36
Data Sources Not Supported 36
Readme 5

Incorrect Scorecard Rollup Values for PowerCube Expressions 36
Previewing the Scorecard Tree and Assigning Metrics to Scorecards in the Metrics Scope
page does not work 37
Filters on Parent-Child Hierarchies are not Supported for Dimensional (OLAP) Data
sources 37
Error Occurs for a Metrics Extract Containing Static Text-type Scorecard Levels 37
Metric Extracts Containing Typed-in Constant Metric Attribute Values Do Not Deliver
Metrics for PowerCube Data Sources 37
Mapping Levels to Qualifiers Using the Expression Editor for a PowerCube Data Source
Does Not Work 37
Error Occurs When Query Items Mapped to Metrics Qualifiers Are Referenced in
Scorecard Filters 37
Framework Manager 38
Unable to Test Physical Model after Third-Party Metadata Import 38
Invalid Expressions after Third-Party Metadata Import from DB2 Cube Views 38
Levels in IBM DB2 Cube Views Are Not Assigned a Role of memberCaption 39
Functional Dependencies in IBM DB2 Cube Views Are Not Defined as Determinants 39
Occasional Session Issues When Testing Queries in Framework Manager 39
Embedded Externalize Method 39
Unable to Use an IQD Created in Framework Manager That Contains an Oracle Stored
Procedure 39
Problems Arising When an IQD File Exported from Framework Manager Connects to
Two Databases 40
Cannot Specify the Order of Members 40
Full Outer Joins and Oracle 40
Upgraded Report Does Not Run Due to Incompatible Datatype 41
Cannot Synchronize a Project in a Repository 41
Errors Using Non-English Version of Visual SourceSafe 6.0 41
Unable to Start Framework Manager 41
Cognos 8 Documentation Updates 43
Cognos 8 Getting Started 43
Example - Monitor Performance 43
Example - Manage an Event 43
Cognos 8 Troubleshooting Guide 43
Application Error Appears When Upgrading a Report 43
Log Files 44
Mixed Languages Are Displayed in Cognos Connection When Using Samples 44
Not Yet Optimized Cognos PowerCubes May Open Slowly in Cognos 8 44
Failed to Execute Step step_name in Package package_name Because a Conflicting
Process is Already Running. Please Try Again Later. 45
Failed to Unlock the Database After Executing Step step_name in Package package_name.
Please Contact Your System Administrator. 45
Failed to Release Old Database Locks Where DIS ID Is: dispatcher 46
QE-DEF-0177, UDA-SQL-0114, UDA-SQL-0458, and UDA-SQL-0475 Errors When
Running a Report 46
Series 7 Namespaces Do Not Initialize When Services are Started 46
Cognos 8 Installation & Configuration Guide 47
Create Databases for the Content Store and Metric Store 47
Cognos 8 Administration and Security Guide 47
Setting Up Trigger-based Scheduling 47
DB2 OLAP Data Sources and Scenario Dimensions 48
Balanced Hierarchies Not Determined by DB2 OLAP Provider 48
Specify Measure Formats 48
Cognos 8 Report Studio User Guide 49
Controlling the Rows Per Page for Multiple Containers in HTML and PDF 49
Creating Charts Using an SAP BW Data Source 50
6

Creating Burst Reports Using a Dimensional Data Source 50
Using the Expression Editor 50
Cannot View Burst Report 51
Cognos 8 Query Studio User Guide 52
Format Rules for Calculations Returning Number Data Types 52
SAP BW 54
Create a Simple Filter 54
Cognos 8 Analysis Studio User Guide 54
Insert Data 54
Suppress Null Totals and Zero Totals 54
Create a Custom Set 55
Producing Reports in Microsoft Excel Format 55
Insert Data 56
Sets 56
Cognos 8 Metric Studio User Guide for Authors 56
Weeks in Gregorian Calendars 56
Framework Manager User Guide 57
Checking Imported Metadata 57
Moving a Framework Manager Model from One Relational Database to Another 57
Analysis Studio Quick Tour 58
Index 59
Readme 7

Cognos 8 Known Issues
This Readme contains late-breaking information, including
• known issues
• documentation updates
The documentation included in this release is current as of November 11, 2005. To view
subsequently discovered issues and documentation updates, visit the Knowledge Base on the
Cognos support Web site (http://support.cognos.com/kb-app/knowledgebase).
From within the online help, you can click the following link to open a printable version of this
document (PDF).
To view a complete list of environments currently supported by Cognos products, such as
operating systems, patches, browsers, Web servers, directory servers, and database servers, visit
the Cognos support Web site (http://support.cognos.com).
Installation and Configuration
This section contains known issues about installation and configuration.
Unable to Load DB2 OLAP Library in Framework Manager
You installed the DB2 OLAP 8.1 client and cannot load the DB2 OLAP library into Framework
Manager. You receive the following message:
DB2-ERR-0028 Unable to load the following DB2 OLAP library:
"C:\ibm\db2olap\bin\essapin.dll"
Cognos 8 is configured to use the DB2 OLAP library for Version 8.2. To resolve this problem, you
must edit the qfs_config.xml file and rename the library for Version 8.1.
nbna
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 doodp82 to doodp81 and save the changes.
Accented or Double-Byte Characters May Not Display Correctly When
Installing Cognos 8 on Linux
If you are using issetup under a UTF-8 locale, accented or double-byte characters may not display
correctly.
To resolve this problem when installing in German or French, use a non-UTF-8 locale and then
launch issetup or use the character-mode program issetupcc to install Cognos 8.
To resolve this problem when installing in Japanese, use the character-mode program issetupcc
and change the encoding setting of X Terminal to Shift-JIS, then install Cognos 8.
Readme 9

Cognos 8 Known Issues
Cannot Load Apache Module into Server When Using Cognos 8 and Cognos
Series 7 Applications on the Same Web Server
When configuring an Apache gateway for Cognos 8 on a Web server that is also being used for
Cognos Series 7 applications, the Web server may not start. You may see a message similar to the
following:
Syntax error on line 557 of //webserver/IHS_###/conf/httpd.conf:
Cannot load /usr/cognos/cgi-bin/imrapmod.so into server: Exec format error
In your Web browser, you may see the following message:
500 Internal Server Error in the browser:
The server encountered an internal error or misconfiguration and was unable to
complete your request.
Please contact the server administrator, name@company.address and inform them
of the time the error occurred, and anything you might have done that may have
caused the error. More information about this error may be available in the
server error log.
The problem occurs because of incompatibilities between shared libraries used by the two gateway
modules. Both gateway modules are loaded by one process, Apache Web server. A single Apache
Web server cannot load both the Cognos 8 and version 7.3 application modules.
To resolve this problem, upgrade your Cognos Series 7 applications to version 7.3 MR2 or higher,
or run each gateway module in a separate Apache process using the method described below.
For example, configure the first instance of Apache as the proxy server and to load mod_cognos
for Cognos 8. Configure the second instance to run the Cognos Series 7 gateway module.
446124
Steps
1. Enable mod_proxy on the original Apache Web Server.
This server becomes the proxy server.
2. Install and configure a second instance of Apache on a different port.
3. On the original server, do the following:
• Remove any existing Cognos Series 7 configuration information from the httpd.conf file
and then add the following information:
LoadModule proxy_module modules/mod_proxy.so # modify to suit platform
ProxyPass http://hostname:port/cognos/cgi-bin/imrapmod
• Edit the Apache envvars file and ensure that c8/cgi-bin appears before the cer4/bin and
cer4/cgi-bin directories in the shared library search path.
4. On the second server, do the following:
• Configure the Apache module gateway settings that are required for Cognos Series 7.
For more information, see the Change the Apache Web Server Settings for Apache
Module Gateways topic in Configuration Manager User Guide.
• Configure the server to use the same port as the one specified in the ProxyPass line in step
3.
• Edit the Apache envvars file and ensure that c8/cgi-bin is not in the shared library search
path.
Non-ASCII Characters in Install Directory Will Cause Run-Time Errors
The use of non-ASCII characters in the name of the Cognos 8 installation directory will cause
run-time errors. Some product functions, particularly report execution, will fail.
To resolve this issue, use the default installation directory, \Program Files\cognos\c8, or use an
alternate installation directory name which uses ASCII characters.
10

Cognos 8 Known Issues
483217
Japanese Characters Corrupted When Running issetup
487002
If you run issetup from an X Windows client running on a Microsoft Windows computer,
Japanese characters may be corrupted.
To work around this problem, follow these steps:
1. When you install Cognos 8 on a UNIX computer, open the console display.
2. Type LANG=C and LC_ALL=C to specify English only for the installation.
Yen and Won Characters Appear as Backslashes
In the Unicode standard map, the character stored as U+005C appears as a backslash. The yen and
won characters are stored as U+00A5 and U+20A9 respectively. However, adherence to the standard
is not universal and the U+005C storage value is often used for the yen symbol in Japan and as the
won symbol in Korea.
The appearance of character symbols depends on the font used. If you want to use U+005C as a
yen or a won, change the font. In HTML and PDF output, the cascading style sheet file
GlobalReportStyles.css controls which font is used and it is stored in the folders \Cognos\c8\bin\
and \Cognos\c8\webcontent\schemas\.
Cognos provides a standard default font, Andale WT, which uses the standard Unicode map for
U+005C as backslash. Cognos also provides Andale WT J and Andale WT K, that map the U+005C
value as a yen and a won respectively. You can download these fonts from the Cognos support
Web site (http://support.cognos.com). To use the fonts, copy them to \Cognos\c8\bin\fonts\ (or the
path set by Cognos Configuration) and then follow the steps below to modify the style sheet.
1. Stop the Cognos 8 server.
2. Enable one of the following sections as below:
/* For Japanese: */
.pg,
.pp
{
font-family: 'MS UI Gothic', Tahoma, arial, geneva, helvetica,
sans-serif, 'Andale WT J';
}
Or
nbna
/* For Korean: */
.pg,
.pp
{
font-family: Gulim, Tahoma, arial, geneva, helvetica, sans-serif,
'Andale WT K';
}
3. Restart the Cognos 8 server.
Upgrading ReportNet 1.1 to Cognos 8 Using Oracle 10g Application Server
When you deploy Cognos 8 using the Oracle 10g application server, the Cognos 8 application
code is run during the deployment step and then stopped automatically by Oracle. This may result
in a partial update of the Content Manager data store. When a user attempts to access the portal,
the following error message appears:
There are no tabs available in your portal.
This problem does not occur in a non-application server environment, or with other application
servers.
Readme 11

Cognos 8 Known Issues
489870
To avoid this issue, do the following:
1. Configure the Cognos 8 Content Manager database to point to a new database before you
deploy Cognos 8.
2. Complete the installation and verify that the portal can be accessed.
At this point, there is no content in the portal.
3. Stop the Oracle OC4J instance.
4. Run Cognos Configuration and specify the ReportNet 1.1 Content Manager database.
5. Start the Oracle OC4J instance.
The Content Manager data store is properly updated.
Cannot Publish Series 7 Cubes to Cognos 8 Following Upgrade
After you upgrade from Cognos ReportNet to Cognos 8 you may not be able to publish cubes
from PowerPlay Enterprise Server to Cognos Connection. Similarly, if a user opens a cube from
Cognos Connection that was published from PowerPlay Enterprise Server, they may receive the
following error when they save the report to Cognos Connection: "Your session ticket is invalid. It
may have expired."
To resolve this problem, you can restructure your virtual directories so that the Series 7 and
Cognos 8 gateways are within the same structure or change the default cookie path in Cognos 8.
If you change the cookie path, you will not be able to run ReportNet and Cognos 8 on the same
computer.
Steps to Set the Virtual Directories
• Create a virtual directory structure such that both the PowerPlay Enterprise Server Series 7
gateway and the Cognos 8 gateway are within the same structure. For example, set up your
virtual directories such as
• Create an alias called cognos8 that points to the c8_location\webcontent directory.
• Create an alias called cognos8/cgi-bin that points to the c8_location\cgi-bin directory.
• Create an alias called cognos8/series7 that points to the series7_location\webcontent
directory.
• Create an alias called cognos8/series7/cgi-bin that points to the series7_location\cgi-bin
directory.
• Create an alias called cognos8/series7/help that points to the
series7_location\Documentation directory.
497254, 498533
Steps to Change the Default Cookie Path
1. Start Cognos Configuration.
2. Click Actions, Edit Global Configuration, and click the Server tab.
3. In the Path box under Cookie Setting, type
/
4. Click OK.
5. Save your configuration.
Note: If you change the cookie path, you will not be able to run ReportNet and Cognos 8 on the
same computer. If you intend to run ReportNet and Cognos 8 on the same computer, you can
correct this problem by changing your virtual directories as described above.
12

Cognos 8 Known Issues
Choosing Only One Language When Installing Cognos 8 Transformer and
PowerPlay
The Cognos 8 BI OLAP Modeling and Mobile Analysis packages are delivered on multiple CDs.
Each CD is organized into two or more top-level language folders such as English, French, and
Japanese. When installing these products, you must install them from one of the available
language folders.
The language that you choose becomes the language of the user interface of the product. However,
the product can process data in any of the supported languages.
Series 7 Integration
This section contains known issues about Series 7 integration.
Publish to Cognos 8 Fails if a Different Format is Used to Identify the Series 7
Directory Server
452195
To publish from PowerPlay Enterprise Server to Cognos 8, you must use the same format to
identify the connection information for the Series 7 namespace directory server in both Cognos
Series 7 Version 3 and Cognos 8.
For example, if you specify a host name in one product and then use the IP address in the other,
PowerPlay Enterprise Server is not able to publish to the Cognos 8 portal. Instead, it detects a
mismatched configuration, prompts for credentials and, even if valid credentials are entered, raises
a "Publish failed" error.
The solution is to use the same format to identify the directory server hosting the Cognos Series 7
namespace in both product configurations; either a fully qualified host name or a specific IP
address.
Unsupported Cognos Planning 7.3 Features with Cognos 8
nbna
The following Planning - Contributor 7.3 features are unsupported with Cognos 8.
• Publish to PowerPlay Enterprise Server admin extension - All unpublished data source
tasks
• Publish to PowerPlay Enterprise Server admin extension - Published data source task
"Create PowerCubes and Publish to PowerPlay Enterprise Server"
• Publish to PowerPlay Enterprise Server admin extension - Published data source task
"Publish PowerCubes to a Cognos Portal"
• Publish to Cognos Metrics Manager admin extension
• View in PowerPlay Web client extension
Cannot Open PowerPlay 7 Reports Published to Cognos Connection
nbna
In Cognos Connection, if you try to open published PowerPlay 7 reports in Report Studio or
Analysis Studio, you receive an error message.
You must upgrade PowerPlay 7 reports before you can open them in Cognos 8. This upgrade
functionality was not available when you installed Cognos 8. To determine if the upgrade
functionality is available, contact Cognos Customer Support.
Readme 13

Cognos 8 Known Issues
Transformer Errors Using Excel Data Sources on Windows 2000 SP4
501142, 501165
Security
Importing an Excel crosstab into Transformer can cause errors in Transformer if you have
Microsoft Data Access Components (MDAC) version 2.8 SP1 installed and you are using a
Windows 2000 SP4 computer.
Also, opening the data source viewer for an Excel data source can cause errors in Transformer if
you have MDAC version 2.6 to 2.8 installed and you are using a Windows 2000 SP4 computer.
This section contains known issues about security.
Issues with Integrated Windows Authentication
The single signon mechanism does not work when Cognos 8 is configured as follows:
• Microsoft Internet Explorer runs on a Windows NT computer.
• The authentication namespace is configured with the Active Directory provider.
• Microsoft Internet Explorer on a Windows 2000 or Windows 2003 server is configured for
Integrated Windows Authentication.
As a result, users are prompted for their Active Directory credentials.
This problem occurs because the Cognos 8 Active Directory provider uses ADSI protocol and
Kerberos delegation for authentication in a single signon environment. When Microsoft Internet
Explorer runs on Windows NT, it cannot authenticate to the IIS server using Kerberos delegation.
When your system is configured for Windows Integrated Authentication, for the single signon to
work with IIS, you must
• configure Cognos 8 to communicate with the Active Directory server using the LDAP
provider.
• configure the external identity mapping property to read the REMOTE_USER environment
variable.
A Namespace Configured with LDAP SSL Is Not Available
When you use an LDAP namespace and you have SSL configured for communication with the
directory server, the namespace may not be available when you start Cognos 8.
This problem occurs if the directory that contains the cert7.db file does not contain the key3.db
file. The key3.db file is required by the LDAP SDK version used with the current version of
ReportNet.
To avoid this problem, ensure that the key3.db and cert7.db files are in the same directory.
Error When Using the SDK Custom Authentication JDBC Provider Sample
When you want to use the sample, a run-time error occurs because the JDBC drivers for SQL
Server are not available.
To solve this problem, perform the following steps.
Steps
1. Install the JDBC drivers.
The drivers are available on the Microsoft Web site.
2. Copy the following files from the jdbc_driver_installation/lib directory to the
c8_installation/webapps/p2pd/WEB-INF/lib directory:
• msbase.jar
• mssqlserver.jar
14

Cognos 8 Known Issues
• msutil.jar
Charts do Not Appear When Internet Explorer 6.x Security Level Set to High
In Cognos 8, HTML output reports are displayed in Microsoft Internet Explorer 6.x with 24-bit
transparency to ensure that the appropriate color depth is displayed, typically for charts.
If you operate in an environment that requires the Internet Explorer 6.x security level to be set to
high, charts may not appear. If you cannot lower the security setting for security reasons, you may
want to disable chart transparency. Charts are displayed in Internet Explorer with transparencies
displayed in white.
To access the server administration tool, you must have execute permissions for the server
administration secured feature and traverse permission for the Administration secured function.
For more information, see "Securing Functions and Features" in the Administration and Security
Guide.
nbna
Steps
1. In Cognos Connection, click Tools, Server Administration.
2. Click the Configure tab.
3. In the Name column, click the dispatcher you want.
4. For ReportService, in the Actions column, click the set properties button.
5. Click the Settings tab.
6. For the Environment category, next to Advanced settings, click the Edit link.
7. If it appears, select the Override the settings acquired from the parent entry check box.
Otherwise, proceed to the next step.
8. In the Parameter column, type EnableChartTransparencyIE.
9. In the Value column, type False to disable chart transparency in Internet Explorer.
10. Click OK.
11. Click OK again.
Testing SQL Server Datasource Connection When Using External Namespace
Authentication
490323
After you create a datasource connection to SQL Server or SQL Server Analysis Services and select
an external namespace for authentication, testing the connection will always result in the
"RSV-SRV-0040 An application error has occurred" error. However, the connection may work
correctly.
To resolve this problem, you can confirm that the data source connection is valid using
Framework Manager to import metadata or using one of the studios to query it.
Administration
This section contains known issues about administration.
Unable to Connect to a Cognos Planning - Contributor Data Source
Attempting to connect to a Cognos Planning - Contributor Data Source may result in a failed
connection test or you may see a message similar to the following:
A socket reported a communication error
To successfully connect to a Cognos Planning - Contributor data source requires the installation of
Cognos Planning 7.3 Service Pack 3 and the Cognos 8 - Integration Install, with the Cognos 8 -
Contributor Data Server selected.
Readme 15

Cognos 8 Known Issues
475844
These installation kits will be available as a download from the Cognos support website
http://support.cognos.com
Index Update Options Appear When Selecting Default Options For a Job
500328
When you are setting the default options for a job that schedules multiple entries, the option Index
update options that appears is not functional. Settings that you choose for this option will not
cause errors, but they will be ignored. These settings will be relevant in a future release.
A Report Does Not Run as Scheduled
481534
General
If you remove an authentication namespace from Cognos Configuration, a report may not run as
scheduled if the owner’s stored credential included authentication for the deleted namespace.
To correct this problem, refresh the owner’s stored credentials.
Tip: Click Preferences, click the Personal tab, and then click Renew the credentials .
This section contains general known issues.
CMM Strategy Maps Not Rendered to Excel
nbna
Due to issues with Microsoft Excel support for images in spreadsheets, Metric Studio strategy
maps will not appear in reports saved to Microsoft Excel format.
Problems When Printing PDF
You print a document in PDF format, but the print job is incomplete. For example, the job stops
printing when it reaches a particular graphic.
This is an Adobe Reader issue that can occur when printing some PDFs using some versions of
Adobe Reader and some printer models. The same PDF may print correctly under one or both of
the following conditions:
• using a different version of Adobe Reader
• using a different printer
If you print from Adobe Reader 4.0 or later product, you can try the following solution.
Steps to Force a Page to Print as an Image
1. In Adobe Reader, from the File menu, click Print.
2. In the Print dialog box, click Advanced.
3. In the Advanced Print Setup dialog box, select the Print as image check box.
Because files print more slowly using this option, make sure you specify only the non-printing
page.
4. In the Print Range section, click Pages from and Pages to, type only the page number of the
non-printing page, and then click OK.
You can print the rest of the PDF by resending the job starting on the next page.
5. Clear the Print as image check box.
6. In the Print Range section, click Pages from and Pages to, type the page range for the
remaining pages, and then click OK.
Although you can use the Print as image option to print the file, this setting does not resolve the
original printing problem. For more information, see the Adobe Web site.
16

Cognos 8 Known Issues
nbna
Text Does Not Appear Properly in Quick Tours
471519
If your computer uses large fonts, you may not see all the text or text may not wrap properly in
the Cognos 8 quick tours. To fix this problem, do one of the following:
• Use small fonts for your computer.
• Use the smallest font setting in your Web browser.
Documentation CD not Included in the Cognos 8 Package
Cognos 8 documentation states that "All online books are available on the Cognos
documentation CD". However, in an effort to reduce the total number of CDs, we have removed
this redundant content.
nbna
All Cognos 8 online books continue to be available in the
c8_location\webcontent\documentation\en directory.
Broken Links in Documentation
nbna
In the HTML output of the Cognos 8 documentation, links to other documents in the
Introduction chapters may be broken. Broken links occur if a component of Cognos 8 was not
installed.
Unable to Launch Toolbar Buttons in Cognos Viewer When Using Jaws Screen
Reading Software
Users of Jaws screen reading software are able to navigate to the toolbar buttons and hear a
description of each button when viewing a report in Cognos Viewer. However they cannot launch
any of the buttons.
The toolbar buttons in Report Viewer can be accessed via keyboard navigation when the screen
reader is disabled.
Drill-Through Performance Slower
493659
Drill-through performance in Cognos 8 may be slower than in ReportNet for the same reports.
Adobe Reader Versions for Server Printing on Windows
Due to an issue with earlier versions of Adobe Reader 7.x, Cognos 8 on Windows requires Adobe
Reader 7.0.5 or higher for server printing. Alternatively, Adobe 5.0.5 or 6.x may also be used.
492030
Note that this issue does not affect the use of Adobe Reader 7 in the browser for viewing or
printing.
Server Printing on AIX
500409
Server-side printing on AIX may produce the following error message, despite the fact that the
report was printed successfully.
RSV-DST-0009 The print process returned a status code of 999
You can ignore this error message, as the document was printed successfully.
Readme 17

Cognos 8 Known Issues
DB2 Data Sources
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 using data or metadata in a DB2 OLAP server, you may see an exception
window indicating that something wrong happened with the query.
The error occurred because Windows did not have enough remote procedure call (RPC) ports
available.
To resolve this problem, you must increase the number of RPC ports that are available for
program use. You do this by creating a MaxUserPort TCP/IP entry in the Registry Editor.
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.
476181
Steps
1. From the Start menu, click Run.
2. In the Run dialog, 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.
6. Double-click MaxUserPort.
7. In the Edit DWORD Value window, do the following:
• Select Decimal.
• Type a value between 30000 and 65534.
Tip: The maximum value, 65534, is recommended.
• Click OK.
8. Close the Registry Editor window.
9. Restart the Microsoft CRM server.
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.
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.
18

Cognos 8 Known Issues
483570
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.
Incorrect Average Value if Using DB2 OLAP/Essbase
500534
If you are using DB2 OLAP/Essbase, you may obtain an incorrect value for an average in a
grouped list report with a parent-child hierarchy. This is a known issue that will be addressed in a
future release.
Incorrect Count Value if Using DB2 OLAP/Essbase
483788
If you are using DB2 OLAP/Essbase, you may obtain an incorrect value for a count summary in a
grouped list report. This is because the count for a root member is set to the sum of count values
for its descendants. This is a known issue that will be addressed in a future release.
Member Attributes Are not Supported for DB2 OLAP/Essbase
These attributes will not be available for filtering and grouping in the Cognos 8 studios in this
release.
There is no workaround for this problem.
SAP BW Data Sources
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.
Incorrect Units of Measure in Calculations
421591
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.
You can change the format of the corresponding column to obtain the desired unit of measure.
Grouping Columns That Have the Count Summary
435017
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.
Missing Measures in Crosstab Reports
437751
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.
Readme 19

Cognos 8 Known Issues
Custom Formatting for Empty Cells Does Not Appear in Cognos 8
425064
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 using Cognos 8.
Default Value Is Not Highlighted for SAP BW Hierarchy Node Prompt
401113
The hierarchy node variable is a placeholder that takes the place of a member in a hierarchical
tree. It is created with a default value. SAP BW may not return the correct default value for the
hierarchical node variable.
If a report uses a hierarchy node variable, the variable appears on the prompt page when you run
the report in Cognos Report Studio or Query Studio, but the default value is not highlighted.
Creating Sections on Reports That Access SAP BW Data Sources
443696
437613
SAP BW data sources may have problems with sections in reports under the following
circumstances:
• using a lowest-level query item that represents an SAP BW hierarchy containing ragged paths
as the section
If a section in a report uses the lowest-level query item in a ragged hierarchy in an SAP BW
data source (for example, the children of the "not assigned" node), you may receive this BAPI
error:
BAPI error occurred in function module BAPI_MDDATASET_SELECT_DATA. Value
for characteristic unknown
The solution is to remove the section from the lowest-level query item.
• using several multicubes with SAP variables
If you create a section in a report using conformed multicubes with SAP variables, you may
receive an SAP error message.
The solution is to use one multicube when creating sections in reports.
Calculation Displays Incorrect Unit Format
421591, 494230
When using an SAP BW data source, Cognos 8 does not correctly display the derived unit for
calculated measures. This occurs because SAP does not return the correct unit format for the
calculated measure, which is processed at runtime.
Summary Rows Return Incorrect Total Values
409532
When the rollup of the measure is a minimum, summary rows return incorrect total values.
Calculated Key Figures Appear with the Non-Aggregate Icon
nbna
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.
20

Cognos 8 Known Issues
Query Studio
This section contains known issues about Query Studio.
Limitation Using Custom Groups and Drill Down Features in Query Studio
483201
You cannot drill down on an object that has a custom group defined.
Cannot Use Hierarchies from Dimensionally Modeled Relational Models
nbna
When working with a dimensionally modeled relational model, you cannot insert hierarchies in a
report.
Text and Border Styles Are not Applied to Empty Reports
463562
If you specify text styles or border styles for an empty report, the styles are not applied. If you
subsequently add a column to the report, the column will not have the styles you specified.
Unable to Run a Report After Cognos 8 is Restarted
470873
If Cognos 8 is restarted while you are working in Query Studio or Report Studio, you will not be
able to continue to work or run the report, and an error will appear.
To resume working, close the browser and relaunch Query Studio or Report Studio.
Tip: If you are working in Report Studio and you made changes since you last saved the report,
you can preserve your changes by copying the report specification to the clipboard using the Copy
to Clipboard command in the Tools menu. When you restart Report Studio, use the Open Report
from Clipboard command in the same menu to open the report.
Background Color Is not Applied to Empty Crosstab Cells
478777
When applying a background color to cells in a crosstab, the color is not applied to cells that are
empty.
Functions not Available
481930
When working with a multidimensional data source, the Calculate menu does not show the
following functions:
• Rank
• % of total
• Percentile
• Quartile
Unable to Insert Data Items from Two Hierarchies of a Single Dimension
488615
In Query Studio or Report Studio, you cannot insert two data items from two hierarchies of a
single dimension.
Readme 21

Cognos 8 Known Issues
Background Color in Template Does not Appear
484108
Drilling on Measures
476624
When creating a Query Studio template in Report Studio, if you add a list object and change its
background color, the color change does not appear when you apply the template to a Query
Studio report.
Do not add any objects to the page body when you are creating a Query Studio template. The
page body should always be blank.
When working with a dimensional data source, if you insert a folder of measures in which there
are measures contained in another folder, you cannot drill on the measures.
To drill on the measures, drag each measure into the report instead of the folder.
Grouping on an Attribute
497529
When using a MSAS data source, grouping on an attribute may result in an empty report or in a
report that is incorrectly grouped.
Subtotals in Grouped Lists
498295
When using a PowerCube that contains a ragged hierarchy, if you group on the first level in the
hierarchy, subtotals may appear in the wrong place or show wrong values.
To resolve the issue, group on the second level.
Adding a Filter to a Crosstab with a Currency and a Calculation
500922
When working with a PowerCube as the data source, if you have a crosstab that contains both a
parent-child hierarchy representing currency and a calculated measure, and you then create a filter
on the measure, summary values are rendered incorrectly.
To work around this issue, ask your modeler to modify the currency dimension so that it is not a
parent-child hierarchy, or do not filter on the measure.
Filters May Not Work in Some Sectioned Reports
491443
In Query Studio, if a measure is cut and pasted before a sectioned item in a report when a filter is
based on any sectioned item that is below the sectioned measure, any filters set for the sectioned
grouping level will provide incorrect results. This is because Query Studio generates a filter with a
FOR clause that includes the sectioned measure.
Workaround: The FOR clause should exist to provide the level at which the filter is to be applied,
but the measure should not be included in the FOR clause. You must open the query in Report
Studio and remove the measure from the FOR clause
Unable to Filter on Multiple Currencies at Once
501536
In Query Studio, if you filter on currencies, you can only filter on one or all currencies. For
example, if your report contains four currencies and you filter on one or four currencies, the
report is filtered correctly. But if you filter on two or three currencies at once, no filter is applied to
the report. To filter on multiple currencies, you can use Analysis Studio.
22

Cognos 8 Known Issues
Summary Values of Non-additive Measures May Be Incorrect
496568
If a list report in Query Studio or Report Studio contains multiple measures and a Calculated
summary row, the summary row will always provide a Total summary of the associated rows,
which may be incorrect if the measures are non-additive. For example, percentages and average
values are summed.
Report Studio
This section contains known issues about Report Studio.
Style Properties not Supported
nbna
The following style properties will work when running reports in HTML format but not in PDF.
• The Show empty cell borders check box in the Table Properties dialog box.
• The Horizontal Alignment property value Justify.
• All options in the Text Flow & Justification dialog box:
• Direction
• Writing mode
• Bi-directional
• Kashida space
• The Text indent value in the Spacing and Breaking dialog box.
Bursting on MOLAP Data
491948
491952
Report bursting is limited when the underlying data source is a cube (Cognos PowerCube,
Microsoft Analysis Services, Hyperion Essbase or IBM DB2/OLAP). The burst report must be a
grouped report and the burst is restricted to the outermost grouping in the report. For example, if
you have a report grouped on Country and State, then you can burst the report only on Country.
Aggregate Values Are Not Appearing in Crosstabs
When working with dimensionally modeled data, if you place members from the same hierarchy
on opposite edges in a crosstab and then aggregate them, blanks appear instead of totals.
You can show the aggregate values.
480409
Steps to Show Aggregate Values
1. Access the query in Query Explorer.
2. In the Properties pane, set the Override Dimension Info property to Yes.
3. Click the Dimension Info tab.
4. For each level of the original dimension, create a separate dimension with a single hierarchy
and single level.
5. Include all necessary facts.
6. Lay out the query items in the report as per the original layout.
When you run the report, the aggregate values appear as expected.
Connecting Queries Between Different Data Sources
Cognos 8 supports the following:
Readme 23

Cognos 8 Known Issues
nbna
• RDBMS to RDBMS joins
• set operations of any two queries
• master-detail relationships of any two queries
• drill from any query to any other query
The following are not supported in this release:
• cube-to-cube (homogeneous) joins
• cube-to-cube (heterogeneous) joins
• cube-to-RDBMS joins
• cube-to-SAP BW joins
• SAP-BW-to-RDBMS joins
Creating a Chart from an Existing Query
474114
In Report Studio version 1.1, it is possible to create a crosstab report, add a chart object to the
page, and use the same query data as the crosstab to populate the chart automatically.
To give you more control over which data is shown in the chart, the auto populate option is no
longer included in Cognos 8. You must now define the data in the chart manually.
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, warnings, and information messages,
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 and may not return data.
Extra Rows Appear in a Grouped List
If you are working with a DB2/OLAP or Essbase data source, extra rows may appear in a grouped
list report when you add a filter and the Count function to the report. Or, you may see an empty
report instead.
To resolve this issue, remove the filter or the Count function from the report.
Pivoting to a Crosstab Shows the Member of the Attribute
nbna
Event Studio
You have a list style report or query and you have grouped by an attribute of a dimension.
Grouping by attributes is not supported in this release. Thus, when you turn a report that is
grouped by attributes into a crosstab, you see the member to which the attribute belongs. This can
affect summaries, particularly in cases where attribute values are repeated across members.
For example, the report contains a dimension with this structure: Product=level, Product Id=Id,
Product Name=caption, Color=attribute. Grouping on the attribute Color will give a different
result than grouping on Product Name/Product Id.
We recommend that report authors avoid creating crosstab reports with grouped attributes for the
current release.
This section contains known issues about Event Studio.
24

Cognos 8 Known Issues
Tasks Do Not Run According to Execution Rules
492331
If you run an agent with specified execution rules, then run the same agent again before the first
run has completed, some event statuses may be incorrectly evaluated. This may cause the agent to
perform tasks for event statuses that are not specified in the execution rules.
To avoid this problem, wait until the agent finishes running before you run it again.
Agent Run Fails
nbna
If you run an agent that does not include any data items from the package, then check the agent’s
run history in Cognos Connection, you notice that the run failed. The following error message
also appears.
CNC-ASV-0025 Agent Condition invalid: CNC-EVE-3105 Unable to update the event
status record. RSV-RND-0101 The layout does not refer to any data items. Unable
to render the XML or CSV output.
To avoid this problem, right-click a data item in the Insertable Objects area and click Insert as
Data Item.
Analysis Studio
This section contains known issues about Analysis Studio.
Analysis Studio Limitations
In this release, the following limitations exist for Analysis Studio.
Performance When Applying Filters
Complex filters against large cubes is known to slow performance. In these scenarios, we
recommend running the report from Cognos Connection, either by scheduling the report or using
the notify option.
Expand Level
Expanding a level is limited to three levels in the crosstab. To view more details at lower levels, we
recommend expanding once and go down on a level until you reach the desired level of detail.
This limitation was introduced to better manage performance when reading large data sources.
Subtotals and Calculations
Subtotals and calculations using calculated measures (e.g., count or average) will result in a "--"
(two dashes) to be displayed in the cells, rather than a value. Calculated (or non-rollup) measures
are visually distinguished by the measure icon in the data tree.
Expanded Sets Cannot be Saved as a Custom Set
Expanded sets cannot be saved as a custom set in this release.
Context Filter Limitations
In this release, sets filtered by a rule that references any of the automated subtotals, such as More
and Hidden, Subtotal (Included) or Subtotal (Excluded), cannot be used in the context area.
Filter by Label or Attribute is Case Sensitive
486777
When you define a filter rule by using a label or an attribute, the text is case sensitive.
Readme 25

Cognos 8 Known Issues
Cells with '- -' are Represented as NULLS in Export to Excel
488293
When a value cannot be computed by the data provider, two dashes (--) are shown in the cell. To
be compatible with the numeric format, this text appears as a null when exported to Excel.
Exporting the text may result in an error message being shown when opening the file with
versions older than Excel 2003.
Context Filter Limitations
In this release, you cannot use a set in the context section of the overview area if the filter rule of
the set references automated subtotals such as More and Hidden, Subtotal (Included), or Subtotal
(Excluded).
Defining Languages for OLAP Data Sources
499296
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.
Crosstab Shows Percentage But Chart Shows Values
494291
When the crosstab calculates the percentage of the total for an item, the chart does not show the
values as a percentage.
Analysis Studio Does Not Reflect Package Configuration Settings
498615
To improve performance, package configuration settings such as the default analysis and the
display limits are cached the first time you access a package. When you make any additional
changes, you must cycle or restart the report service to update the server cache.
Analysis Studio Ignores Changed Package Reference in Cognos Connection
499322
You cannot change the package reference for an analysis from the Properties dialog box in Cognos
Connection. This is because the analysis uses member unique name references.
Server Error When Sorting a Selection-Based Set by Attribute
492637
When a selection-based set contains members from different levels, sorting the set by an attribute
that is not common to all levels results in a server error.
Similarly, if you append a member from a different level to a selection-based set that is sorted by
attribute, the same error occurs.
Suppress Items when Accessing MS Analysis Services Cubes May Produce
Unexpected Results
When accessing Microsoft SQL Server Analysis Services cubes, applying Suppress Items with other
operations, such as Rank and Show as %, may produce the following results:
• the results of a Rank calculation show as errors
• when Show as % is applied, removes items that should not be removed
26

Cognos 8 Known Issues
501682 and 501709
Metric Studio
This section contains known issues about Metric Studio.
Default Import Source Expects a Folder in the Deployment Directory
nbna
When you create a Metric Package the default Import Source is set import tab-delimited files from
a folder called "cmm". To use this default location, manually create the folder in the deployment
directory. Alternatively, you can change the default import source to point to another folder in the
Deployment directory.
Test Data Source in Cognos Connection Fails for Security Reasons
nbna
The "Test Data Source" feature of the Cognos Connection Directory Tool does not work for
Metric Studio installations. The following error is always returned:
"RSV-BBP-0018 The current user does not have the capabilities required to execute the
'testDataSourceConnection' operation. Please contact your Administrator. "
This does not imply that the data source is unavailable or improperly configured.
Recommended Patches for Oracle 10g
nbna
There are several Oracle bugs that may be encountered when attempting to run Metric Studio on
Oracle 10g.
Oracle bugs 2170512, 1326581, 1306577 and 2966778 cause intermittent ORA-00904 errors in
the application, and are fixed by the application of the 10.1.0.4 patch set. Oracle bug (4261258)
which causes error ORA-7445 [KKOIJG] in select statement during parsing phase is resolved by
patch 4287619.
Consequently, we recommend the installation of the following patches if customers are using
Oracle 10g:
• 10.1.0.4 patchset (available at http://metalink.oracle.com)
• Patch 4287619 (available at http://updates.oracle.com/download/4287619.html)
"To-Date" Comparisons are Not Available
nbna
In this release, "to-Date" comparisons are not available (e.g. Year-to-date summary values).
Concurrent Tasks May Corrupt Metric Store
473002
The Data Integration Service does not prevent two tasks from running concurrently on the same
metric store. If two or more tasks are run concurrently by one or more users, the metric store may
be corrupted.
Oracle 9.2 Package Initialization Error if NLS_LANG Environment Variable is
Not Set Appropriately Before Starting Up Cognos 8 Tomcat Server
You will encounter an exception error when trying to initialize a CMM package if the Oracle
specific environment variable NLS_LANG is not set correctly.
Readme 27

Cognos 8 Known Issues
nbna
Workaround: Cognos Series 8 requires that the Oracle specific environment variable NLS_LANG
be set appropriately before starting up Cognos 8 Tomcat server. Please ensure that the character
set portion of this variable is set to UTF8. For example, in the United States, this may be
something like: AMERICAN_AMERICA.UTF8
User Permissions for the Metric Store Database (MS SQL Server)
486855
The user account for the metric store database must be the database owner. You must use the
owner user-account to log on to the Cognos 8 data source used in the Metric Package.
For information about setting user permissions, see the MS SQL Server documentation for the
sp_changedbowner utility.
Metric Type Settings Lost When a Calendar is Cleared
479177
After you Clear metric history and calendar data for a Metric Studio package, you see that the
metric types have lost their business calendar settings even after the Metric Studio calendar was
recreated. If using Metric Designer, the metric types defined in Metric Studio are no longer visible.
To preserve these settings, export your metric types before clearing the business calendar. After
clearing the calendar, reload your exported .cmm file (metric types staging file) or edit the metric
types manually to reset the different business calendar settings.
Equations Using Only Constants are not Allowed in Calculated Metrics Types
486808
In the metric type properties page, users cannot create an equation with a constant value but no
metric type as operands. They will be prompted to cancel or modify the equation.
Constant equations loaded through data staging will be ignored by Metric Studio.
You can stage constant values for different metrics manually or using Metric Designer. You can
also enter the constant values directly into other equations where they are used. Also, user entered
values can be used.
Default Report and Diagram Setting not Exported
489347
When you export objects and their related diagrams and reports to files, the settings for each
object's default report and diagram are not included. When you import these files to a new metric
store, you will have to set the default reports for each object using the user interface.
Manually re-set the default diagrams and default reports in Metric Studio after running the import
task.
When Migrating a CMM 2.2 Application With Translated Units to Metric Studio
8.1, Metric Values are not Migrated
487230
When migrating a CMM 2.2 application in which the user has translated units in CMM
Administration, Metric Studio 8.1 will corrupt some metric types and the metric values will not be
migrated to the new Metric Studio 8.1 application.
To correct this issue, the user should upgrade to the latest hotsite version of CMM 2.2 before
exporting their application data. Please contact Cognos Customer Support to obtain the latest
CMM 2.2 hotsite.
28

Cognos 8 Known Issues
Data Format for Specifying Security on Groups and Group Types has Changed
490784
Security defined for groups and group types that are in the policy stage flat files (cms), created for
the beta version of Metric Studio 8.1, will not load.
The data format has changed since beta. Before, the group and group type objects were identified
by name but now object ids are used.
If the group and security data currently resides in a beta metric store then upgrade the metric store
and export the groups, group types and the permissions.
If the group and security data currently reside tab-delimited files, modify the files to load groups
and group types using the object stage file and specify object ids for all of the groups and group
types. Modify the policy stage file to reference the groups and group types by object id.
Group-type Names Display as Unreadable Characters (SQL Server Only)
490856
After importing from Cognos Metrics Manager 2.2 files into Metric Studio 8.1, group-type names
in double-byte character sets such as Japanese display as unreadable characters.
Modify the Cognos Metrics Manager 2.2 .cmo file that contains the localized group type names so
that it conforms to the Metric Studio 8.1 format (see the user documentation for details.) Load the
new file from a Metric Studio 8.1 import source.
Multilingual Characters May not Print Correctly When Using an Oracle Metric
Store
488010
466171
When using an Oracle metric store, some characters (for example Chinese, Japanese) may not
show properly in the Printer Friendly version of a Metrics Studio page.
To correct this problem, set the NLS_LANG environment variable as documented in the Set Up
the Data Source or Import Source Environment section of the Installation and Configuration
Guide.
Imports and Exports May Fail in a Distributed Installation
492065
If Metric Studio is not installed on the same server as Content Manager, the import or export may
fail because the import file path is not available.
Install the Content Manager component on the application server where the Application Tier
Components (Metric Studio) are installed.
Content that uses double-byte characters displays as unreadable characters
(Oracle)
494367
Content entered using a double-byte character, set such as Japanese, displays as unreadable
characters in the user interface. This includes the navigation path shown at the top of most screens
and the Import Sources screen under the Tools menu.
You must use a database character setting (NLS_CHARACTERSET) that supports the characters
for the locale setting.
Readme 29

Cognos 8 Known Issues
Removing Periods From a Calendar That Contains Weeks May Remove the First
Week of the First Remaining Year
500188
When removing periods from a calendar that contains weeks, the first week of what is now the
first year is missing. This occurs when the last week of a deleted year spans two years.
Delete one less year than you otherwise would have.
Errors During the Import of a Custom Calendar Are Not Shown in the Calendar
Creation Wizard
500259
If the tab-delimited files that import your custom calendar contain errors, the resulting custom
calendar may be missing custom names, or contain unexpected errors. However the import errors
are not shown in the Initialize Metric Store wizard. Instead, the import errors are shown in *.bad
files which can be found in directories under installation_location\logs\CMM_Dataload.
Ensure that there are no *.bad files in directories under
installation_location\logs\CMM_Dataload.
Oracle Database Created but Not Configured as Expected
497970
A user running the cmm_create_db script to create a metric store must be a member of the
ORA_DBA group (Oracle on Windows) or the dba group (Oracle on UNIX). If they are not, some
steps in the script will fail.
The database is created but the script steps fail so additional configuration, such as creation of the
CMM user account and granting of privileges do not occur.
The user cannot test the data source connection or access the data source when creating a new
package.
To work around this problem, after the database is created, logon to the database as SYS and
manually execute the configuration steps in the prepare_cmm_db.sql script which is located in
c8_install_location/configuration/schemas/cmm/oracle/util.
Unexpected Date Format in the User Interface
428347
Short date formats are not set according to regional locale settings of the Windows OS. Instead,
the date formats are based on the ICU standard called CLDR, documented at
http://www.unicode.org/cldr. For example, if the locale is set to Italian and the date is December 1,
2003, the Windows short date format is 01/12/2003 but the ICU date format is 1-dic-03.
Initializing an Oracle Metric Store Which Does Not Have the NLS_LANG
Environment Variable Set Properly Has Unexpected Results
495504
If you initialize an Oracle metric store without first setting the NLS_LANG environment variable
correctly, results are inconsistent. The installation may fail or you may be asked to upgrade the
metric store immediately after install.
Set the NLS_LANG environment variable appropriately for your own environment. The purpose
and syntax of setting this variable can be found at:
http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96529/ch3.htm#49560
30

Cognos 8 Known Issues
Some Characters Cannot Be Loaded When the Database Has a Non Unicode
Dataset
If the database character set(s) does not support unicode characters, Metric Studio allows you to
enter values using the user interface but those values cannot be imported using tab-delimited files.
They will result in unreadable characters.
498792
The workaround for this problem is to use a database character set setting that supports the
appropriate characters.
Extending a Calendar That Has No Year-Level Fails If the Number of Periods of
the Initial Calendar Contains a Partial Year
If you attempt to extend a calendar that has no year-level and contains a partial year, you receive
an error or the calendar is created with incorrect period names.
The periods in your initial calendar cannot equate to a partial year. You should also extend the
calendar by any number of periods that equate to years.
500197
For example, if the top level of the calendar is 'Quarters', then the calendar must be created with a
multiple of 4 quarters. A calendar with 13 quarters will generate the above error when it is
extended.
Calculation Fails When the Decimal Period Is Not a Period
Metric type calculation fails if the decimal placeholder in values typed into the expression editor is
not a period. For example, in a French environment the decimal symbol, comma, will not be valid
in the metric type expression editor of Metric Studio.
494413
Use periods instead of commas.
The start_time_cd and created_dt Columns of the .cmn Tab-Delimited File
Must Be Formatted as yyyy-mm-dd hh:mm:ss (DB2)
499787
If the values in the start_time_cd and created_dt columns of the .cmn tab-delimited file are not
formatted as yyyy-mm-dd hh:mm:ss, you will receive the following error when you try to import
the .cmn file into a DB2 database and the task will fail:
DIS-RUN-3272 Failed to import file 'your_file.cmn' into package
'your_package_name' from location 'Default Import Source'.
The following messages will also be added to your *.cmn.log file under the subfolder of
installation_location\logs\ CMM_DataLoad.
SQL3112W There are fewer input file columns specified than database
columns.
SQL3519W Begin Load Consistency Point. Input record count = "0".
SQL3520W Load Consistency Point was successful.
SQL0180N The syntax of the string representation of a datetime value is
incorrect. SQLSTATE=22007
SQL3185W The previous error occurred while processing data from row "1" of
the input file.
The values of the start_time_cd and created_dt columns of the .cmn flat file must be changed to
have the format yyyy-mm-dd hh:mm:ss (24 hour clock).
Imports and Exports May Fail in a Distributed Installation
If Metric Studio is not installed on the same server as Content Manager, the import or export may
fail because the import file path is not available.
Readme 31

Cognos 8 Known Issues
492065
496075
Install the Content Manager component on the application server where the Application Tier
Components (Metric Studio) are installed. Also ensure that the Deployment files location is set to
a common location that can be accessed from all servers.
Printing a List of Scorecard Projects or Metric Actions Can Result in an Empty
List
Printing from the scorecard projects or metric actions tab can result in a PDF showing only a
heading and footer even though the list is visible in the user interface.
The problem occurs if the configured gateway URI and the URL used by the user to access Metric
Studio are different.
499590
For example, the Gateway URI value under Environment in Cognos Connection may be set to
http://gatewayhostname:80/cognos8/cgi-bin/cognos.cgi but users access Metric Studio using the
URL http://localhost:80/cognos8/cgi-bin/cognos.cgi. Or, the Gateway URI value under
Environment in Cognos Connection may be set to http://localhost:80/cognos8/cgi-bin/cognos.cgi
but users access Metric Studio using the URL
http://gatewayhostname:80/cognos8/cgi-bin/cognos.cgi.
You must configure the Gateway URI and the URL used by users to access Metric Studio with the
same value. The recommended value is http://gatewayhostname:80/cognos8/cgi-bin/cognos.cgi.
Calendars Including Weeks Contain More Years and Start One Year Earlier than
Expected
500541
After creating a calendar that contains weeks, the calendar starts one year earlier then the date
you specified. The calendar also extends beyond the expected end-date. When you extend the
calendar, it is extended by more years then you expect.
This behavior is as designed and is because weeks can cross month and year boundaries.
Metric Studio ensures that the first week of the calendar occurs before the start of your data
because the first week is likely to be a partial week. Metric Studio also ensures that the calendar
does not end on a partial week so that the calendar can be extended without affecting rollup
results.
Metric Lists Do Not Display When Using DB2
500531
Errors occur when viewing metrics if the system locale for a Metric Studio server installed on DB2
is configured to format numbers using a character other than a period as the decimal point.
On the server, add the following to the file db2cli.ini
[DBALIAS]
PATCH2=15
Where DBALIAS is name of the DB2 database used as the metric store.
On Windows, db2cli.ini can be found in [DB2InstallFolder]\sqllib and on UNIX db2cli.ini can be
found in [DB2InstanceFolder]/sqllib/cfg.
Non-Integer Values Using a Character Other Than a Period as the Decimal
Point Are Not Imported When Using DB2
If non-integer data values to be imported into Metric Studio use a character for the decimal point
other than the period character, then the values are not loaded. A NULL value is loaded instead.
An example of a warning message in the import logs located in the subfolder of
Installation_Location\logs\CMM_DataLoad is
32

Cognos 8 Known Issues
SQL3123W The field value in row "1" and column "7" cannot be converted to a
PACKED DECIMAL value. A null was loaded.
The following non-integer fields are affected
Diagram staging file (.cdo)
XPOS, YPOS, XEND, YEND
Value staging file (.cmv)
KPI_VALUE
500920
Metric type staging file (.cmm)
HC_YAXIS_MIN, HC_YAXIS_MAX
Always use a period, ".", as the decimal point in the data to be imported.
When Running the Metric Maintenance Task, Clear Metric History and
Calendar Data, Some Calendar Properties May Be Lost
501076
After running the Metric Maintenance task Clear Metric History and Calendar Data, objects, such
as metric types, might lose calendar related properties. An example of a calendar property is the
business calendar level. Also, some parts of the Metric Studio user interface might not work
properly even after the calendar is recreated.
You must reload all of the metadata and data files.
Data Removed From Metric Data Store
501076
If the Clear calendar data metric maintenance task option is set, all data and objects, except global
settings and display preferences, are permanently removed from the metric data store. This option
is set when
• you run the Clear metric history and calendar data metric maintenance task
• you run a user-created task that sets the Clear calendar data option
To avoid this problem, export the content that you wish to preserve to files before you run the
metric maintenance task.
List View Displays Incorrect Week
501076
When the enabled business days of the first week are in the previous year, the List view starts with
week two. Meanwhile, the List view for the previous year displays the first week. In this case, the
first week will not have a subtotal row. To view the week total, the user must view the Scorecard
for that specific metric and week.
This issue can also occur with the last week of a year, typically week 52, which is displayed in the
view for the next year.
Metric Designer
This section contains known issues about Metric Designer.
Readme 33

Cognos 8 Known Issues
Metric Designer Does not Warn the User if the Metrics Extract Mapping do not
Match the Metric Type Rollup Properties
474101
When the user maps more than the lowest time level(s) in a metric extract, Metric Designer does
not warn the user if the metric type rollup calculation property is set to any setting other than
'Supplied by Client'.
The work around for this issue is for the user to confirm that the metric type rollup calculation
property to be set to Supplied by client.
Error UDA-SQL-0564 When Executing a Notes Object Extract
475776
This error (UDA-SQL-0564) occurs when the user has mapped a non-date value to the "Start
Time Code" attribute. in an object extract.
The user can use the "_make_timestamp" function in the expression editor to convert the
non-date value to a date value.
Metric Type Settings Lost When a Calendar is Cleared
479177
After you Clear metric history and calendar data for a Metric Studio package, you see that the
metric types have lost their business calendar settings even after the Metric Studio calendar was
recreated. If using Metric Designer, the metric types defined in Metric Studio are no longer visible.
To preserve these settings, export your metric types before clearing the business calendar. After
clearing the calendar, reload your exported .cmm file (metric types staging file) or edit the metric
types manually to reset the different business calendar settings.
Framework Manager - Import Source and Anonymous User Language
Preference
nbna
When accessing an Framework Manager package using the anonymous user, Metric Designer uses
the Regional Setting of the computer where Metric Designer is installed instead of the Cognos 8
Language Preference.
Workaround: Configure the computer Regional Settings to be the same as the Anonymous user
Cognos 8 Language Preference.
Framework Manager - Import Source Connections and Credentials
nbna
Metric Designer does not support Framework Manager import sources with missing connection
or credentials or Framework Manager import sources with multiple import sources.
Metric Designer delivers unreadable values from Japanese Microsoft SQL
Server Import Sources when writing to files
441923
Metric Designer delivers unreadable values to Metric Studio when using an Import Source that
references a MS SQL Server Japanese_CI_AS collation and writing the extract results to files.
To correct this issue change the Metric Studio Import source Collation Sequence located in Tools,
Import sources, to ‘Japanese Unicode’
34

Cognos 8 Known Issues
Japanese Extracts to Oracle via Metric Studio Staging files Fails
Executing a Metric Designer extract to read from a SQL Server Japanese_CI_AS collation import
source and deliver data to Metric Studio staging files that are loaded into a Metric Studio Oracle
9i data base using the Import data from files into staging area option in Cognos Connection fails.
448555
Workaround: Set the NLS_LANG = JAPANESE_JAPAN.UTF8 and changing the Metric Studio
Import File Collation to 'UTF8' on the Import Sources page, located under the Tools menu in
Metric Studio.
Cognos 8 Package Import Source - "No Accessible Views" Error
448059
While selecting a Cognos 8 package to use as a Metric Designer extract import source, you receive
the message:
"BME-AS-0019 There is no views accessible for the user".
This issue may occur if you previously attempted to connect to a package and was denied by
security.
Workaround: Exit and reopen the extract wizard.
Create Date Field for Object Extracts
440772
The created date field is not available for extracts. Metric Studio uses the publish/execution date
for the create date.
Metric Filters are Still Invalid After Upgrading a Model and Retargeting Broken
References
After upgrading a model and retargeting a broken reference to your import source, metric filters
to that import source are not updated correctly.
473386
Open the extract, select the metric mapping page, and delete and recreate your metric filters.
Unrecognized Vendor-Defined Japanese Characters in Cube Extracts
When you define an extract using a cube import source, Metric Designer does not recognize all
vendor-defined Japanese characters that were used in the cube.
nbna
Workaround: Do not use the limited vendor-defined characters.
Problem Trying to Execute an Extract Created Against a Framework Manager
Model Going Against a Teradata Database
At execute time the follow error occurs: "E-DEF-0177 An error occurred while performing
operation 'sqlPrepareWithOptions' status='-69'.
UDA-SQL-0043 The underlying database detected an error during processing the SQL request.
[NCR][ODBC Teradata Driver][Teradata RDBMS] The number of digits specified must be
between 1 and 18."
In \configuration\pd.ini, there is now a new section called "ExecuteOptions", with
two preferences:
1. "castKPIValues" -- if set to "true", CMD still specifies the CAST expression.
2. "castKPIValuesType" -- Applicable only if "castKPIValues" in (1) above is set to "true".
Specifies what type to cast the measure to. Default is DECIMAL( 19, 5 ).
Readme 35

Cognos 8 Known Issues
Workaround: Set the "castKPIValuesType" preference to DECIMAL( 18, 5 )
468372
Example:
true
DECIMAL(18,5)
IQD Import Source - Error Reading IQD file that Contains the Oracle 'Replace'
Function
445064
When using an IQD import source that contains a Oracle 'replace' function, the following error is
displayed:
QE-DEF-0177 An error occurred while performing operation
'sqlPrepareWithOptions' status='-228'.
UDA-SQL-0450 An unexpected error encountered during the "fetch" operation.
UDA-SQL-0450 An unexpected error encountered during the "fetch" operation.
UDA-SQL-0450 An unexpected error encountered during the "fetch" operation.
UDA-SQL-0219 The function "replace" is not available as an external, database,
or built-in function.
To correct this issue, edit the file "cogdmor.ini" located in the installation location\cognos\pd1\bin
directory and set "Empty_String_Is_Null" to "F".
Adding Multiple IQD files to an Import Source
When you add multiple IQD files to a 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.
440049
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.
Data Sources Not Supported
The following data sources are not supported as Metric Designer import sources in this release:
• SAP BW data source
• Cognos 8 Contributor data source
• Microsoft Analysis Services data source
• IBM OLAP server data source
• Hyperion Essbase data source
• PowerCube data sources with DB2 target Metric Store
nbna
Incorrect Scorecard Rollup Values for PowerCube Expressions
500830
When a Cognos PowerCube metrics extract has more than one scorecard level in the scorecard
hierarchy, and the metric attributes (Actual, Target, Tolerance, etc.) contain expressions created
using the Expression Editor, the rollup values of the parent scorecard in some cases may be
incorrect.
36

Cognos 8 Known Issues
Previewing the Scorecard Tree and Assigning Metrics to Scorecards in the
Metrics Scope page does not work
482648
When previewing the Scorecard tree with levels that contain string expressions in the Scorecard
Level attributes for a PowerCube metrics extract, the scorecard preview does not work. Also,
refreshing the Metrics Scope page results in an empty window which prevents the user from
assigning metric values to scorecards.
Workaround: PowerCube metrics can be executed to staging tables and flat files or published to
the content store despite this error. There is no workaround for metrics scoping other than to use
complex filters on Scorecards.
Filters on Parent-Child Hierarchies are not Supported for Dimensional (OLAP)
Data sources
494909, 497977
Filters on parent-child hierarchies do not work correctly for dimensional (OLAP) data sources.
Filtering the parent level does not filter the child level as it would for a hierarchy based on a
regular level.
Error Occurs for a Metrics Extract Containing Static Text-type Scorecard
Levels
500448
Metrics extracts containing text-type scorecard levels produce a CCLUnknownError when
previewing the scorecard tree, refreshing Metrics Scope page, or executing the extract.
Workaround: Use the All (static) member. This alleviates the business need for text-type scorecard
levels.
Metric Extracts Containing Typed-in Constant Metric Attribute Values Do Not
Deliver Metrics for PowerCube Data Sources
500908
A metrics extract containing typed-in constant metric attribute values (Actual, Tolerance, Target,
etc.) fails to deliver rolled-up metrics for parent scorecard levels for a PowerCube data source. The
execution of the extract delivers only the metrics at the lowest scorecard levels.
Workaround: Use the Expression Editor to create a summary expression for the Metrics attribute.
For example:
Average()
Average (.25)
Mapping Levels to Qualifiers Using the Expression Editor for a PowerCube Data
Source Does Not Work
501433
When creating an expression for qualifiers that contain levels in the expression editor, and using a
PowerCube data source, the qualifier data is not delivered into the staging files or tables.
Workaround: Use query items instead of levels for mapping a qualifier
Error Occurs When Query Items Mapped to Metrics Qualifiers Are Referenced
in Scorecard Filters
The following error occurs when query items mapped to a metrics qualifier are referenced in the
scorecard filters for a Microsoft SQL server based Metric Studio data store.
Readme 37

Cognos 8 Known Issues
501492
PD-MD-0089 An error occurred in the execution of the metric values query for extract
.
QFS-ERR-0130 The query is not supported
Workaround: Filter by the caption or filter by PPDS_KEY instead of PPDS_CODE.
Framework Manager
This section contains known issues about Framework Manager.
Unable to Test Physical Model after Third-Party Metadata Import
481680
After importing third-party metadata into Framework Manager, physical tables may fail while
being tested.
During the import, the model name may have been written into the database properties as a
schema or catalog.
To resolve this issue, check the database properties and delete the schema or catalog if it has the
same name as your model.
Invalid Expressions after Third-Party Metadata Import from DB2 Cube Views
After importing DB2 Cube Views into Framework Manager, some expressions in calculations may
be invalid because they use DB2CV references ($$1, $$2, and so on) instead of Framework
Manager references. Query subjects that use these embedded calculations in DB2 Cube Views
expressions will not be testable.
To fix the invalid query subjects, do the following:
1. In Framework Manager, identify all imported query items that represent embedded
calculations using references such as $$1, $$2, and so on.
2. In the Properties pane, find the information provided in the patternMapping property for
each query item.
The patternMapping property indicates the mapping between the DB2 Cube Views
parameters in the imported calculation and the actual DB2 Cube Views object references in
the original model.
3. Double-click a broken query subject.
4. Double-click the embedded calculation corresponding to the query item identified in step 1.
5. If the calculation was assigned a default name ("Calculation..."), replace it with the actual
query item name.
6. Replace the DB2 Cube Views parameters with the actual Framework Manager object
references that these parameters represent.
7. Repeat these steps for each broken query subject.
Here is an example:
After importing a DB2 Cube Views model, "Logical Model" -> "Sales Model" -> "Sales Facts" is
a broken query subject because of the calculation in the [Sales Model].[Profit] query item.
The patternMapping property for this calculation contains:
[OPEN BRACE]$$1[CLOSE BRACE]=Sales Facts.Revenue [OPEN BRACE]$$2[CLOSE
BRACE]=Sales Facts.Costs
Its expression is:
[OPEN BRACE]$$1[CLOSE BRACE] - [OPEN BRACE]$$2[CLOSE BRACE]
38

Cognos 8 Known Issues
499847
Using this information, change the expression of the query item to:
[Physical Model].[SALESFACT].[REVENUE] - [Physical Model].[SALESFACT].[COSTS]
Levels in IBM DB2 Cube Views Are Not Assigned a Role of memberCaption
A default attribute is assigned to a level in DB2 Cube Views. The default attribute contains the
data that will appear for the level. In the current release, this information is not assigned the role
of memberCaption during the import of metadata.
489386
In Framework Manager, assign the memberCaption role to the attribute associated with the level.
Functional Dependencies in IBM DB2 Cube Views Are Not Defined as
Determinants
In DB2 Cube Views, functional dependencies can be captured in their schemata for levels. In the
current release, this metadata is not mapped into determinants during import of metadata.
489381
In Framework Manager, define the functional dependencies as determinants.
Occasional Session Issues When Testing Queries in Framework Manager
You may receive an error message when testing query subjects or expressions in Framework
Manager. This is caused by query caching issues when working with more than one project in the
same Framework Manager session.
nbna
To resolve this issue, save your work, close Framework Manager and reopen your project. If the
error still occurs, it is not a session issue and additional troubleshooting will be required.
Embedded Externalize Method
nbna
The Embedded externalize method appears in Framework Manager but does not represent
functionality for the current release.
Unable to Use an IQD Created in Framework Manager That Contains an Oracle
Stored Procedure
When trying to use an IQD created in Framework Manager that contains an Oracle stored
procedure, you may receive a message similar to the following:
(TR0118) Transformer can't read the database [datasource] defined in \.iqd.
DMS-E_General A general exception has occurred during operation 'execute'
The native SQL generated in an IQD created in Framework Manager is wrong. The IQD cannot
be used in Transformer.
nbna
To resolve this problem, you should execute the stored procedure and set the Externalize Method
to IQD. Create a model query subject from the executed stored procedure, then publish the
package and open in Transformer.
Readme 39

Cognos 8 Known Issues
Problems Arising When an IQD File Exported from Framework Manager
Connects to Two Databases
nbna
When exporting data from Framework Manager to Transformer, it is possible to externalize a
single IQD file that generates SQL for two different databases. However, due to differences in the
way data access layers are handled in Cognos 8 and Transformer, Transformer cannot import such
an IQD file.
This is a known issue and Cognos is currently developing a solution to address it.
Cannot Specify the Order of Members
491332
When you are defining a level for a regular dimension on a relational data source, you cannot
specify the order of the members in the current release. This limitation results in the following
functions returning members who are dependent on the sort order in which the data was
retrieved:
• firstFromSet
• remainderSet
• head
• item
• lag
• lead
• nextMember
• prevMember
• lastPeriods
• closingPeriod
• openingPeriod
• parallelPeriod
• periodsToDate
• subset
• cousin
• firstChild
• firstSibling
• lastChild
• lastSibling
We recommend that you do not use these functions when using dimensionally modeled relational
data sources. To ensure that report authors do not use these functions, use Quality of Service to
exclude them from the functions list.
Full Outer Joins and Oracle
nbna
By default, Cognos 8 will not send full outer joins to ORACLE 9 and 10G due to the 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)
Please note any manual edits to the ini settings are overwritten by the next install and you must
manually replicate them on all machines where you have installed Cognos 8 or Framework
Manager.
40

Cognos 8 Known Issues
Upgraded Report Does Not Run Due to Incompatible Datatype
Enhancements have been made in Cognos 8 to more strictly enforce datatype checking. When you
upgrade a report to Cognos 8, the report may not run due to an error about incompatible
datatypes.
This can be caused by
• creating a calculation that uses a prompt and not testing the calculation before saving it
• manually setting an incorrect datatype in the Cognos ReportNet model
To resolve this problem, open and test the calculation or query subject that is affected. This will
correct the datatype.
496391
You can also manually correct the datatype in the Cognos ReportNet model and then upgrade the
report again.
Cannot Synchronize a Project in a Repository
When you try to synchronize a project that is in a repository, nothing happens and no error is
reported. This happens whether the project is checked in or checked out.
499849
To resolve this problem, use the Manage Projects command or the Save As command to make a
copy of the project. This will remove repository information. Run synchronize again, and then put
the project back into the repository.
Errors Using Non-English Version of Visual SourceSafe 6.0
451487
You use a non-English version of Visual SourceSafe 6.0 and you create a new VSS connection in
the Connection Manager of the Dialog Repository. You encounter errors when
• testing the connection
• creating a new folder under the connection
• adding the root of any project to VSS
In this release, Framework Manager is unable to work with non-English versions of Visual
SourceSafe 6.0.
Unable to Start Framework Manager
491879
When starting Framework Manager, you may receive the following error message if you do not
have administrator privileges on the local machine.
BME-EX-0046 Unable to save the project. The file
D:\ProgramFiles\Cognos8\win32\bin\../configuration\bmt.ini does not exist or
has read-only attributes. Check if the file exists or change the attributes of
the file to read-write and save the project again.
To resolve this problem, ask your administrator to grant you administrator privileges on the local
machine.
Readme 41

Cognos 8 Known Issues
42

Cognos 8 Documentation Updates
Cognos 8 Getting Started
This section contains additions and corrections that will appear in the next version of Cognos 8
Getting Started.
Example - Monitor Performance
Note: This topic will include the following additions in the next version of the Cognos 8 Getting
Started.
Step 2 should read as follows:
In Cognos Connection, open Metric Studio and select the GO Metrics package.
Step 4 should read as follows:
Click the Asia Pacific - Return Quantity % metric and then click List.
Example - Manage an Event
Note: This topic will include the following additions in the next version of the Cognos 8 Getting
Started.
The query item Reason description is now named Return reason.
In step 3, you should create the following expression:
[Return quantity]>0 AND [Return reason] IN ('Unsatisfactory product', 'Defective product',
'Incomplete product', 'Wrong product shipped')
Cognos 8 Troubleshooting Guide
This section contains additions and corrections that will appear in the next version of Cognos 8
Troubleshooting Guide.
Application Error Appears When Upgrading a Report
Note: This topic will be added to the Troubleshooting appendix of the Report Studio User Guide
in a future release.
When upgrading a report, the following error appears if the report contains data items in the page
layout that are not in a data container:
RSV-SRV-0040 An application error has occurred. Please contact your Administrator.
This error occurs when Cognos 8 cannot determine the query reference for a data item. Such data
items are identified by a small red circle with a white x icon that appears in the lower left corner.
To correct the error, drag the data items into a container. If the container is a list, we recommend
that you drag the data items into the list page header or footer, or the overall header or footer. If
you want to see the first row of the item on each page or in the overall report, drag the item to the
list page header or overall header. If you want to see the item’s last row on each page or in the
overall report, drag the item to the list page footer or overall footer.
Tip: If a header or footer does not exist, create it.
Readme 43

Cognos 8 Documentation Updates
Log Files
Note: This topic will include the following additions in the next version of the Cognos 8
Troubleshooting Guide.
The ReportNet to Cognos 8 Upgrade File
This file contains a summary of the results of an upgrade from ReportNet to Cognos 8. The log
file is named upgradeLog.xml and is located in the c8_location/log directory. The file is in xml
format and references an xslt stylesheet. You can double click the file to have it appear in your
browser.
Mixed Languages Are Displayed in Cognos Connection When Using Samples
Note: This topic will be added to the Cognos 8 Troubleshooting Guide in a future release.
You open a Cognos PowerCube in Cognos Connection and see a mixture of languages.
When you restore the Cognos_samples.zip file in the webcontent/samples/content folder it
contains multilingual content. When you change the locale setting on your computer, reports
appear in the language specified for your computer. This is not true for sample Cognos
PowerCubes. When you restore Cognos_powercubes.zip, a different folder is set up for each
language. If you select a PowerCube from a language folder that is different than the language
specified by the locale setting on your computer, a mixture of languages is displayed in Cognos
Connection.
There are two options for solving this problem:
• Re-install the Cognos PowerCube. First ensure that your computer is set to the locale that is
consistent with the language of the PowerCube package you are installing. Then, install only
the package from the language folder that matches the locale setting.
• Or, in Cognos Connection, open each PowerCube package, click the Set Properties button,
and in the Language box, select the language of the Cognos PowerCube.
Not Yet Optimized Cognos PowerCubes May Open Slowly in Cognos 8
Note: This topic will be added to the Cognos 8 Troubleshooting Guide in a future release.
If your non-compressed PowerCubes take too long to open in the Cognos 8 Web studios, we
recommend that you run a command line utility named pcoptimizer, supplied with Cognos 8, to
improve run-time OLAP performance. This optimization utility is suitable for older PowerCubes
when the model no longer exists or the data used to build the PowerCube is no longer available.
With Transformer Version 7.3 Maintenance Release 2, you have the option of making this
optimization an automatic part of the build process, by adding an entry to your Windows .ini file
or by creating the required environment variable on UNIX. If you use this method, the
optimization process also enables drill-through access on all PowerCube measures by default.
There is an expected, but slight, increase in PowerCube size and build times. However, in most
production environments, run-time PowerCube OLAP performance improves significantly.
Steps to Use the Command Line Utility (Cognos 8)
1. Back up your target PowerCube, then navigate to the Cognos_8_installation_location/bin
directory.
2. On Windows, open a command line window and run PCOptimizer.exe.
3. On UNIX, enter the following line to run the optimization command line utility:
pcoptimizer [-t] [-v] [-h]
where is the full PowerCube or time-based partitioned control cube name with
the .mdc extension, if the PowerCube resides in the same location as pcoptimizer. Otherwise,
is the full path with the .mdc extension.
44

Cognos 8 Documentation Updates
Note: This method only supports metadata extraction. To set up user-configurable drill-through,
you must use Transformer and specify automatic optimization. Wildcard character support is not
currently available. You must therefore invoke the utility once per PowerCube. If is
not provided, the program enters an interactive mode, prompting you for a PowerCube name and
accepting keyboard input. The optional parameters are as follows:
• -t or test mode; it tests whether the metadata was extracted and loaded into the PowerCube.
The return code indicates the status.
0 if the metadata was extracted and loaded
10 if the metadata was not loaded
20 if an error occurred while accessing the PowerCube
• -v or verbose mode; text is output to standard output (stdout), indicating what was done,
including error message if any. If running in interactive mode, -v is assumed. All text is
currently output in English only.
• -h for command-line help; if is not provided, it prints the usage and options to
the screen.
Steps to Configure Automatic Optimization (Transformer Version 7.3)
1. On Windows, to enable automatic optimization for all PowerCube builds, locate the
trnsfrmr.ini file in the installation_location\cern\bin directory, open it in any text editor, and
add the following entry:
EnablePCOptimizer=1
Optimization is now turned ON for all PowerCube builds.
2. On the Windows command line, to optimize a specific PowerCube build, type the following:
trnsfrmr –DEnablePCOptimizer=1 –cm
3. On UNIX, to enable optimization for all PowerCube builds during the current session, use the
-D flag or define the environment variable EnablePCOptimizer in the trnsfrmr.rc file(s).
Tip: To disable the feature, change the value of your optimization setting to zero or remove
the definition.
4. After your PowerCubes build, you can open the relevant log files and confirm that the
following entries appear:
Start updating of ‘cube_name’ with optimized metadata.
. . .
End updating of ‘cube_name’ with optimized metadata.
This indicates successful extraction of the metadata needed to optimize the opening of each
PowerCube in Cognos 8, as well as drill-through support for all measures in each PowerCube.
Failed to Execute Step step_name in Package package_name Because a
Conflicting Process is Already Running. Please Try Again Later.
Note: This topic will be added to the Cognos 8 Troubleshooting Guide in a future release.
The data integration service performs tasks, such as the metric maintenance tasks on the metric
store. Simultaneous execution of some tasks can cause data to be corrupted or lost. A locking
mechanism ensures that this does not occur.
This error occurs when a task does not start because a potentially conflicting task is already
running or because a lock for a previous task did not clear.
Wait and try to run the task at a later time. If the error continues to occur, check the crn_client log
file to identify the lock that was not cleared and use the appropriate statements to clear the lock
(p. 45).
Failed to Unlock the Database After Executing Step step_name in Package
package_name. Please Contact Your System Administrator.
Note: This topic will be added to the Cognos 8 Troubleshooting Guide in a future release.
Readme 45

Cognos 8 Documentation Updates
The data integration service performs tasks, such as the metric maintenance tasks on the metric
store. Simultaneous execution of some tasks can cause data to be corrupted or lost. A locking
mechanism ensures that this does not occur.
This error occurs when a task being performed by the data integration service fails to remove a
lock from the Task_Locks table in the metric store.
The system administrator can clear locks by stopping and starting the data integration service. For
more information, see the Administration and Security Guide.
You can instead manually clear records in the Task_Locks table of the metric store by deleting
locks.
Step to Delete, from a Metric Store, All Locks
• Execute the following statements:
delete from task_locks where passport 'master_lock'
update task_locks set lock_type = 0
Step to Delete, from a Metric Store, All Locks Created by a Specific Data Integration
Service Instance
• Execute the following statements:
delete from task_locks where lock_comment = ''
update task_locks set lock_type = 0
Step to Delete, from a Metrics Store, the Lock for a JBLP Task Step Created by a
Specific Data Integration Service Instance
• Execute the following statement:
delete from task_locks where lock_type = and lock_comment
=
where the values for and can be
determined by querying the task_locks table
Failed to Release Old Database Locks Where DIS ID Is: dispatcher
Note: This topic will be added to the Cognos 8 Troubleshooting Guide in a future release.
This error occurs when the lock for an automated procedure failed to clear.
The system administrator must remove old locks by stopping and starting the service or manually
clearing the lock (p. 45). For information about stopping and starting a service, see the
Administration and Security Guide.
QE-DEF-0177, UDA-SQL-0114, UDA-SQL-0458, and UDA-SQL-0475 Errors
When Running a Report
Note: This topic will include the following correction in the next version of the Cognos 8
Troubleshooting Guide.
The recommended maximum sort buffer size will be changed from 512 MB to 16 MB.
Series 7 Namespaces Do Not Initialize When Services are Started
Note: This new topic will appear in the Troubleshooting Guide and the Cognos Configuration
User Guide in a future release.
To address an issue related Series 7 namespaces, a new setting called
Series7NamespacesAreUnicode has been added to Cognos Configuration. This setting instructs
the Cognos 8 Series 7 provider to enable UTF-8 processing on the namespace data.
46

Cognos 8 Documentation Updates
UTF-8 processing is only available with Series 7 namespaces of version 16.0 and above. For other
versions, the behavior and actions are as follows:
• In a multi-code page environment, do not disable the setting or the server may fail.
• If the system finds a Series 7 version 15.2 namespace and the Series7NamespacesAreUnicode
setting is enabled, Cognos 8 reverts to disabled behaviour.
• If you have a mixed namespace environment, that is, a directory server with both version15.2
and version 16.0 namespaces, the version 15.2 namespace may not initialize. In this case, you
must disable the Series7NamespacesAreUnicode setting.
Cognos 8 Installation & Configuration Guide
This section contains additions and corrections that will appear in the next version of the
Cognos 8 Installation and Configuration Guide.
Create Databases for the Content Store and Metric Store
This topic will include the following steps in the next version of the Cognos 8 Installation and
Configuration Guide.
497970
Steps for the Metric Store on Oracle If the Database Does Not Exist
1. Log into the Oracle server as a user that belongs to the ORA_DBA group on Windows or the
dba group on UNIX.
2. Navigate to the c8_location/configuration/schemas/cmm/oracle directory, and run the
cmm_create_db.cmd script by typing the following command:
cmm_create_db sid path database_version [user_to_create]
Use the following values in your command:
• sid is the new database that will be created.
• path is the path where the data files will be created.
• database_version is the version of the Oracle software that is installed. For example,
oracle9 or oracle10.
• user_to_create is the user created by the script and given database owner permissions.
This value is optional.
3. Determine which user account Metric Studio will use to access the database.
The user account must be the database owner (dbo) or aliased to the database owner.
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.
Setting Up Trigger-based Scheduling
Note: This enhanced topic will appear in the Administration and Security Guide in a future
release.
To schedule an entry based on an occurrence and confirm trigger-based scheduling, you must have
read, write, execute, and traverse permissions. You also require the following access permissions
for all data sources used by the entry.
• dataSource - Execute and Traverse
• dataSourceConnection - Execute and Traverse
With only Execute access, you are prompted to log on to the database.
• dataSourceSignon - Execute
Before setting up trigger-based scheduling, ensure that your credentials exist and are up to date.
Readme 47

Cognos 8 Documentation Updates
Tip: Click Preferences, click the Personal tab, and then click Renew the credentials.
Follow this process to set up trigger-based scheduling:
❑ Schedule an entry based on the occurrence.
❑ Have your administrator set up the trigger occurrence on a server. For more information, see
the Administration and Security Guide.
Trigger occurrences can also be set up by an SDK developer using the Cognos 8 Software
Development Kit (SDK). For more information, see the Developer Guide.
If you are an administrator, you can disable trigger-based scheduling. See the Administration and
Security Guide.
DB2 OLAP Data Sources and Scenario Dimensions
Note: This topic will include the following correction in the next version of the Cognos 8
Administration and Security Guide.
SCENARIO_DIMENSION should be COGNOS_SCENARIO_DIMENSION.
Balanced Hierarchies Not Determined by DB2 OLAP Provider
Note: This topic will be added to the next version of the Cognos 8 Administration and Security
Guide.
DB2 OLAP Provider does not determine if a hierarchy is balanced or unbalanced. It considers all
hierarchies as being unbalanced by default.
In a balanced hierarchy, each path descends to the same depth while the branches in an
unbalanced hierarchy descend to different levels.
Steps to Specify Balanced Hierarchies
1. Ask the database administrator to create a special User Defined Attribute (UDA) named
COGNOS_HIERARCHY_BALANCED in the outline of the DB2 OLAP database. The UDA
is created for the root member of the corresponding dimension containing a balanced
hierarchy.
2. Set the attribute to 1.
Specify Measure Formats
Note: This topic will be added to the next version of the Cognos 8 Administration and Security
Guide.
To improve the readability of the values reported, you can specify an alternative format string for
any measure. Define a UDA for nonlabel members in the Account dimension:
COGNOS_FORMAT=format_string
The format_string value can be any one of the predefined number formats listed in the table
below. You can use a preset numeric format to show values as millions (M) or thousands (K). For
example, 1,801,791 can be shown as 1.8M or 1,801.8K.
The predefined format strings are as follows:
Format Option Sample Value Example
General 1000000 1000000
0 1000000 1000000
#,##0 1000000 1,000,000
$0 1000000 $1000000
$#,##0 1000000 $1,000,000
0% 1000000 100000000%
%0 1000000 %100000000
48

Cognos 8 Documentation Updates
0E+000 1000000 1E+006
0K 1000000 1000K
#,##0K 1000000 1,000K
K0 1000000 K1000
K#,##0 1000000 K1,000
$0K 1000000 $1000K
$#,##0K 1000000 $1,000K
0M 1000000000 1000M
#,##0M 1000000000 1,000M
M0 1000000000 M1000
M#,##0 1000000000 M1,000
$0M 1000000000 $1000M
$#,##0M 1000000000 $1,000M
With the exception of the General format string, you can also preset the number of decimal places
to show, using the format string ~n, where n is the number of decimal places. For example,
1,801,791 can be shown as $1,801,791.00 using the format string $#,##0~2. If you do not want
any decimal places, end the format string with ~0.
If your client application uses a different locale, you must replace the Currency ($), Thousands (,)
and Decimal (.) symbols in the format_string value for the COGNOS_FORMAT UDA with the
corresponding locale symbols in effect for the client application.
If you do not specify the number of decimal places to show, or if the format string does not match
one of the predefined values (including locale symbols), the General format string is used by
default.
You can apply a different format for each measure. The following illustrates some examples of
how you can apply different formatting to different measures:
Measure
Applied Format
Measures (Account dimension) COGNOS_FORMAT=#,##0
Units
COGNOS_FORMAT=#,##K
Costs
COGNOS_FORMAT=$#,###
Profits
COGNOS_FORMAT=0%
Cognos 8 Report Studio User Guide
This section contains additions and corrections that will appear in the next version of the
Cognos 8 Report Studio User Guide.
Controlling the Rows Per Page for Multiple Containers in HTML and PDF
Note: This topic will be added to the Running a Report section in the Report Studio User Guide in
a future release.
If you have more than one data container in a report, such as a list and a crosstab, you can control
how the report is rendered in HTML and PDF by setting the Rows Per Page property for each
container.
Cognos 8 uses the following rules when rendering reports in HTML and PDF:
• If the Rows Per Page property is not set for any of the data containers, 20 rows per page are
rendered in HTML and each page is completely filled in PDF. The first data container is
rendered until there is no more data, followed by the next container, and so on.
Tip: The number of rows that appear on a PDF page depends on the font size set in the report.
Readme 49

Cognos 8 Documentation Updates
• If the Rows Per Page property is set for each data container, the specified numbers of rows are
rendered in HTML and PDF on each page until there is no more data.
• If the property is set for only some of the containers, the specified numbers of rows are
rendered in HTML and PDF on each page until there is no more data. For the remaining
containers, 20 rows per page are rendered on each page in HTML and each page is completely
filled in PDF.
For example, you have two lists, List1 and List2. You set the Rows Per Page property to 5 for
List1. When you run the report in HTML, the first page contains the first 5 rows from List1
followed by the first 15 rows of List2.
• If no data is returned for a data container, an empty container is rendered.
Creating Charts Using an SAP BW Data Source
Note: This topic will be deleted in the Report Studio User Guide in a future release.
If you create charts using an SAP BW data source, and the fact query contains currency values, the
currency format may be lost in the chart. To restore the currency format, edit the Data Format
property of the fact query item and set the format type to currency.
If a fact query item contains values in multiple currencies, only the currency of the first value is
applied to the chart.
Creating Burst Reports Using a Dimensional Data Source
Note: This corrected topic will appear in the Report Studio User Guide in a future release. The
title of the topic changed from Creating Burst Reports Using an SAP BW Data Source.
You can burst a report using a dimensional data source by using burst information stored in the
data source. We assume that you do not want to append bursting information to existing
dimensional data sources. The solution is to create a relational data source that contains the burst
information.
To burst a report using a dimensional data source, do the following:
❑ In Framework Manager, include both the dimensional data source that is the basis for
reporting and the relational burst table in the model.
For more information about models, see the Framework Manager User Guide.
❑ In Report Studio, create a master-detail report in which the master query drives the report of
interest and the detail query contains the burst information.
The master query must be grouped by a data item that you are bursting on and that has a
corresponding data item in the relational burst table.
Author the detail query against the relational burst table. The burst table must contain two
columns, the data item corresponding to the one used in the master report for bursting, and
the data item that contains the recipient information. The recipient can be an email address or
an expression that results in a search path to an object in Content Manager, such as an
account, group, role, contact, or distribution list.
For more information about master-detail queries, see Create a Master Detail Relationship.
❑ Ensure that the detail query, which must be evaluated by Cognos 8 when the report is
executed, is not visible:
• Place a list that is based on the detail query in a conditional block for which the box type
is set to None.
• Link the master and detail queries using the following expression:
[Master Burst Key] = [Detail Burst Key]
When you set the burst options for the report, the master query provides the data items for the
burst key, and the detail report provides the data items for the burst recipients.
Using the Expression Editor
Note: This topic will include the following corrections in the next version of the Framework
Manager User Guide and the Report Studio User Guide.
50

Cognos 8 Documentation Updates
This topic currently states the following:
Note that SAP BW does not support any of the summary functions, constructs, and common
functions, nor many of the operators and constants, that are listed in this appendix.
The text will be changed to the following:
SAP BW does not support all operators or summaries. This can be confusing if you have
imported SAP BW metadata and non-SAP BW metadata into the same model.
SAP BW does not support the following operators:
• contains
• ends with
• like
• lookup
• starts with
SAP BW does not support the following member summaries:
• date-time
• interval
• interval month
• interval day
• interval day to hour
• interval day to minute
• interval day to second
• interval hour
• interval hour to minute
• interval hour to second
• interval minute
• interval minute to second
• interval second
• interval year
• interval year to month
• time with time zone
• timestamp with time zone
Cell values are date, number, or time. Attribute values are strings.
Cannot View Burst Report
Note: This topic will be added to the Troubleshooting section in the Report Studio User Guide in
a future release.
When you burst a report, each burst output is sent to the associated list of recipients. If a list of
recipients contains invalid entries, the following occurs:
• The burst output is not saved to Content Manager.
Consequently, you cannot view the burst output in Cognos Connection.
• If you choose to send the output by email, only valid recipients will receive an email.
Although the output is sent as an attachment if you select the Attach the report check box, no
link is generated if you select the Include a link to the report check box.
• The following error message appears in the run history for the report, where parameter 1 is
the burst key, parameter 2 is the list of recipients, and parameter 3 contains the error messages
returned by Content Manager:
An error occurred while saving the output for the burst instance with the recipients (). Here are the details:
Note: The list of recipients includes both the valid and invalid recipients.
Readme 51

Cognos 8 Documentation Updates
For example, a report is set up to burst on Country, and the recipients are managers. Running the
report produces the following countries and recipients:
• Canada: John, Mary
• U.S.: Peter, Frank
• France: Danielle, Maryse
Frank is an invalid recipient. The burst outputs for Canada and France are saved to Content
Manager, but not the U.S. output. If you choose to send an email to each recipient and you
selected the Include a link to the report check box, the email to Peter will not contain a link to the
output for US. The error message that is generated will contain Peter and Frank as values for
parameter 2 with no indication as to which is invalid.
To resolve the problem, do the following:
Steps to Correct or Remove Burst Recipients
1. View the error message in the run history for the report.
2. From the list of recipients, determine which recipients are invalid.
You may need to consult with your administrator to find out which recipients are invalid.
3. Correct or remove the invalid recipients.
Correcting or removing invalid recipients will depend on how the list of recipients was
defined, such as through a calculated field or a burst table.
4. Run the report again.
Cognos 8 Query Studio User Guide
This section contains additions and corrections that will appear in the next version of the
Cognos 8 Query Studio User Guide.
Format Rules for Calculations Returning Number Data Types
Note: This topic will be added to the Add a Calculation to a Report section in the Query Studio
User Guide in a future release.
When you create a calculation that returns a number, the formatting of the resulting column is
based on
• the calculation operation
• the format of the parent column or columns
• the number of decimals specified when a value is typed in the Number box
Note that all non-numeric format elements are ignored when creating the calculation format.
Sum, Difference, Maximum, Minimum
The following applies when the calculation operation is sum, difference, maximum, or minimum:
• If all calculation parents are percentages, the resulting column will also have a percentage
format.
• If all calculation parents are currency formats with the same currency code, the resulting
column will have the currency format with that currency code.
• For all other cases, the resulting column will have the number format.
• The number of decimals of the resulting column is set to that of the parent that has the largest
number of decimals.
• All other formatting that is identical in all parents is passed to the resulting column.
Product
The following applies when the calculation operation is product:
• If all calculation parents have the number format, the resulting column will also have the
number format
52

Cognos 8 Documentation Updates
• If the calculation parents are a mix of number and percent formats, the resulting column will
have the percent format
• If the calculation parents are a mix of currency and number or percent formats, the resulting
column will have the currency format if all currency formats have the same currency code.
Otherwise, the resulting column will have the number format.
• If all calculation parents are percentages, the resulting column will also have a percent format
• If the calculation parents are a mix of more than two format types, or some parents are
unformatted, the resulting column will have the number format.
• The number of decimals in the resulting column is set to that of the parent that has the largest
number of decimals or to the number typed in the Number box, whichever number is higher.
• All other formatting that is identical in all parents is passed to the resulting column.
Division, Average
The following applies when the calculation operation is division or average:
• If all calculation parents have the number format, the resulting column will also have the
number format.
• If the calculation parents are a mix of number and percent formats, the resulting column will
have the percent format.
• If the calculation parents are a mix of currency and number or percent formats, the resulting
column will have the currency format if all currency formats have the same currency code.
Otherwise, the resulting column will have the number format.
• If all calculation parents are percentages, the resulting column will also have a percent format.
• If the calculation parents are a mix of more than two format types, or some parents are
unformatted, the resulting column will have the number format.
• The number of decimals in the resulting column is set to a maximum of three.
• all other formatting that is identical in all parents is passed to the resulting column.
Percent, Percent Difference, Percent Total
The following applies when the calculation operation is percent, percent difference, or percent
total:
• The resulting column will have the percentage format.
• The number of decimals in the resulting column is set to two.
Percentile, Rank, Quartile, Quantile
The following applies when the calculation operation is percentile, rank, quartile, or quantile:
• The resulting column will have the number format.
• The number of decimals of the resulting column is set to two.
Round, Round Down
The following applies when the calculation operation is round or round down:
• The resulting column will have the same format as the parent.
Absolute
Power, Sqrt
The following applies when the calculation operation is absolute:
• The resulting column will have the same format as the parent.
The following applies when the calculation operation is power or sqrt:
• The resulting column will have the number format.
• The resulting column will have the same format as the parent, such as number of decimals,
sign, and scale.
Readme 53

Cognos 8 Documentation Updates
SAP BW
Note: This topic will be deleted in the Query Studio User Guide in a future release.
In charts created using an SAP BW data source, if a query item contains currency values, the
currency format may be lost in the chart. To restore the currency format, set the Format category
of the query item to Currency.
In charts created against an SAP BW data source, if a query item contains values in multiple
currencies, only the currency of the first value is applied to the chart.
Create a Simple Filter
Note: This topic will include the following additions in the next version of the Query Studio User
Guide.
When filtering a level or creating a prompt, click Show details to view parent information for each
member. The parent information appears in parentheses after each member. Viewing parent
information is useful when identical names exist. For example, the level City contains Paris
(Ontario) and Paris (France). If the data source you are using supports searching, parent
information also appears when you search for specific values by clicking Search for Values.
When filtering a dimension or hierarchy, members appear in a tree.
Cognos 8 Analysis Studio User Guide
Insert Data
This section contains additions and corrections that will appear in the next version of the
Cognos 8 Analysis Studio User Guide.
Note: The following information will be added to the Insert Data topic in the Analysis Studio User
Guide in a future release.
Note: When you insert items from a relational data source containing sparse data, you may see the
following error message:
PCA-ERR-0017 Unable to find the child name of missing member.
This error can occur when the underlying model does not use outer joins in the hierarchy
definition. For more information, see the Framework Manager User Guide.
Suppress Null Totals and Zero Totals
Note: This corrected topic will appear in the Analysis Studio User Guide in a future release.
To reduce clutter in an analysis, you can suppress items where the total results in a zero or null
value.
You can suppress rows, columns, or both. For example, you may want to suppress the data for a
customer with whom you have no interaction over a time period (nulls), but not for a customer
who repeatedly buys and returns goods, resulting in a net revenue of zero dollars (zeros).
Note: When sets are stacked in rows or columns, then suppress totals is not available.
Steps
1. Click the suppress items button on the toolbar.
2. Choose where to apply the suppression:
• Apply to Rows Only
• Apply to Columns Only
• Apply to Rows and Columns
3. Choose a suppression option to apply:
• Total is Null
54

Cognos 8 Documentation Updates
Create a Custom Set
• Total is Zero
• Total is Null or Zero
4. A suppression icon next to the item label in the overview area indicates that suppression is
applied.
Tip: To remove suppression, repeat step 1 and click No Suppression.
Note: The following information will be added to the Create a Custom Set topic in the Analysis
Studio User Guide in a future release.
You cannot save a set as a custom set under the following conditions:
• The analysis contains a context filter based on a dynamic definition, such as a calculation or
top or bottom filter, rather than a static item or items, such as 2005, or Camping Equipment
and Personal Accessories.
• The set contains a calculation that references multiple dimensions, such as ranking
calculations, or a percent of base calculation that references an item from the opposite axis of
the crosstab.
• The set contains a user-defined filter based on a calculation.
• The set is expanded to show more than one level.
Producing Reports in Microsoft Excel Format
Note: The following information will be added to the appendix Producing Reports in Microsoft
Excel Format in the Analysis Studio User Guide in a future release.
Using Reports Saved in XLS Format
Charts and Custom Colors
Repeating Pie Charts
If you open a report that was saved in XLS format or run a report in XLS format, and security
settings in your browser are set so that you are prompted to open or save the report, do not click
Save. If you save the report, the spreadsheet content will not be saved. This is because Excel
reports in Office 2000 HTML format use relative paths to the spreadsheets. The relative URL
paths are no longer available when you open a saved XLS report.
Instead, click Open first and then choose to save the report.
When running a report containing a chart in Excel format, the chart requires that 16 Cognos 8
default colors be added to the Excel custom palette. 16 is the maximum number of colors that
Excel accepts in its custom palette. If the report contains a report object that uses an additional
custom color, Excel cannot add it to the custom palette. Excel will attempt to match the custom
color to one of its available standard colors. As a result, the report object will be a few shades
away from the custom color used.
If you have a report that has repeating pie charts, and you define a chart title, Excel will show
each pie with a title that is a concatenation of the chart title and the data series. For example, if
the chart title is Quantity Sold by Order Method and Product Line and the data series is Order
method, the title of each pie in Excel will be
Quantity Sold by Order Method and Product Line, order method
Discrete Axis Label Skip Control in Charts
In Cognos 8 charts, you can control the skipping of discrete axis labels. This feature is not
supported in Excel charts.
Text Strings with More Than 255 Characters
Cells in Microsoft Excel have a limit of 255 characters. If your report contains text strings that are
longer than 255 characters, they will be formatted as text and appear as ######.
Readme 55

Cognos 8 Documentation Updates
Insert Data
Note: The following information will be deleted from the Insert Data topic in the Analysis Studio
User Guide in a future release.
When you insert items from a relational data source containing sparse data, you may see the
following error message:
PCA-ERR-0017 Unable to find the child name of missing member.
This error can occur when the underlying model does not use outer joins in the hierarchy
definition. For more information, see the Framework Manager User Guide.
Sets
Note: The following information will be added to the Sets topic in the Analysis Studio User Guide
in a future release.
In the crosstab, you can create a new selection-based set from an existing set by selecting the
members you want, then clicking Keep in the right-click menu. The new selection-based set
replaces the set from which it originates.
Cognos 8 Metric Studio User Guide for Authors
This section contains additions and corrections that will appear in the next version of the
Cognos 8 Metric Studio User Guide for Authors.
Weeks in Gregorian Calendars
Note: This topic will be added to the Metric Studio User Guide for Authors in a future release.
Metrics Manager lets you include weeks in Gregorian calendars. Unlike manufacturing calendars,
these weeks can begin in one month, quarter or year, and end in another. This can affect how
Metrics Manager loads and represents data.
Weeks Cannot Rollup to Higher Period Levels
Because a week might not end in the same month, quarter, or year in which it began, you cannot
calculate higher period level totals by rolling up weekly totals. Therefore, if weeks are the lowest
level in the calendar, you must set the data load level of the metric to a value other than weeks.
Regardless of this setting, you can always load data at the week level.
Load Months or Days to Get High-Level Rollups
To calculate high-level rollups, you must load data at a level that does not span higher periods.
• Loading Days
In a calendar that includes days, you can load data at the daily level so that Metric Manager
can calculate rollups for weeks, months, quarters and years.
• Loading Weeks and Months
In a calendar whose lowest level is weeks, you must load data at a higher level, such as
months, so that Metric Manager can calculate rollups for quarters and years.
Weeks Only Belong to a Month for Navigation Purposes
Each week belongs to a month so that users can navigate to a specific week in the calendar. This
setting is for navigation purposes only and does not imply any rollup from weeks to months.
When you create a Metric Package you can set a week to belong to:
• the month in which it begins
• the month in which it ends
• the month to which the majority of its days belong
This setting also controls how many weeks are in a year.
56

Cognos 8 Documentation Updates
Weeks Affect Trends Calculations
When you set a trend to Calculate trend by comparing to: Previous period, Metric Studio
calculates trend arrows by comparing:
• the same day of the previous week, at the daily level
• the same week of the previous month, at the weekly level
Metric Studio uses the value set in the calendar wizard to determine the week of the month.
Gregorian Weeks Are Not Supported in Custom Calendars
You cannot create a custom calendar that contains weeks that span higher-level periods. This is
only supported through the Metric Package calendar wizard.
Framework Manager User Guide
This section contains additions and corrections that will appear in the next version of the
Framework Manager User Guide.
Checking Imported Metadata
Note: This topic will include the following additions in the next version of the Guidelines for
Modeling Metadata, a separate documentation piece as well as a chapter in the Framework
Manager User Guide. If you are using an Oracle database, see "Full Outer Joins and
Oracle" (p. 7) for more information.
483743
Sparse Data
When modeling for analysis or reporting, it is important to consider the nature of the business
questions versus the nature of the data source.
A common scenario is that a relationship between a dimension and a fact table in a star schema is
optional. This means that not every dimensional member is mandatory in the fact table. OLAP
engines compensate for this by inserting an appropriate value when creating the OLAP structure
for any dimensional intersection points that do not have data.
When modeling, it is common to override optional relationships between dimensions and facts for
improved performance. However, when performing analysis or reporting on sparse data where
you require information about dimensional members that have no facts, outer joins must be
enabled to ensure that data is returned for valid dimensional intersection points.
For example, an Analysis Studio user wants to create this report:
2004 2005
Canada 1,000,000
Mexico 500,000 750,000
United States 1,000,000 2,000,000
To enable outer joins, we recommend that you do the following:
• Check with your database administrator to ensure that the data source can support full outer
joins.
• Import metadata with outer joins enabled.
Moving a Framework Manager Model from One Relational Database to Another
Note: This topic will be added to the next version of Guidelines for Modeling Metadata, a
separate documentation piece as well as a chapter in the Framework Manager User Guide.
Readme 57

Cognos 8 Documentation Updates
There are several things to consider when moving a Framework Manager model from one
relational database to another. Unlike changing from one identical database to another on the
same platform, it may not be sufficient to simply change the data source connection information.
To move a model from one relational database to another, do the following:
❑ Evaluate the DDL to determine portability for physical names by
• constraining physical names to a lowest common denominator, such as 31 characters
• avoiding using reserved words as names
• using a consistent case on names, such as all lowercase
❑ Evaluate the DDL to determine portability for database qualification.
❑ Evaluate the DDL to determine portability for data types in terms of compatibility and the
precision and scale of datatypes.
❑ Review any native SQL statements in your models and reports for relational-specific syntax
that may or may not be supported.
❑ Review usage of vendor-specific functions.
There may not be an equivalent vendor function or common function. A common function
that is unsupported by the relational database may result in local processing that did not
previously occur.
❑ Rebuild the physical tables.
When you import tables, Framework Manager imports physical information about the tables
and columns that is used internally at run time. For example, collation information is
reconciled only by rebuilding the physical tables.
❑ Test the moved model.
There will be other differences, such as performance characteristics, how data is ordered
based on collations, and so on, that are revealed only by testing.
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.
58

Index
Symbols
.cmn
DB2, 31
.db files, 14
.pro files, 58
A
a socket reported a communication error, 15
accented characters
not displayed properly, 9
accessing data sources, 18, 19
actions
printing, 32
administration
Metric Studio strategy maps not rendered, 16
Administration and Security Guide, 47
administrative privileges, 41
Adobe PDFs
problems printing, 16
Adobe Reader
versions required for printing reports, 17
agent run fails, 25
AIX
server-side printing, 17
Analysis Studio
context filter limitations, 25
custom sets, 25
dashes appearing instead of values, 25
limitations, 25
Analysis Studio quick tour, 58
Analysis Studio User Guide, 54
Apache gateway
problems starting, 10
as percentage
values, 26
attribute-based sorting, 26
attributes
grouping on, 22
authentication
Series 7 namespaces, 46
auto populate option
removal, 24
B
backslashes appear instead of currency, 11
balanced hierarchies
DB2 OLAP, 48
blank values
appearing instead of totals, 23
burst reports
creating using a dimensional data source, 50
bursting
MOLAP data, 23
C
calculated key figures, 20
calculated metrics
constants, 28
calculated summaries
Query Studio and Report Studio, 23
calculations
CognosViewer, 26
commas, 31
format rules, 52
SAP BW data sources, 19, 20
calendar
extending, 31
incorrect time span, 32
years, 32
calendar data
clearing in Metric Studio, 34
calendar settings
metric types, 28
cert7.db file, 14
changing
package reference, 26
character display
incorrect, 29
characters
unrecognized Japanese, 35
characters improperly displayed, 9
chart
creating from an existing query, 24
charts not appearing, 15
Clear calendar data option, 33
clear metric history and calendar data
properties lost, 33
Cognos 8
integration with Cognos Planning, 13
package, 35
publishing from PowerPlay Enterprise Server, 13
Cognos Configuration
reconfiguring, 34
Cognos Connection
test data source fails, 27
Cognos Planning
integration with Cognos 8, 13
Cognos Planning - Contributor
connecting to data source, 15
Cognos Viewer
calculations, 26
configuration settings, 26
Readme 59

Index
connections
ODBC, 34
context filter limitations, 25, 26
copyright, 2
corrupted
metric store, 27
creating
burst reports using a dimensional data source, 50
simple filters, 54
crosstabs
aggregate values not appearing, 23
parent-child currency hierarchy, 22
cubes
apostrophes in package name, 35
short names unsupported, 35
taking too long to open, 44
unrecognized Japanese characters, 35
currencies
filtering in Query Studio, 22
currency
won, 11
yen, 11
custom calendars
import errors, 30
custom formatting
not appearing for empty cells, 20
custom set
creating, 55
custom sets in Analysis Studio, 25
D
dashes
appearing instead of values in Analysis Studio, 25
data export
upgrade, 28, 29
data removed from metric data store, 33
data sources
connecting to Cognos Planning - Contributor, 15
unable to open a cube using 8.2 DB2 OLAP, 18
unable to open a cube using Essbase 7.1, 18
database character set
unicode, 31
datatypes
incompatible, 41
date display
incorrect, 30
date format
.cmn, 31
dates
creating for object extracts, 35
DB2
date format, 31
import null values, 32
incorrect average value, 19
incorrect count value, 19
metric lists display, 32
DB2 Cube Views
functional dependencies, 39
roles, 39
DB2 data sources
problems accessing, 18
DB2 OLAP
query failure using DB2 OLAP Server, 18
unable to load library, 9
unable to open a cube using 8.2 DB2 OLAP, 18
DB2-ERR-0028, 9
determinants, 39
diagrams
missing, 28
dimensional data
filtering, 54
dimensional data source
creating burst reports, 50
dimensions
order of members, 40
display
metric lists, 32
distributed installation
imports and exports, 31
document
version, 2
documentation
Administration and Security Guide, 47
Analysis Studio quick tour, 58
Analysis Studio User Guide, 54
broken links, 17
cubes taking too long to open, 44
Getting Started, 43
Installation and Configuration Guide, 47
log files, 44
Metric Studio User Guide for Authors, 56
problems printing PDFs, 16
Query Studio User Guide, 52, 57
quick tours, 17
Report Studio User Guide, 49
Troubleshooting Guide, 43
documentation CD, 17
documentation updates
Framework Manager User Guide, 33, 57
double-byte characters
improperly displayed, 9
DPR-ERR-2002 error message, 11
drilling down
cannot create custom groups in Query Studio, 21
drill-through performance, 17
E
embedded externalize method, 39
errors
a socket reported a communication error, 15
custom calendar import, 30
DB2-ERR-0028, 9
QE-DEF-0478, 21
SDK Custom Authentication JDBC Provider sample, 14
syntax error on line 557, 10
TR0118, 39
Essbase
incorrect average value, 19
incorrect count value, 19
EssBase 7.1
unable to open a cube, 18
60

Index
Excel Data sources
Transformer error, 14
execution error
UDA-SQL-0564, 34
expand command in Analysis Studio, 25
export
distributed installation, 31
failing in a distributed installation, 29
exporting
IQD files, 40
expression editor
commas, 31
expressions, 38
extend
calendars, 31
externalizing query subjects, 39
extracts
unrecognized Japanese characters in cubes, 35
F
file not found errors, 17
files
adding multiple IQD, 36
filtering
currencies in Query Studio, 22
dimensional data, 54
filters
invalid, 35
filters not working in sectioned reports, 22
format rules
calculations, 52
format strings, 48
Framework Manager
IQDs and Oracle stored procedures, 39
issues, 38
missing connections and credentials, 34
problems using Visual SourceSafe 6.0, 41
testing queries, 39
TR0118 error, 39
unable to load DB2 OLAP library, 9
user language preference, 34
Framework Manager User Guide
documentation updates, 33, 57
full outer joins
Oracle, 40
functional dependencies, 39
functions
order of members, 40
G
gateways
problem starting Apache, 10
Getting Started
documentation updates, 43
group types
not importing correctly, 29
grouping
first level in a list, 22, 24
on an attribute, 22
grouping columns
SAP BW data sources, 19
H
hierarchies
DB2 OLAP, 48
hierarchy node prompts, 20
history data
clearing in Metric Studio, 34
I
import
custom calendar errors, 30
distributed installation, 31
failing in a distributed installation, 29
group types, 29
null values in DB2, 32
Import Source
loading data, 27
Impromptu Web Reports
conflict with Apache gateway, 10
incorrect average value using DB2 or Essbase, 19
incorrect count value using DB2 or Essbase, 19
index update options not available, 16
initialization, namespaces, 46
initialize
Oracle metric store, 30
Installation and Configuration Guide, 47
installation and configuration issues
cannot load Apache module, 10
cannot load DB2 OLAP library, 9
run-time errors, 10
installing
Cognos 8 on Linux, 9
Integrated Windows Authentication
issues, 14
interactions
with Impromptu Web Reports, 10
invalid expressions, 38
IQD files
adding multiple, 36
problems exporting, 40
replace function, 36
issetup
corrupt Japanese characters, 11
J
Japanese characters
unrecognized in cube extracts, 35
Japanese characters corrupted, 11
Japanese currency, 11
Japanese extracts
MS SQL server, 34
Oracle, 35
JDBC drivers, 14
jobs
index update options not available, 16
join relationships
creating in Report Studio, 23
joins
Oracle, 40
outer, 57
Readme 61

Index
K
key figures, 20
key3.db file, 14
known issues
administration, 15
Analysis Studio, 25
Cognos Connection, 18
DB2 data sources, 18
Event Studio, 24
Framework Manager, 38
general, 16
installation and configuration, 9
Metric Studio, 27
Query Studio, 21
Report Studio, 23
SAP BW data sources, 19
security, 14
Series 7 integration, 13
Korean currency, 11
L
languages
OLAP data sources, 26
LDAP namespaces
starting Cognos 8, 14
levels
DB2 Cube Views, 39
limitations in Analysis Studio, 25
Linux
characters not displayed properly, 9
List view in Metric Studio, 33
lists
grouping on first level, 22, 24
loading data
Import Source, 27
log files
documentation, 44
logging on
problems, 15
M
measures
format strings, 48
SAP BW data sources, 19
members, order of, 40
metadata query failure with DB2 OLAP server, 18
metric lists
display, 32
metric store
cannot access, 30
corrupted, 27
permissions, 28
Metric Studio
additional columns in Project tab-delimited file, 58
List view, 33
Metric Studio strategy maps
in Microsoft Excel reports, 16
Metric Studio User Guide for Authors, 56
metric type
calculations, 31
metric types
calendar settings, 28
recreating after clearing data, 34
Microsoft Excel reports
Metric Studio strategy maps do not appear, 16
migrating
models, 57
migration
final data export, 28, 29
models
migrating from one relational database to another, 57
MS SQL server
Japanese extracts, 34
N
namespaces and initialization, 46
no data
rollups, 34
null values
import, 32
numeric formats, 48
O
object extracts
creating dates, 35
object properties
lost, 33
ODBC connection, 34
OLAP data sources
languages, 26
Oracle
database, 30
full outer joins, 40
Japenese extracts, 35
metric store initialization, 30
NLS_LANG environment variable, setting, 27
NLS_LANG setting, 35
replace function, 36
running on 10g, 27
order of members, 40
outer joins
Oracle, 40
sparse data, 57
P
package reference
changing, 26
packages
Cognos 8, 35
import source security, 35
parent-child currency hierarchy
in crosstabs, 22
PDF
unsupported style properties, 23
performance
drill-through, 17
permissions
metric store, 28
pivoting to a crosstab, 24
62

Index
ports
setting the maximum number for program use, 18
PowerPlay 7 reports
cannot open, 13
PowerPlay Enterprise Server
publishing to Cognos 8, 13
printer friendly page
character display, 29
printing
actions, 32
Adobe PDFs, 16
after restarting dispatcher, 27
empty lists, 32
projects, 32
printing reports
Adobe Reader versions required, 17
problems accessing DB2 data sources, 18
problems accessing SAP BW data sources, 19
projects
printing, 32
synchronizing, 41
prompts
hierarchy node, 20
Published PowerPlay 7 reports
cannot open, 13
publishing to Cognos 8 from PowerPlay Enterprise Server, 13
Q
QE-DEF-0478 error, 21
quarter rollup
no data, 34
query failure with DB2 OLAP server, 18
Query Studio
calculated summaries, 23
filtering currencies, 22
filters not working in sectioned reports, 22
unable to create custom groups, 21
Query Studio User Guide, 52, 57
query subjects
externalizing, 39
quick tours
documentation update, 58
problems with text, 17
R
regular dimensions
order of members, 40
relational models
migrating, 57
relationships
creating joins in Report Studio, 23
replace function
IQD, 36
Report does not run as scheduled, 16
Report Studio
aggregate values not appearing, 23
bursting on MOLAP Data, 23
calculated summaries, 23
creating join relationships, 23
Key Transformation validation level returns partial
information, 24
Report Studio (cont'd)
style properties not supported, 23
Report studio
pivoting to a crosstab, 24
Report Studio User Guide, 49
report styles
defaults not preserved, 16
ReportNet 1.1 documentation updates
Framework Manager User Guide, 33, 57
ReportNet 1.1 issues
Framework Manager issues, 38
reports
formatting not preserved, 16
missing, 28
report execution fails, 10
repository
synchronizing projects, 41
roles, 39
run-time errors, 10
S
samples
SDK Custom Authentication JDBC Provider, 14
SAP BW
key figures, 20
summaries and functions, 50
SAP BW data sources
calculations, 19
grouping columns, 19
hierarchy node prompts, 20
measures, 19
problems accessing, 19
sectioning reports, 20
summary rows, 20
unit formats, 20
SDK Custom Authentication JDBC Provider sample, 14
sectioned reports, 22
sectioning reports
SAP BW data sources, 20
security
issues with Integrated Windows Authentication, 14
issues with the SDK Custom Authentication JDBC
Provider sample, 14
LDAP namespaces, 14
problems logging onto a Series 7 namespace, 15
security issues
namespace configured with LDAP SSL is not available, 14
SDK, 14
using Integrated Windows Authentication, 14
Series 7 namespaces
authentication, 46
problems logging on, 15
Series7NamespacesAreUniccode, 46
server-side printing on AIX, 17
sets in Analysis Studio, 56
settings
Series7NamespacesAreUniccode, 46
simple filters
creating, 54
single signon
issues with Integrated Windows Authentication, 14
Readme 63

Index
socket reported a communication error, 15
sorting
attribute based, 26
sparse data, 57
SQL Server
importing group types, 29
testing datasource connections, 15
starting Framework Manager, 41
style properties missing in PDF reports, 23
summary rows
SAP BW data sources, 20
suppress items, 26
synchronizing
projects, 41
syntax error on line 557, 10
T
tasks, concurrent, 27
Teradata
executing a Framework Manager-based extract, 35
testing
models, 38
SQL Server datasource connections, 15
testing queries in Framework Manager, 39
text
problems in quick tours, 17
third-party data sources
8.2 DB2 OLAP, 18
EssBase 7.1, 18
third-party importing
expressions, 38
testing, 38
To-Date comparisons, 27
toolbar buttons, unable to launch, 17
total values
SAP BW data sources, 20
Transformer
using an IQD created in Framework Manager, 39
Transformer errors, 14
Troubleshooting Guide, 43
upgrading reports
incompatible datatypes, 41
V
values
as percentage, 26
version
document, 2
Visual SourceSafe
errors in Framework Manager, 41
W
Web servers
problems starting, 10
won character, 11
Y
year rollup
no data, 34
yen character, 11
U
UDA-SQL-0564
execution error, 34
unable to create custom groups, 21
unable to run reports, 10
unbalanced hierarchies
DB2 OLAP, 48
unicode
database character set, 31
unit formats
SAP BW data sources, 20
unreadable characters, 29, 30, 32
unsupported Cognos Planning 7.3 features, 13
upgrade
final data export, 28, 29
upgrading
reports, 16
using Oracle 10g Application Server, 11
upgrading ReportNet 1.1, 11
64