Cognos(R) 8 Business Intelligence...

Cognos(R) 8 Business Intelligence

README

Cognos(R) 8 Business Intelligence Readme

README

Product Information

This document applies to Cognos(R) 8 Version 8.2 and may also apply to subsequent releases. To check for newer versions of this document, visit the Cognos Global Customer Services Web site (http://support.cognos.com).

CopyrightCopyright (C) 2007 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; 6,986,135 B2; 6,995,768 B2; 7,062,479 B2; 7,072,822 B2.

Cognos and the Cognos logo are trademarks of Cognos Incorporated in the United States and/or other countries. All other names are trademarks or registered trademarks of their respective companies.

While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors or technical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information contained in this document.

This document shows the publication date. The information contained in this document is subject to change without notice. Any improvements or changes to either the product or the document will be documented in subsequent editions.

U.S. Government Restricted Rights. The software and accompanying materials are provided with Restricted Rights. Use, duplication, or disclosure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, or subparagraphs (C) (1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227-19, as applicable. The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803.

This software/documentation contains proprietary information of Cognos Incorporated. All rights are reserved. Reverse engineering of this software is prohibited. No part of this software/documentation may be copied, photocopied, reproduced, stored in a retrieval system, transmitted in any form or by any means, or translated into another language without the prior written consent of Cognos Incorporated.

Table of Contents

Introduction 9

Chapter 1: Cognos 8 Known Issues 11Installation and Configuration 11

Stability Problems with MS SQL Server Analysis Services 2005 in Cognos 8 11Cognos 8 Server May Fail to Start 11Unable to Load DB2 OLAP Library in Framework Manager 12Accented or Double-Byte Characters May Not Display Correctly When Installing Cognos

8 on Linux 12Non-ASCII Characters in Install Directory Will Cause Run-Time Errors 12Japanese Characters Corrupted When Running issetup 12Yen and Won Characters Appear as Backslashes in Charts and PDFs 12Cannot Publish Series 7 Cubes to Cognos 8 Following Upgrade 14Choosing Only One Language When Installing Cognos 8 Transformer and

PowerPlay 14Issues with IBM WebSphere 6.0 on AIX 5.3 15

Series 7 Integration 15Unsupported Cognos Planning 7.3 Features with Cognos 8 15

Security 15Existing Passwords May not Work in an SAP Namespace 15Users Are Repeatedly Prompted for Credentials When Trying to Log On to an SAP

Namespace 16Charts do Not Appear When Internet Explorer 6.x Security Level Set to High 16

Administration 16Unable to Connect to a Cognos Planning - Contributor Data Source 17

General 17Not Yet Optimized Cognos PowerCubes May Open Slowly in Cognos 8 17Drill-Through Performance Slower 18Changes to Decimals in Currency Formats 18Currency Values in a Report Appear as Numbers 19Different Results for List Reports and Crosstabs that Use the Same Set Expression 19Relationships Not Maintained in a Report With Overlapping Set Levels 19Ragged or Unbalanced Hierarchies Result In Unexpected Behavior 20Excel Functions Used in the MDX Result in Server Error 20Web Links Do Not Work In Acrobat 7.x 20Adobe Reader Versions for Server Printing on Windows 21Problems Using Web Help with an Apache Web Server 21Metadata Change in Essbase Not Reflected in Studios 21No Results are Returned for Footer Cells When Using Semi-Additive Measures in

Dimensionally Modeled Relational Data Sources 21DB2 Data Sources 22

Query Fails When Using DB2 OLAP Server 22Unable to Open a Cube Using 8.2 DB2 OLAP or EssBase 7.1 23

SAP BW Data Sources 23Incorrect Units of Measure in Calculations 24Grouping Columns That Have the Count Summary 24Missing Measures in Crosstab Reports 24Crosstab with the Same Dimension on Both Edges Returns No Data 24Custom Formatting for Empty Cells Does Not Appear in Cognos 8 24

Readme 3

Creating Sections on Reports That Access SAP BW Data Sources 24Summary Rows Return Incorrect Total Values 25Calculated Key Figures Appear with the Non-aggregate Icon 25Filter Expressions Using Report Items and Smart Prompts Do Not Return Values 25

Cognos 8 Business Intelligence Transformer 7.4 25Queries Against Multiple Hierarchies in the Same PowerCube Dimension Do Not

Execute 25Query Studio 26

Cannot Use Hierarchies from Dimensionally Modeled Relational Models 26Text and Border Styles Are not Applied to Empty Reports 26Functions not Available 26Unable to Insert Data Items from Two Hierarchies of a Single Dimension 26Background Color in Template Does not Appear 26Subtotals in Grouped Lists 27

Report Studio 27Unable to Run Cognos 8.2 Reports in Cognos 8.1 27Set Expressions That Depend on the Current Measure May Return Incorrect Data 27Running Totals Are Incorrect in Crosstab Reports 27Aggregate Values Are Not Appearing in Crosstabs 28Calculated Rollup Aggregate Type Is Computed in Different Ways 28Key Transformation Validation Level Returns Partial Information 28Pivoting to a Crosstab Shows the Member of the Attribute 28

Event Studio 29Error in AssignStaff Stored Procedure in ELM Returns Agent Sample 29Parsing Error When Passing Data From a Dimensionally Modeled Package 29

Analysis Studio 29Analysis Studio Limitations 29Error Occurs in Japanese Internet Explorer 7 When Running an Excel Report in Analysis

Studio 30The "More" Calculation in Analysis Studio May Return Non-intuitive Numbers 30Analysis Studio Shows the Wrong Currency Symbol 30Filter by Label or Attribute is Case Sensitive 31Cells with '- -' are Represented as NULLS in Export to Excel 31Context Filter Limitations 31Defining Languages for OLAP Data Sources 31Crosstab Shows Percentage But Chart Shows Values 32Analysis Studio Does Not Reflect Package Configuration Settings 32Analysis Studio Ignores Changed Package Reference in Cognos Connection 32Server Error When Sorting a Selection-Based Set by Attribute 32Suppress Items when Accessing MS Analysis Services Cubes May Produce Unexpected

Results 32Unable to Search in the Source Tree for Data Enclosed In Brackets When Using Microsoft

SQL Server Analysis Services 2000 32Report Options are Ignored When Running an Analysis in Report Viewer 32

Metric Studio 33Error When Viewing a History Chart or Diagram on a DB2 Server with the 8.2 JDBC

Driver 33The Setting to Show This Report in Lower-Level Scorecards Is Lost After Export and

Reimport 33The Setting to Show This Report on All Metrics of This Type Is Lost After Export and

Reimport 33Package Creation Fails If Default Oracle Permission Is Revoked 33Metrics Are Not Created on Scorecards 34Actions Loaded From File Do Not Trigger Watchlist Emails 34Errors When Loading Data with Timestamps into SQL Server 2005 34Recommended Patches for Oracle 10g 34

4

Oracle 9.2 Package Initialization Error if NLS_LANG Environment Variable is Not Set Appropriately Before Starting Up Cognos 8 Tomcat Server 35

Equations Using Only Constants are not Allowed in Calculated Metrics Types 35Content that uses double-byte characters displays as unreadable characters (Oracle) 35Right-clicking to Follow a Link in a New Web Browser Window Is Not Supported 35Full-width Tilde (Korean) Does Not Display Correctly After Import into IBM DB2 35Korean Full-width Tilde Changes to Half-width Tilde After Being Imported into a DB2

Metric Store 36Full-width Tilde and Full-width Hyphen Characters Change to the "?" Character After

Being Exported From a DB2 Metric Store with -Korean(EUC-KR)(DB2) Encoding 36

Unable to Delete Time Periods from the Calendar 36Metric Designer 36

Cannot Edit or Run an Extract 37Japanese Characters Do Not Display Correctly After Import into SQL Server 37Framework Manager - Import Source and Anonymous User Language Preference 37Framework Manager - Import Source Connections and Credentials 37Metric Filters are Still Invalid After Upgrading a Model and Retargeting Broken

References 37Problem Executing an Extract Created From a Framework Manager Model Using a

Teradata Database 38IQD Import Source - Error Reading IQD file that Contains the Oracle 'Replace'

Function 38Adding Multiple IQD files to an Import Source 38Data Sources Not Supported 39Filters on Parent-Child Hierarchies Are Not Supported for Dimensional (OLAP) Data

sources 39Error Occurs for a Metrics Extract Containing Static Text-type Scorecard Levels 39Metrics Extracts Containing Typed-in Constant Metric Attribute Values Do Not Deliver

Metrics for PowerCube Data Sources 39Construct Functions in Scorecard Identifier Expressions Not Supported for PowerCube

Import Sources 39Day Level Time Period Filter May Cause Metric Designer to Become Non-responsive 40When You Log off and Then Log on Using Different Credentials the Authentication

Information is Not Refreshed 40MUNs Have Changed in Filter Expressions in Extracts from Earlier Versions of Metric

Designer 40Computer Hangs When Executing a Metrics Extract 40

Framework Manager 40System Objects for SQL Server 2005 Do Not Appear 40Duplicate Schemas and System Tables When Using Teradata and Sybase 41Changes Made to a Child Segment Not Reflected in the Parent 41Running the BME Script Player Can Result in Errors 41Dynamic Retargeting of Query Items Fails 41Full Outer Joins Not Sent to Oracle 9 and 10G 42Framework Manager Hangs When Using the Isolation Level for Informix Data

Sources 42Error Results When Testing a User-defined Function in a Stand-alone Calculation 42Cannot Test the Key Figures Dimension with an Embedded Calculation 42Cannot Test a Calculation When the Active Language Is Not English 42Dimensional Functions and Members Are Not Always Supported 43Cannot Test a Dimension with an Embedded Filter That Refers to a Stand-alone

Calculation Returning a Member 43Cannot Specify the Order of Members When Defining a Level 44Dimension Appears Empty in Analysis Studio 44BEx Queries Do Not Pass Back Hierarchies in a Characteristic Structure 44Errors When Running a Report from the Find Report Dependencies Window 45

Readme 5

Insufficient Memory to Export a Large InfoCube 45Embedded Externalize Method Does Not Function 45Default Setting for SQL Generation Has Been Changed 45

Cognos 8 Go! Office 45Workbook Closes Unexpectedly If Name Contains Square Bracket 45Cannot Open a Report in Excel in Cognos Connection If You Have a COM Add-in

Workbook Open 45The Cognos Action Pane Disappears When Using the Smart Client and You Run a Report

in Excel in Cognos Connection 46No Report Content Is Imported When the Report Name Contains a Single Quote (') 46COC-ERR-2607 46Incorrect Format for the Prompt Value in Prompted Reports 46DPR-ERR-2079 Firewall Security Rejection Error While Running Report After Expired

Session 47Cognos 8 Go! Office Does Not Start in Microsoft Word 47

Chapter 2: Cognos 8 Documentation Updates 49General 49Build Application Wizard Help 49

Select the Application to Build 49Cognos 8 Architecture and Deployment Guide 50

Server Locale 50Cognos 8 Installation and Configuration Guide 50

Configure Cognos Components to Run Within the Application Server 50Enable or Disable Cognos 8 Go! Office Functionality for COM Add-in Users 51

Cognos 8 Administration and Security Guide 52Access Permissions 52Set Query Prioritization 52Model-based vs. Report-based Drill-through Access 54Members and Values 54Business Keys 54Scope 55Set Up Drill-through Access in a Package 55

Cognos 8 Analysis Studio User Guide 55Suppressing Empty Cells 55

Cognos 8 Analysis Studio Quick Tour 56Cognos 8 Event Studio User Guide 56Framework Manager User Guide 56

Upgrading the Model 56Converting Query Subjects with Dimension Information to Regular Dimensions 56Determinants 57Defining Determinants 57Work with SAP BW Data in Cognos 8 Planning 58

Cognos 8 Getting Started 58Cognos 8 Go! Office User Guide 59Cognos 8 Metric Studio User Guide 59

Equations (.equ) 59Equation Items (.eqi) 59

Cognos 8 Query Studio User Guide 59Cognos 8 Report Studio User Guide 59

ReportOption 59Applying Filters to Dimensional Reports 60Setting Object Properties 60Creating Burst Reports Using a Dimensional Data Source 60Connecting Queries Between Different Data Sources 61Remove Upgrade Messages 61Set Options 61

6

Report Studio Properties 61Visual Aids Button 62Set Up Drill-through Access in a Report 62

Cognos 8 Troubleshooting Guide 62

Chapter 3: Deprecation Notices 63Supported Environments 63Framework Manager Security Filters for SAP BW: Notice of Intent to Change the Default

Setting 63

Index 65

Readme 7

8

Introduction

This Readme contains late-breaking information, including installation issues, limitations, and known issues.

The documentation included in this release is current as of February 2007.

Visit the Cognos Global Customer Services Web site for• updates to this Readme and product documentation• the fix list, which is a list of the known issues that were addressed in this release

Updates to the software are made available on the Cognos Global Customer Services Web site (http://support.cognos.com). These updates contain the latest set of quality improvements that were completed after the release of this software. We recommend that you review these updates and apply them once you have completed the installation.

Readme 9

http://support.cognos.com/go/docs/cognos8_bi/8.2/rdm_cr_updates.html

http://support.cognos.com/go/docs/cognos8_bi/8.2/fix_list.html

http://support.cognos.com

Introduction

10

Chapter 1: Cognos 8 Known Issues

This section contains information about Cognos 8 BI known issues.

Installation and ConfigurationThis section contains known issues about installation and configuration.

Stability Problems with MS SQL Server Analysis Services 2005 in Cognos 8When running Analysis Studio reports, or at other times, you may find that the Microsoft SQL Server Analysis Services 2005 is using all available memory and becomes unstable, re-starts, or crashes. This is a known issue with the Microsoft SQL Server Analysis Services 2005 database.

To address this problem, you must install server patch SP2 for Analysis Services 2005, and change some configuration settings applied to that server. Most importantly, the setting DataStorePageSize, which limits the size of memory pages used during query execution, must be updated. Setting this to the value specified below enables the server to determine the best setting to use for memory useage.

To apply the required settings to a server, edit the msmdsrv.ini file, which is usually found in the following location:

C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Config

Change the configuration values for the following settings to the values shown here: • DataStorePageSize=1• AllowPresizeHashTable=1• UseDataCacheFreeLastPageMemory=1• DataStoreHashPageSize=1• DataStoreStringPageSize=1

You must restart the AS service after changing these values. 541003

Cognos 8 Server May Fail to StartA Cognos 8 server may fail to start after an upgrade or new installation, but no error message appears. This may occur when a previously running or new Cognos 8 server is configured to use a large amount of memory.

If the server on which Cognos 8 is installed contains version 1.0 of Microsoft security update 921883, there may be an issue when a lot of contiguous memory is requested by an application.

This is a known issue with version 1.0 of Microsoft security patch 921883. Microsoft distributed a second version of the patch to fix the problem. As a workaround, uninstall the first security patch, or install version 2.0 of the patch. Alternatively, you can configure the Cognos 8 server to use less memory.

For more information, see the Microsoft knowledge base article about programs using a lot of contiguous memory failing, at http://support.microsoft.com.nbna

Readme 11


Unable to Load DB2 OLAP Library in Framework ManagerYou 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.

Steps1. In the c8_location\configuration directory, edit the qfs_config.xml file.2. Find the following code:

<provider name="DB2OlapODP" libraryName="doodp82" connectionCode="DO"/>

3. Change the library name from doodp82 to doodp81 and save the changes.nbna

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.

Non-ASCII Characters in Install Directory Will Cause Run-Time ErrorsThe 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.483217

Japanese Characters Corrupted When Running issetupIf 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:

Steps1. 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.487002

Yen and Won Characters Appear as Backslashes in Charts and PDFsThe Japanese Yen and Korean Won characters are stored as U+00A5 and U+20A9, respectively, in the Unicode standard character map. However, the usage of these values is not universal and U+005C is often used for the Yen character in Japan and the Won character in Korea. Depending on the fonts you have available, the character stored as U+005C can appear as a backslash rather than a Yen or Won character.

12


Fonts used to display data in a report are selected using a matching process between the fonts requested when the report is designed and the fonts that are available when the report is rendered. For PDF output and charts, this process occurs on the server where all fonts on the server that generates the report can be used.

In charts and PDF output, the cascading style sheet file named GlobalReportStyles.css controls which fonts are used when reports are rendered. The file is located in the c8_location\bin directory.

Cognos provides a standard fallback font named Andale WT. Andale WT is world font that contains characters for many languages and characters including Latin, Cyrillic, Japanese, Chinese and Korean. Andale WT is intended to be used on a server when there are no other language specific fonts available. Because it is designed for many languages, it may not adequately represent characters in a specific language. For example, Andale WT also uses U+005C as a backslash.

However, Cognos also provides an Andale WT Japanese and Andale WT Korean font. These fonts map the U+005C value as a Yen or Won character. The Andale WT Japanese and Andale WT Korean fonts are available on the Cognos 8 Supplementary Languages CD. To use these fonts, you must install them from the Cognos 8 Supplementary Languages CD and then modify the GlobalReportStyles.css file.

Steps the Install the Fonts for Yen and Won Characters1. Use the installation wizard on the Supplementary Languages CD on each computer where

Application Tier components are installed.For more information, see the Cognos 8 Supplementary Languages Installation and Configuration Guide.

2. On the Component Selection page of the installation wizard, expand the Additional Language Fonts option, and select the font you want to install.

3. Follow the instructions in the installation wizard to complete the installation.The fonts are copied to the c8_location\bin\fonts directory. This font location is defined in the Physical fonts location value in Cognos Configuration under Local Configuration, Environment. If you move the fonts to another location, ensure that the new location is added to the Physical fonts location value.

Steps to Update the Style Sheet1. Open the GlobalReportStyles.css style sheet in a text editor.

The GlobalReportStyles.css style sheet is located in the c8_location\bin directory.2. Enable one of the following sections and modify it as shown below:

/* For Japanese: */.pg,.pp{

font-family: 'MS UI Gothic', 'Andale WT J', Tahoma, arial, geneva, helvetica, sans-serif;}

Or

/* For Korean: */.pg,.pp{

font-family: Gulim, 'Andale WT K', Tahoma, arial, geneva, helvetica, sans-serif;}

The PDF generator will use the first font in the list that is available on the server and includes all the characters in the string to be displayed. If you have other fonts on your server that you would prefer to use, you can insert them into the list.

3. Save the GlobalReportStyles.css file.

Readme 13


4. Restart the Cognos 8 server.Any changes you make to the style sheet will be overwritten if you upgrade Cognos 8. You will have to repeat this procedure following an upgrade.nbna

Cannot Publish Series 7 Cubes to Cognos 8 Following UpgradeAfter 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 Directories1. 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

2. Create an alias called cognos8 that points to the c8_location\webcontent directory.3. Create an alias called cognos8/cgi-bin that points to the c8_location\cgi-bin directory.4. Create an alias called cognos8/series7 that points to the series7_location\webcontent

directory.5. Create an alias called cognos8/series7/cgi-bin that points to the series7_location\cgi-bin

directory.6. Create an alias called cognos8/series7/help that points to the series7_location\Documentation

directory.

Steps to Change the Default Cookie Path1. 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.

497254

Choosing Only One Language When Installing Cognos 8 Transformer and PowerPlay

The Cognos 8 Business Intelligence Transformer 7.4 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.

14


Issues with IBM WebSphere 6.0 on AIX 5.3Cognos testing has found difficulties with IBM WebSphere 6.0 on AIX 5.3. Cognos recommends upgrading to AIX 5.3 Technology Level 4, Service Pack 2. nbna

Series 7 IntegrationThis section contains known issues about Series 7 integration.

Unsupported Cognos Planning 7.3 Features with Cognos 8The following Planning - Contributor 7.3 (or later) features are unsupported with Cognos 8.• Publish to Cognos Metrics Manager admin extension

If you do not have PowerPlay Enterprise Server, the following features are also unsupported.• Publish to PowerPlay Enterprise Server admin extension - All unpublished data source tasks• View in PowerPlay Web client extensionnbna

SecurityThis section contains known issues about security.

Existing Passwords May not Work in an SAP NamespaceWhen you log on to Cognos Connection using an SAP namespace, some previously functional passwords may no longer work. The following error message may appear: "Unable to authenticate a user. Please contact your security administrator. Please type your credentials for authentication".

This is because of a policy change in SAP software. In previous versions of SAP software, passwords were not case sensitive. All password characters were automatically converted to uppercase. In SAP RFC 6.40, password characters are not automatically converted to uppercase and so passwords are case sensitive.

To address the password policy change, the SAP BAPI interface introduced a new configuration parameter named bapiPasswordConv. Using this parameter, you can enable or disable the functionality that automatically converts all password characters to uppercase. To ensure that all previously created passwords can still provide successful logon to Cognos Connection, set the value of the bapiPasswordConv parameter to true.

Steps to Change the Setting of the bapiPasswordConv Parameter1. Open the file bapiint_config.xml.

This file is located in the c8_location\bin directory.2. Change the value of the bapiPasswordConv parameter to true, as shown in the following

fragment of code: <bapiAbapDebug value="false"/>

<bapiTransCall value="false"/> <bapiCharConv value="true"/> <bapiCmdRecording value="false"/> <bapiCacheReset value="false"/> <bapiCallLocks value="false"/> <bapiSupportCancel value="true"/> <bapiMaxSuspendTime value="200"/> <bapiPasswordConv value="true"/>

3. Save the file.

Readme 15


4. Restart the Cognos 8 service.

For more information, see the following SAP Notes:• 792850 - Preparing ABAP systems to deal with incompatible passwords• 862989 - New password rules as of Web AS ABAP 7.0/NetWeaver 2004nbna

Users Are Repeatedly Prompted for Credentials When Trying to Log On to an SAP Namespace

When users whose user IDs or passwords contain special characters try to log on to an SAP namespace, they are repeatedly prompted for credentials and may not be granted access.

This is because SAP BW systems, version 3.5 and older, by default use a non-Unicode code page. Newer SAP systems use a Unicode code page. As a result, the default SAP server code page was modified for the SAP authentication provider to use a Unicode code page, which is SAP CP 4110.

To avoid this issue, in Cognos Configuration, modify the default SAP BW Server Code Page parameter for the SAP authentication provider to use a non-Unicode code page, such as SAP CP 1100.nbna

Charts do Not Appear When Internet Explorer 6.x Security Level Set to HighIn 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.

Steps1. 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.

nbna

AdministrationThis section contains known issues about administration.

16


Unable to Connect to a Cognos Planning - Contributor Data SourceAttempting 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 custom installation of Cognos 8 Planning, version 8.1 or higher, with the Cognos 8 - Contributor Data Server selected. 506864

GeneralThis section contains general known issues. This includes issues that affect more than one Cognos 8 component, such as Query Studio and Report Studio. Issues that affect just one compoonent are described in the section for that component.

Not Yet Optimized Cognos PowerCubes May Open Slowly in Cognos 8If your PowerCubes take too long to open in the Cognos 8 Web studios, we recommend that you optimize them for use with Cognos 8.

With the Cognos 8 installation of Transformer version 7.4, cube optimization is automatic in the cube build process. For older PowerCubes, for example when the model no longer exists or the data used to build the cube is no longer available, we recommend that you run a command line utility named pcoptimizer, supplied with Cognos 8, to improve run-time performance.

There is an expected, but slight, increase in PowerCube size and build times. However, in most production environments, run-time PowerCube performance improves significantly.

Tips:• To check that the pcoptimizer utility is enabled for automatic cube optimization in your

Cognos 8 installation of Transformer version 7.4, in Cognos Series 7 Version 4 Configuration Manager, ensure that the Cognos PowerPlay Transformer PowerCube Optimization for Cognos 8 setting is set to True.

• If you do not optimize older cubes for use with Cognos 8, when you attempt to use these cubes in Framework Manager, you will be prompted to optimize them before you proceed to use them.

Steps to Optimize a Cube in Cognos 81. 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] <cubename>where <cubename> is the fully qualified PowerCube or time-based partitioned control cube name with the .mdc extension, if the PowerCube resides in the same location as pcoptimizer. Otherwise, <cubename> is the full path with the .mdc extension.Note: This method only supports metadata extraction. To set up user-configurable drill through, you must use Transformer 7.3 Maintenance Release 2 or subsequent releases to optimize the cube. Wildcard character support is not currently available. You must therefore invoke the utility once per PowerCube. If <cubename> 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

Readme 17


• 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 any error messages. If running in interactive mode, -v is assumed. All text is output in English only.

• -h for command-line help; if <cubename> is not provided, it prints the usage and options to the screen.

Steps to Optimize a Cube in Transformer Version 7.3 Maintenance Release 2 or Subsequent Releases1. On the Windows command line, to optimize a specific PowerCube build, type the following:

trnsfrmr –DEnablePCOptimizer=1 –cm <model_path_and_filename>In Transformer version 7.3 Maintenance Release 2 and Transformer version 7.4 installed with Cognos Series 7 Version 4, you must first enable optimization. To do this, locate the trnsfrmr.ini file in the installation_location\cern\bin directory, open it in any text editor, and then modify or add the following entry, as appropriate:EnablePCOptimizer=1

2. 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.

3. 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.

Drill-Through Performance Slower Drill-through performance in Cognos 8 may be slower than in ReportNet for the same reports.493659

Changes to Decimals in Currency FormatsWhen you open a PowerCube in a Cognos 8.2 Web studio or in Cognos 8 Business Intelligence Mobile Analysis 8.2, you may notice changes in the number of default decimal places shown in currency formats.

This behavior is due to the following changes: • The default decimal formatting in currency formats is now determined by the measure format

selected in the cube, instead of from the data source Currency Table definition.For example, if the Actual Revenue measure format specifies two decimal places and the USD currency in the Currency Table specifies no decimal places, two decimal places will now be shown in the USD currency value.

• Calculations that include a division operator and at least one currency operand will now show a resulting value with three decimal places only when• neither of the currency values includes decimals• two currency operands have different numbers of decimal placesIn all other calculations of this type, the number of decimals in the resulting value will be determined by the number of decimals in the currency value. The following examples illustrate this new behavior:• $4.00 / $2.00 = $2.00• $4 / $3.0000 = $1.3333• $4 / $3 = $1.333

18


• $4.0 / $3.00 = $1.333

For more information about measure formats or currency tables, see the Transformer online help.545573, 545408, 545427, 546183

Currency Values in a Report Appear as NumbersIf you are working with an OLAP data source, currency values appear as numbers when a report is run if the currency measure in the report is formatted as a number in the data source. This issue occurs in Report Studio and Query Studio.

To resolve the problem, do one of the following:• Ask your modeler to format the currency measure in the data source as a currency.• In the report, specify currency as the data format for the measure and apply the currency

formatting properties that you want.If the report contains multiple currencies, you must insert the member for each currency and format each member separately.

546547

Different Results for List Reports and Crosstabs that Use the Same Set Expression

In a list report, a set expression such as TopCount produces fewer rows than the corresponding crosstab report.

For example, in a list report with Year in the first column, followed by a column containing an expression that returns the top three months by revenue, there will be only three rows in the report, corresponding to the top three months across all years. If you group by Year, the report still shows only three months. However, in a crosstab report, you will see three months for each year.

This behavior is a change from ReportNet, which delivered the same results for crosstabs as for list reports.

In crosstab reports in Cognos 8, set evaluation is always done in the context of what the set is nested under in the report. However, in list reports set evaluation is done independently of the grouping. For example, if the first column contains Country instead of Year, you see the top three months for each country (across all years) in both cases.

In the case of different dimensions, Report Studio authors can force context independence by replacing [Revenue] in the TopCount expression with the Tuple( [Revenue], X ), where X is the default member of the hierarchy containing Month.

However, for nested levels in the same hierarchy, there is no such workaround at this time.

This behavior may change in a future release. At that time, a mechanism will be provided to upgrade existing reports for both ReportNet and Cognos 8 in a way that preserves their current behavior.537122, 537143

Relationships Not Maintained in a Report With Overlapping Set LevelsIn a report, the relationship between nested or parallel sets at overlapping levels in the same dimension may not always be maintained.

For example, a named set in the data source that contains members from both a Year and Month member is nested under Year, but is not properly grouped by year.

In another example, an error message such as this appears: "OP-ERR-0201 Values cannot be computed correctly in the presence of multiple hierarchies ([Product].[B1], [Product].[Product]) that each have a level based on the same attribute (Product)."

This problem occurs in the following scenarios involving non-measure data items X and Y, that overlap in the same dimension:

Readme 19


• X and Y together as ungrouped report details• Y nested under X• Y appended as an attribute of a group based on X

When using named sets, or sets that cover more than one level of a hierarchy, do not use sets from the same dimension in more than one place in the same report. They should appear on only one level of one edge.548382

Ragged or Unbalanced Hierarchies Result In Unexpected Behavior In ragged or unbalanced hierarchies, some members that are not at the lowest level of the hierarchy may have no descendants at one or more lower levels. Support for these hierarchy gaps in relational sources is limited. For OLAP sources, more complete support is provided, but some reports may result in unexpected behavior. • Groups corresponding to missing members may appear or disappear when grouped list

reports are pivoted to a crosstab. This happens with set expressions using the filter function, and detail filters on members.

• Ragged and unbalanced sections of the hierarchy are suppressed when set expressions in that hierarchy are used on an edge.

• When a crosstab is sectioned or is split into a master-detail report, sections corresponding to missing members become empty.

Some of these behaviors may be corrected in a future release, while others may be codified as supported behavior. To avoid these behaviors, avoid the scenarios above.

The following scenarios are believed to be safe:• One or more nested level references on an edge, with no modifying expression.• A hierarchy reference on only one level of one edge.• One or more explicit members or sets of explicit members as siblings on only one level of one

edge.• Summaries of the previous three scenarios.

In all cases, reports based on ragged and unbalanced hierarchies should be tested to confirm that hierarchy gaps are handled correctly.529310

536799

536813

539603

Excel Functions Used in the MDX Result in Server Error ZYou attempt to use Excel functions in the MDX and you receive an error similar to the following:

"YK -ERR 0008 The data provider returned an error message: The '[ROUNDDOWN]' function does not exist."

The solution is to install MS Office on the MS SQL 2005 Server computer.542692

Web Links Do Not Work In Acrobat 7.xIf you are using Adobe Acrobat Reader version 7.x , you may encounter problems with Web links and email addresses.

20


In this version of Acrobat Reader, Web and email addresses present in the text are interpreted as links when the PDF is viewed. This interpretation of text-based Web addresses may be problematic when the URL is split between lines, or when the underlying text is not recognized properly.

For example, the presence of a period in an email address can cause a problem, so that an address like [email protected] is interpreted as [email protected].

Another example is where Cognos documents refer to [email protected], and Acrobat Reader interprets the link as mailto:[email protected] rather than mailto:[email protected].

To solve this problem, do one of the following: • Upgrade to Acrobat Reader 8.• Turn off the feature that automatically detects URLs.

Tip: In Acrobat Reader 7, from the Edit menu, click Preferences. In the Categories box, click General. Clear the Automatically detect URLs from text check box.

For more information, see the Knowledge Base topic about periods in e-mail addresses on the Adobe Acrobat Web site (http://www.adobe.com).

Adobe Reader Versions for Server Printing on WindowsDue 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.

Note that this issue does not affect the use of Adobe Reader 7 in the browser for viewing or printing.492030

Problems Using Web Help with an Apache Web ServerWhen a user tries to view Web help using Mozilla Firefox or Netscape Navigator served from an Apache Web server, they are shown three characters in the browser window (ï"¿). The server is returning a Content-Type of ISO8859-1 error for all HTML files.

As a user, you can resolve this problem by setting encoding in the browser to Unicode (UTF-8).

Tip: From the View menu, click Character Encoding, Unicode (UTF-8).

As the administrator, you can resolve this problem for your users by setting the AddDefaultCharset flag to Off for HTML files.

For more information, see the topic about adding a default character set at http://httpd.apache.org/docs/2.0/mod/core.html.

Metadata Change in Essbase Not Reflected in StudiosWhen there is a metadata change on the Essbase server, the change is not immediately reflected in the metadata tree in the studios.

To view the new structure, you must restart both the Essbase server and the Cognos Content Manager server.545114

No Results are Returned for Footer Cells When Using Semi-Additive Measures in Dimensionally Modeled Relational Data Sources

Aggregate Rules is a new feature in Framework Manager that allows modelers to specify semi-additive behavior for dimensionally modeled relational data sources. At this time, there are limitations on footer aggregation in Query Studio and Report Studio. No issue exists for Analysis Studio.

Readme 21


In Report Studio, when you create a crosstab report containing footer summaries, no results are returned for the footer cells. To correct this, you must modify the footer cell expression.

Steps1. In the report layout, right-click the crosstab and click Go to Query. 2. In the Data Items pane, click the data item used by the footer cell.3. In the Properties pane, double-click the Expression property.4. In the Expression Definition box, change the expression from within detail to within

set.5. Save the report and run it again.

You now have correct summaries according to the aggregate rule applied

At this time there is no workaround in Query Studio to populate footer summaries for crosstab queries.nbna

DB2 Data SourcesThe 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 ServerWhen you run a query to retrieve metadata or data in a DB2 OLAP server, you may see an exception window indicating that there is a problem with the query.

The error probably occurred because Windows did not have enough remote procedure call (RPC) ports available. This lack of sufficient RPC ports can cause data retrieval from DB2 OLAP and Essbase data sources to fail because of network communication errors.

To resolve this problem, you must increase the number of RPC ports that are available for program use. Hyperion and Microsoft propose that you add two registry entries, MaxUserPort TCP/IP and TcpTimedWaitDelay in Microsoft Registry Editor.

For more information about these parameters, see http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/regentry/58811.asp.

Important: Use Registry Editor at your own risk. Incorrect use may cause problems that require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly.

We also recommend that you edit the Cognos 8 qfs_config.xml configuration file.

Steps to Add Entries in Microsoft Registry Editor1. From the Start menu, click Run.2. Type regedit and then click OK.3. In the Registry Editor window, click the following directory:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters4. From the Edit menu, click New, DWORD Value.

The new value appears in the list of parameters.5. Type MaxUserPort and then press Enter.

Double-click MaxUserPort.6. In the Edit DWORD Value window, do the following:

• Click Decimal.• Type a value between 30000 and 65534.

Tip: We recommend the maximum value, 65534.

22


• Click OK.7. From the Edit menu, click New, DWORD Value.

The new value appears in the list of parameters.8. Type TcpTimedWaitDelay and then press Enter.9. Double-click TcpTimedWaitDelay.10. In the Edit DWORD Value window, do the following:

• Click Decimal.• Type a value between 30 and 300 seconds.

The default is 240 seconds (4 minutes).• Click OK.

11. Close the Registry Editor window. 12. Restart the Microsoft CRM server or reboot your computer for these settings to take effect.

Steps to Edit the Cognos qfs_config.xml Configuration File1. Open the qfs_config.xml configuration file from the configuration directory.2. Add the following parameters under the appropriate provider section, such as <provider

name="DB2OlapODP"...>.• <parameter name="RecoveryAttemptNumber" value="50"/>• <parameter name="RecoveryWait" value="3000"/>The RecoveryWait value is in milliseconds.Note: DB2OlapODP and Essbase are synonymous and are used interchangeably in Cognos 8.476181

Unable to Open a Cube Using 8.2 DB2 OLAP or EssBase 7.1If 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 Library1. In the DB2 OLAP 8.2 client installation wizard, select the Custom installation type, and then

click Next.2. Select the Essbase API for Windows 32 option if it has not already been selected, and then

proceed through the remaining pages of the installation wizard.3. When the installation is finished, locate libdb42.dll in the folder

db2olap_installation_location\api\redist, and copy this file to the client installation folder db2olap_installation_location\bin.

4. Restart your system.Note: If you apply a Fix Pak to your DB2 OLAP 8.2 client, remember to also recopy libdb42.dll (as explained above), to ensure that your \bin folder always contains the most up-to-date version of this required file.483570

SAP BW Data SourcesThe 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.

Readme 23


Incorrect Units of Measure in CalculationsWhen creating calculations in Report Studio and Query Studio, you may encounter problems with the units of measure. For example, the calculation Cost*Cost returns the unit of measure CAD^2 in BEx but * in Cognos 8.

Change the format of the corresponding column to obtain the desired unit of measure. 421591

Grouping Columns That Have the Count SummaryIf you add the Count summary to a non-fact column in a list and then group the column, the column will not be grouped when you run the report.

To resolve this issue, group the column first before adding the Count summary.435017

Missing Measures in Crosstab ReportsIf you have a crosstab with multiple measures (multiple summary types and semi-additive aggregations), one measure may not render if the default aggregation function for the measures is set to Automatic.

To resolve this issue, set the default aggregation function to None.437751

Crosstab with the Same Dimension on Both Edges Returns No DataIf you run a crosstab report that has the same dimension on both edges, the report will not return any data.

To resolve this problem, specify that data not be suppressed for the query that is driving the crosstab.

Steps to Specify That Data Not Be Suppressed1. In the report layout, right-click the crosstab and click Go to Query.2. In the Properties pane, click the Suppress property and click None.3. Save the report.545657, 545661

Custom Formatting for Empty Cells Does Not Appear in Cognos 8If the SAP BW server administrator configures custom formatting for empty cells on the SAP BW server, the custom format does not appear in Cognos 8 reports.

Administrators should configure the formatting of empty cells in Cognos 8.425064

Creating Sections on Reports That Access SAP BW Data SourcesSAP BW data sources may have problems with sections in reports under different circumstances:

If a section in a report uses the lowest-level query item in a ragged hierarchy, such as the children of the "not assigned" node, the following BAPI error may appear:

BAPI error occurred in function module BAPI_MDDATASET_SELECT_DATA. Value <valueName> for characteristic <cubeName> unknown

If you create a section in a report using conformed multicubes with SAP variables, an SAP error message may appear.

24


Lowest-level Query Item in a Ragged HierarchyThe solution is to remove the section from the lowest-level query item.443696

Several Multicubes with SAP VariablesThe solution is to use one multicube when creating sections in reports.437613

Summary Rows Return Incorrect Total ValuesWhen the rollup summary function of a measure is minimum, summary rows return incorrect total values.

Currently, there is no workaround for this problem.409532

Calculated Key Figures Appear with the Non-aggregate Icon Calculated key figures appear with the non-aggregate icon in the Key Figures folder.

To solve this, edit the variable in SAP BW and set the TIME OF CALCULATION to Before Aggregation.nbna

Filter Expressions Using Report Items and Smart Prompts Do Not Return Values

If you create a filter expression such as the following, no data is returned.

[ <report item attribute> ] = ?prompt?

To resolve the problem, do one of the following:• Fully qualify the item by using items from the metadata tree instead of the report item tree• Build smart prompts in the report instead of hand coded prompts495958496340

Cognos 8 Business Intelligence Transformer 7.4This section contains known issues about Cognos 8 Business Intelligence Transformer 7.4.

Queries Against Multiple Hierarchies in the Same PowerCube Dimension Do Not Execute

In Cognos 8.2, when you run a query against a PowerCube requesting data from more than one hierarchy in the same dimension, you receive an error message indicating that the action is not supported. As a result, the report does not execute.

Your request fails to execute because, in Transformer models, any grouping of categories from the same dimension that disregards the primary hierarchical organization, such as relative time categories, special categories, or categories from an alternate drill path, is interpreted in Cognos 8 as a distinct new hierarchy in that dimension.

To avoid errors and inconsistencies, if you must support a query containing multiple hierarchies from a single dimension, one possible solution is to manually create new special categories in the Transformer model, and then move the existing categories you require to the new special categories. For this approach to work, you must retain at least one of the previously existing categories in the original structure, for example, the convergence level of a multiple drill hierarchy.

Readme 25


Note: When you create the new special categories, you do not need to specify any special property values.

To view an example of a Transformer model with the relative time categories in a new special category, go to the Cognos Global Customer Services Web site, and on the Utilities page, search on Cognos 8 Business Intelligence Transformer 7.4/Utilities to download an updated Great Outdoors Company sample cube.

For information about creating special categories, see the Transformer online help.529184

Query StudioThis section contains known issues about Query Studio.

Cannot Use Hierarchies from Dimensionally Modeled Relational ModelsWhen working with a dimensionally modeled relational model, you cannot insert hierarchies in a report.nbna

Text and Border Styles Are not Applied to Empty ReportsIf 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.463562

Functions not AvailableWhen working with a multidimensional data source, the Calculate menu does not show the following functions:• Rank• % of total• Percentile• Quartile481930

Unable to Insert Data Items from Two Hierarchies of a Single DimensionIn Query Studio or Report Studio, you cannot insert two data items from two hierarchies of a single dimension.488615

Background Color in Template Does not AppearWhen 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.

To work around this issue, do one of the following: • Edit the style sheet (CSS) classes for lists in Report Studio• Do not add any objects to the page body when you are creating a Query Studio template.

Leave the page body blank.484108

26


Subtotals in Grouped ListsWhen 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.498295

Report StudioThis section contains known issues about Report Studio.

Unable to Run Cognos 8.2 Reports in Cognos 8.1Reports that are upgraded to Cognos 8.2 will not run in Cognos 8.1. This is because the report specification version, as identified by the XML namespace, was updated for the Cognos 8.2 release. The Cognos 8.1 namespace version is as follows:

xmlns="http://developer.cognos.com/schemas/report/2.0/"

The Cognos 8.2 namespace version is as follows:

xmlns="http://developer.cognos.com/schemas/report/3.0/"

Currently, there is no workaround.nbna

Set Expressions That Depend on the Current Measure May Return Incorrect Data

If a crosstab report contains a set expression that depends on the current measure, such as topCount([Year], 3, value([Tents])), you may see the following behavior:• If a measure is added or removed from the report, the set of detail rows or columns changes.

In some cases, the report may fail to run.• If two value calculations are placed side by side, the values do not match. The rows for one of

the calculations are mixed up.

This happens if at the time the set expression is computed for the edge there is no measure in context. The measure that Cognos 8 picks may not be what you expect. Also, the measure picked may be different in different releases.

To avoid this problem, when a set expression that depends on a measure is projected on an edge, specify the measure explicitly. For the above example, to specify the measure explicitly, change the expression to the following:

topCount([Year], 3, value(tuple([Tents],[Revenue])))

Note: This workaround is a recommended best practice. The current behavior may change in a future release to become more predictable so that this best practice will no longer be required.544255

Running Totals Are Incorrect in Crosstab ReportsRunning totals are not calculated correctly when they are summed across a dimension. This is because Cognos 8 does not currently support queries with both dimensional functions and running totals. For example, when you drill down in a report, the query contains the dimensional function children, which is not compatible with running totals. Running totals are supported only for the overall level of a dimension.

Currently, there is no workaround.546796

Readme 27


Aggregate Values Are Not Appearing in CrosstabsWhen 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.

Steps to Show Aggregate Values1. 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.480409

Calculated Rollup Aggregate Type Is Computed in Different WaysIn earlier versions of Cognos 8, footer values for items that use the Calculated aggregate type either explicitly or implicitly, such as when using the Automatic aggregate type, were computed using the minimum aggregate function. Cognos 8.2 computes some of these footer values differently. Here are some examples:• Running total

In earlier versions, the footer was computed using MIN. In Cognos 8.2, the footer is computed using SUM.

• Abs() In earlier versions, the footer was computed using MIN. In Cognos 8.2, the footer is computed by an MDX query using the aggregate-then-calculate aggregation rule.

• Ceiling() In Cognos 8.2, the footer continues to be computed using MIN.

In the case of list reports, the solution is to explicitly define the rollup aggregate function for the measures instead of leaving the default as Calculated or Automatic.546717

Key Transformation Validation Level Returns Partial InformationIn Report Studio, if you revalidate a report using Validate with Options, and select the Key Transformation validation level, you will get back all errors and warnings, but you may get little or no information back regarding the transformation steps from the report specification to the native query sent to the data source.

While the documented description for the Key Transformation validation level is correct, the feature is only partially implemented at present.

Pivoting to a Crosstab Shows the Member of the Attribute 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.

28


We recommend that report authors avoid creating crosstab reports with grouped attributes for the current release.nbna

Event StudioThis section contains known issues about Event Studio.

Error in AssignStaff Stored Procedure in ELM Returns Agent SampleThe AssignStaff stored procedure called in the Cognos 8 sample named ELM Returns Agent does not update the table in the GOSL database or send email messages when the sample is run.

The workaround for this problem is to create the stored procedure under the GOSL schema using the commands provided in the sql script. The commands are found before Part 1 in the sql script file. Run the stored procedure create commands before running the commands in Part 1 or Part 2 as part of running the sample.547337

Parsing Error When Passing Data From a Dimensionally Modeled PackageIf an agent runs a prompted report that is based on a dimensionally modeled data source and passes a value from the agent's event list, the report task fails and the following error messages appear:QE-DEF-0260 Parsing error before or near position: n of: "parameter_value" QE-DEF-0261 OQP - Parsing text:parameter_value

This error occurs because the report can accept only a Member Unique Name (MUN) but the agent passes it a caption value.

There is currently no workaround for this issue.522357

Analysis StudioThis section contains known issues about Analysis Studio.

Analysis Studio LimitationsIn 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.

Readme 29


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.

Error Occurs in Japanese Internet Explorer 7 When Running an Excel Report in Analysis Studio

An error may occur when you close Japanese Internet Explorer 7 installed on Windows XP SP2 while it is running an Analysis Studio report in Excel format.

To solve this problem, Microsoft recommends that you unregister the msctf.dll file using the following command:

Regsvr32/U Msctf.dll

This .dll file is part of the ctfmon.exe speech recognition application. You may turn off any speech recognition application installed on your computer before unregistering the .dll file.

For more information about turning off speech recognition, see

http://support.microsoft.com/kb/313176/EN-US/540718

The "More" Calculation in Analysis Studio May Return Non-intuitive NumbersThe "More" calculation is a simple subtraction of the Grand Total less the Visible Items. In some cases, for example when using a calculated member from the cube such as "YTD Growth", this will return non-intuitive results.

The default behavior is to not show "More" values. If users request the "More" calculation, they will get a result that is equal to Overall Total - Summary of Visible Items. For calculated members such as "Growth" this query will be changed in a future release.524648

Analysis Studio Shows the Wrong Currency SymbolWhen published to Cognos 8 Analysis Studio, PowerCubes show a default currency rather than the currency associated with the locale of your servers and PCs. For example, GBP (£) is shown as $.

To resolve this problem, you can do one of the following:• Create a currency table when you prepare your model in Transformer and embed a default

currency symbol into the resulting PowerCubes, based on the system locale used by your Transformer computer.

• For PowerCubes that do not contain an embedded currency table, set the fallbackCurrency parameter as the default currency.

Steps to Create a Currency Table in Transformer1. In Transformer, from the File menu, click Currency Table, and click OK.2. Right-click each currency measure, and click Allow currency conversion.

30


This default currency table does not include currency information for any locales other than your running locale. Also, you cannot convert to a different currency while working in Analysis Studio.

Step to Set fallbackCurrency as the Default Currency• Define a default currency by setting the fallbackCurrency parameter in the

configuration/qfs_config.xm file to GBP (Great Britain Pounds) or to an alternative currency code as listed in the /ccli18nrescr_xx.xml file.

Here is an example. <provider name="PowerCubeODP" libraryName="pcodp"connectionCode="PC"> ... <providerDetails> <parameters>  <parameter name="maxCalculatedMemberNestingDepth"value="30"/>  <parameter name="normalizeYenWon" value="true"/>  <parameter name="fallbackCurrency" value="USD"/> </parameters> </providerDetails></provider>516574

Filter by Label or Attribute is Case SensitiveWhen you define a filter rule by using a label or an attribute, the text is case sensitive.486777

Cells with '- -' are Represented as NULLS in Export to Excel 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.488293

Context Filter LimitationsIn 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 SourcesThe first time you publish a cube definition to Cognos Connection, you must identify all the languages that represent the data contained in the cube. If you add a language to the model after the cube is published, users with locales that match the added language locale may find that Analysis Studio does not recognize references to the member unique names. There is no impact on users whose locale matches the original language list.499296

Readme 31


Crosstab Shows Percentage But Chart Shows ValuesWhen the crosstab calculates the percentage of the total for an item, the chart does not show the values as a percentage.494291

Analysis Studio Does Not Reflect Package Configuration SettingsTo 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. 498615

Analysis Studio Ignores Changed Package Reference in Cognos Connection 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.499322

Server Error When Sorting a Selection-Based Set by AttributeWhen 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.492637

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 501682501709

Unable to Search in the Source Tree for Data Enclosed In Brackets When Using Microsoft SQL Server Analysis Services 2000

In the source tree, you cannot search for items that are enclosed in brackets, such as Drinks (Colas), when using a Microsoft SQL Server Analysis Services 2000 data source.

Do not include brackets in the search string. 503226

Report Options are Ignored When Running an Analysis in Report ViewerWhen the user runs an analysis in Report Viewer after selecting the Outermost groups on rows option under Page breaks in the Report options dialog box, the outer nesting group is always expanded and any calculations are not shown.

There is no workaround for this issue.501235

32


Metric StudioThis section contains known issues about Metric Studio.

Error When Viewing a History Chart or Diagram on a DB2 Server with the 8.2 JDBC Driver

When the user tries to view a history chart or diagram, they see the following error:

The Cognos Gateway is unable to connect to the Cognos BI server. The server may be unavailable, or the gateway may not be correctly configured. Please try again or contact your administrator.

This problem is known to occur only when Metric Studio is installed on an HP/UX Itanium server. This problem is caused by a bug in the DB2 8.2 JDBC driver (APAR IY92903). IBM plans to fix this problem in FixPak 15.

The only workaround for this problem is to use DB2 9.1.524818

The Setting to Show This Report in Lower-Level Scorecards Is Lost After Export and Reimport

When you create a report for a scorecard, you can select the option to show the report on lower-level scorecards. After you export and reimport the scorecard information the setting is lost. Reports no longer appear on the lower-level scorecards.

The workaround is to manually reselect the setting after import.545987

The Setting to Show This Report on All Metrics of This Type Is Lost After Export and Reimport

When you create a report for a metric type, you can select the option to show the report on all metrics of this type. After you export and reimport the metric type information the setting is lost. The report no longer appears on all metrics of this type.

The workaround is to manually re-select the setting after import.545987

Package Creation Fails If Default Oracle Permission Is RevokedBy default, privileges for the UTL_FILE package supplied by Oracle are granted to PUBLIC. If you revoked this privilege, creation of the metric package fails.

The solution is to grant the required privilege by running one of the following commands:

GRANT EXECUTE ON UTL_FILE TO PUBLIC

GRANT EXECUTE ON UTL_FILE TO CMM_USER524622

Readme 33


Metrics Are Not Created on ScorecardsCalculated metrics are not created if you define the Metric type default calculation on the Value Types tab, but do not click Use the metric type default calculation for the value types that you want calculated and then perform the Metric Maintenance task Recalculate Data Store Derived Values. For example, when creating a calculated metric type, you define the default equation, do not assign it to the value types, and then perform run the Recalculate Data Store Derived Values task. Subsequently assigning the default equation to value types will not generate the expected calculation results. No results will be produced for that metric type when you run the Metric Maintenance task Recalculate Data Store Derived Values.

The solution is to modify the default equation. On the Value Types tab for the calculated metric type, modify the default equation in some way and then assign the value types that you want calculated by clicking Use the metric type default calculation.525650

Actions Loaded From File Do Not Trigger Watchlist EmailsActions loaded from a file will not trigger an email update to users monitoring the metric in their watchlist. An email is only sent for watchlist items when an action is created for the metric in the Metric Studio user interface.524082

Errors When Loading Data with Timestamps into SQL Server 2005If you try to load data into SQL Server 2005 using tab-delimited files that contain dates written with a time component, such as YYYY-MM-DDHH24:MI:SS, you receive one of the following errors:• Error = [Microsoft][SQL Native Client]String data, right truncation• Error = [Microsoft][SQL Native Client]Datetime field overflow

The two workarounds are:• use SQL Server 2000 for the metric store• edit the input files by removing the time component on all rows

A future release of Metric Studio will allow tab-delimited files to contain the time portion of the date.523639523760

Recommended Patches for Oracle 10gThere 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)nbna

34


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.

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.UTF8nbna

Equations Using Only Constants are not Allowed in Calculated Metrics TypesIn 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.486808

Content that uses double-byte characters displays as unreadable characters (Oracle)

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.494367

Right-clicking to Follow a Link in a New Web Browser Window Is Not Supported

A Page Not Found error appears or other problems occur, such as disabled links and buttons, if you follow a link in Metric Studio by right-clicking the link and clicking Open in new Window in Internet Explorer or Open Frame in new window in Netscape and Firefox.

Steps to Follow a Link in Metric Studio by Opening a Second Web browser Window1. Click prepare bookmark in the upper toolbar. 2. From the File menu of the Web browser, click New Window.

Tip: You can also press Ctrl-N.A second window with the same content as the first one appears and you can then click the link that you want.505528

Full-width Tilde (Korean) Does Not Display Correctly After Import into IBM DB2

After you import tab-delimited files containing the Korean character Full-width Tilde into a IBM DB2 metric store, the character does not display correctly.The Full-width Tilde is converted to the Half-width Tilde.

Readme 35


499392

Korean Full-width Tilde Changes to Half-width Tilde After Being Imported into a DB2 Metric Store

When the name or description fields in the .cmo or .cmm tab-delimited file (ANSI file) contain the full-width tilde character, and the character set encoding is 970 in the import source properties, the tilde changes to the half-width tilde character after the files are loaded into the metric store.

This is because the default IBM versions of the codepage table converts the character differently from the Microsoft versions.

Steps to Use a Different Conversion Table1. Contact IBM DB2 Support and be prepared to provide your platform information (Windows,

UNIX and so on) and DB2 version number2. Request the Microsoft version of the conversion table for codepage 970.3. Replace the default conversion table with the alternative conversion table by following the

instruction from IBM499392

Full-width Tilde and Full-width Hyphen Characters Change to the "?" Character After Being Exported From a DB2 Metric Store with -Korean(EUC-KR)(DB2) Encoding

When the name or description fields in the .cmo or .cmm flat file (ANSI file) contain the full-width tilde character or the full-width hyphen character, and - Korean(EUC-KR) is the character set encoding in the import source properties, the characters become "?" when you export with the same encoding

This is because the default IBM version of the codepage table converts the characters differently from the Microsoft versions.

Steps to Use a Different Conversion Table1. Contact IBM DB2 Support and be prepared to provide your platform information (Windows,

UNIX and so on) and DB2 version number.2. Request the Microsoft version of conversion table of codepage 1363.3. Replace the default conversion table with the alternative conversion table by following the

instruction from IBM.523973

Unable to Delete Time Periods from the CalendarThe ability to remove periods (usually years) has been removed from the product to prevent inadvertent deletion of weeks that span years.

The data for the year can be deleted by exporting it and then restaging it with an empty value. Alternatively, a new package can be created that does not contain that year and then the data loaded into that new package.500188

Metric DesignerThis section contains known issues about Metric Designer.

36


Cannot Edit or Run an ExtractAfter closing a Metric Designer project and then opening the same or a different project and attempting to edit or run an extract, the following error messages may appear:

PD-MD-0107 The following error occurred when trying to call stored procedure ’pd_getdisplayname’.

RQP-DEF-0177 An error occurred while performing operation ’sqlPrepareWithOptions’

To resolve this issue, close the Metric Designer project, reopen it, and try editing or running the extract again.523555

Japanese Characters Do Not Display Correctly After Import into SQL ServerAfter you import tab-delimited files formatted as UTF-8 into SQL Server, Japanese characters do not display correctly.

To import tab-delimited files that contain Japanese characters into SQL Server, the tab-delimited files must be in the ANSI format.

If you want to import data containing Japanese characters into a metric store on SQL Server, you can either

Steps1. Manually convert the tab-delimited files from UTF-8 format to ANSI format on a Japanese

operating system before running the metric maintenance task2. Metric Designer generates only UTF-8 format tab-delimited files so if you are creating an

extract that contains Japanese characters, import the extract directly from Metric Designer to the Metric Studio staging area.509949

Framework Manager - Import Source and Anonymous User Language Preference

When accessing a 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 Regional Settings on the computer to be the same as the anonymous user Cognos 8 language preference.nbna

Framework Manager - Import Source Connections and CredentialsMetric Designer does not support Framework Manager import sources with missing connection or credential information, or Framework Manager import sources with multiple import sources.nbna

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.

Open the extract, select the metric mapping page, and delete and recreate your metric filters.473386

Readme 37


Problem Executing an Extract Created From a Framework Manager Model Using a Teradata Database

At execute time, the following 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 of the SQL request.

[NCR][ODBC Teradata Driver][Teradata RDBMS] The number of digits specified must be between 1 and 18."

In installation_location\cognos\c8\configuration\pd.ini, there is now a new section called "ExecuteOptions", with two preferences:

Steps1. "castKPIValues" -- if set to "true", Metric Designer 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 ). Workaround: Set the "castKPIValuesType" preference to DECIMAL( 18, 5 )

<Section Name="ExecuteOptions"><Preference Name="castKPIValues">true</Preference><Preference Name="castKPIValuesType">DECIMAL(18,5)</Preference></Section>

468372

<Section Name="ExecuteOptions">

<Preference Name="castKPIValues">true</Preference>

<Preference Name="castKPIValuesType">DECIMAL(18,5)</Preference>

</Section>468372

IQD Import Source - Error Reading IQD file that Contains the Oracle 'Replace' Function

When using an IQD import source that contains an 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-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 installation_location\cognos\c8\bin, and set "Empty_String_Is_Null" to "F".445064

Adding Multiple IQD files to an Import SourceWhen you add multiple IQD files to an import source, Metric Designer creates an outer join between the first pair of non-numeric, non-date columns with matching names. The join approach is designed to work with a single fact IQD file and with multiple dimension IQD files.

38


Metric Designer does not recognize joins where more than one column is required for a join condition. In this case, enter the IQD files into Metric Designer as separate import sources or combine into a single IQD using Impromptu.440049

Data Sources Not SupportedThe 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 nbna

Filters on Parent-Child Hierarchies Are Not Supported for Dimensional (OLAP) Data sources

When filtering the member in a parent-child hierarchy, child member(s) are not included in the filter.494909497977

Error Occurs for a Metrics Extract Containing Static Text-type Scorecard Levels

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.500448

Metrics Extracts Containing Typed-in Constant Metric Attribute Values Do Not Deliver Metrics for PowerCube Data Sources

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(<constant>)

Average (.25) 500908

Construct Functions in Scorecard Identifier Expressions Not Supported for PowerCube Import Sources

Construct functions including "IF THEN ELSE" and "CASE" are not supported in expressions for scorecard identifiers for PowerCube import sources.508879

Readme 39


Day Level Time Period Filter May Cause Metric Designer to Become Non-responsive

In certain circumstances, setting a detailed time period filter for specific days may cause Metric Designer to become non-responsive.

Workaround: Set filters at a higher time grain such as months.511507

When You Log off and Then Log on Using Different Credentials the Authentication Information is Not Refreshed

When creating Metric Designer extracts involving user class security with PowerCubes, the logon/logoff feature doesn't refresh the authentication information and Metric Designer remains authenticated under the account used to first login. For example, if you log off and then log on again using different credentials, you will still see the model objects relating to the original credentials, rather than the new credentials.

Workaround: Log off and exit Metric Designer. Then, restart Metric Designer and log in using the new credentials.501908.2

MUNs Have Changed in Filter Expressions in Extracts from Earlier Versions of Metric Designer

The syntax of member unique names (MUNs) has changed. Members can appear in Metrics Designer filter expressions, and no model upgrade has been implemented. If you open an extract built in a previous release of Metric Designer, you will still see the members with the old syntax if you open a filter expression in the expression editor. If you try to respecify the filter expression, you will see that the member is different than before.

This is only a usability issue. When executing an extract, CMD will first internally convert the old MUN into the new form before proceeding with the execution.524153

Computer Hangs When Executing a Metrics ExtractWhen executing a metrics extract that uses certain types of filtering, the extract may continue to run without completion. This problem is related to the use of "<>" in an expression.

Workaround: In the Expression Editor, use "NOT IN" instead of "<>".522010.0

Framework ManagerThis section contains known issues about Framework Manager.

System Objects for SQL Server 2005 Do Not AppearWhen importing SQL Server 2005 metadata, if you select the Show System Objects check box, the system objects do not appear. In the current release, Cognos 8 does not support SQL Server 2005 system objects.509158

40


Duplicate Schemas and System Tables When Using Teradata and SybaseIf you are using Teradata V2r6 or Sybase ASE 15, clicking Show System Objects results in schemas and system tables being duplicated in the Import Wizard. If you select both duplicates, the import could hang.512623

Changes Made to a Child Segment Not Reflected in the ParentChanges that you made to a child segment are not reflected in the parent project, even after doing a refresh (F5). This happens because another child segment linked to the parent or the parent project itself is open.

The solution is to close all child segment projects and then reopen the parent project.523454

Running the BME Script Player Can Result in ErrorsRunning the BME script player under some user IDs on UNIX results in the following error: BME-SP-0002 BMT initialization error: BME-EX-0056 Unableto complete the action. The failure could be caused by invalid parameters.Check messagesto determine which errors occurred.

This error is caused by not having read and execute permissions because you are not in the primary group of the person who installed the product.

The solution is to do one of the following:• Use the Metadata provider to execute action logs. (Recommended)

Metadata provider is documented in the Framework Manager Developer Guide. • Change your primary group to be the same as that of the user who installed Cognos 8.• Manually change the permissions of these directories and files: bin, templates, data, and temp.538454

Dynamic Retargeting of Query Items FailsDynamic retargeting of query items in a model query subject fails in synchronization if the column names of the underlying tables do not match the original column names for that query.

You create a view or table in a data source, and import it into Framework Manager. You create a model query subject using the query items of the view or table.

If you change the projection list in the view or table and then synchronize, you are alerted that some objects do not exist. If you choose to replace the column with the new one, an error occurs. Errors also occur when the exclude and stop options are tried.

The following error message appears:Error at Transaction 5, Action 4Action: EvaluateObject failed, skipping...Reason: BMT-MD-0003 QE-DEF-0030 Expression parsing error.QE-DEF-0359 The query contains a reference to at least one object '[ds].[qs].[qi]'that does not exist.QE-DEF-0030 Expression parsing error.QE-DEF-0359 The query contains a reference to at least one object '[ds].[qs].[qi]'that does not exist.

If you attempt to evaluate the object, the model query subject is not re-created.

Readme 41


The solution is to use aliases if you are likely to change the columns in the SQL projection list of your objects. If you use aliases in the projection list and keep them, no problems will be encountered. If you change the projection list to * from a list or vice versa, there will be no problem.538015

Full Outer Joins Not Sent to Oracle 9 and 10GBy default, Cognos 8 will not send full outer joins to ORACLE 9 and 10G due to Oracle bug #2874433. This requires using limited local processing in Cognos 8.

To enable full outer joins with Oracle, you must• ensure that you have the required patch sets, which include the fix for Bug#2874433• modify the cogdmor.ini file to turn on full outer joins (Full_outer_join=T)

Because any manual edits to the ini settings are overwritten by the next installation, you must manually replicate them on all machines where you installed Cognos 8 or Framework Manager. nbna

Framework Manager Hangs When Using the Isolation Level for Informix Data Sources

If you run a stored procedure that can change the data of a query object and the query object is being used, or was used, for testing or running reports, Framework Manager will hang. This happens only with Informix data sources when you use the default isolation level, Reproducible Read, that is set in the data source.

The solution is to reset the data source isolation level to one of the following levels: • cursor stability (recommended)• read uncommitted• read committed515913

Error Results When Testing a User-defined Function in a Stand-alone Calculation

Testing a user-defined function in a stand-alone calculation results in an error if you do not include a query item in the test.

The solution is to ensure that a query item is referenced when testing a user-defined function.519178

Cannot Test the Key Figures Dimension with an Embedded CalculationYou have upgraded an SAP BW model from Cognos ReportNet to Cognos 8. In Cognos ReportNet, the Key Figures dimension contains an embedded calculation. In Cognos 8 you try to test the Key Figures dimension and Framework Manager closes.

The solution is to delete the faulty Key Figures dimension that was generated by the upgrade and then re-import it.

Cannot Test a Calculation When the Active Language Is Not EnglishIf you are using SAP BW metadata in Framework Manager with the design language set to English and you change the active language to another language, such as German, you cannot test a calculation in the expression editor if the expression has a decimal.

The solution is to test the calculation in the studios or the project viewer.

42


543327

Dimensional Functions and Members Are Not Always SupportedAlthough dimensional functions and members are available within the expression editor for Framework Manager, they are not supported when used for calculations and filters inside query subjects and are supported only in certain cases when used for calculations and filters inside dimension objects.

Dimensional functions and members appear as available within calculation and filter definitions, and can be successfully defined and tested when regular and measure dimensions exist in the model. Most dimensional functions do not run when tested within a query subject or dimension and the following error message appears: GEN-ERR-0009 - Datasource type(s) 'OL'- Function 'functionname' is not supported in 'Relational Query Provider'.

All dimensional functions are marked with a Quality of Service indicator, an exclamation mark (!). It is not recommended that you use dimensional functions within query subjects or dimensions in Framework Manager. This is because the result from a dimension and member reference is not compatible with the relational sets returned by testing a dimension or query subject in Framework Manager. This functionality will not be enabled in future releases.

If you choose to use dimensional functions and members in Framework Manager, note the following:• If the expression returns a value that does not depend on the current measure, the expression

can be used as a query item (measure) in the Measures dimension. An example is: Revenue - Cost

• If the expression returns a value that depends only on the current member of a particular dimension, the expression can be used as a query item in that dimension. An example is: substring( Caption(Products), 5 )

• If the expression returns a member or set, the expression cannot be used as a query item. It can be used only as a stand-alone calculation with dimensions and measure dimensions in the studios. Using the expression with query subjects will not be enabled in future releases.An example is: topcount( Products, 10, Revenue )

524479

Cannot Test a Dimension with an Embedded Filter That Refers to a Stand-alone Calculation Returning a Member

In a model that is based on an SAP BW cube, you have defined a stand-alone calculation that returns members from a level. You use this calculation in a filter that is embedded in a dimension. When you test the dimension, you see this error message:QE-DEF-0478 Invalid coercion from 'member' to 'string'for '[sottbw03(unicode)].[CALC] = [National (Standard)].[Market].[Market].[Market]->:[BW].[ZQ1NATMKT].[BUILDERS]'.Ex:- define CALC= members ( [National (Standard)].[Market].[Market].[Market] )- define an embedded filter into MARKET dimension using CALC:[sottbw03(unicode)].[CALC] = [National (Standard)].[Market].[Market].[Market]->:[BW].[ZQ1NATMKT].[BUILDERS]- Test dimension----'error

To solve this problem, use the actual calculation expression in the embedded filter expression instead of using the stand-alone calculation.522411

Readme 43


Cannot Specify the Order of Members When Defining a LevelIn the current release, you cannot specify the order of the members when defining a level for a regular dimension on a relational data source. 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. 491332

Dimension Appears Empty in Analysis StudioA dimension may appear empty in Analysis Studio if the dimension contains a filter based on a member.

For example, if the filter is defined as CountryMember = CANADA, querying for the hierarchy or level returns no values because the filter is explicitly applied.

Here is an example:[Automobile (Original)].[Country].[Country].[Country]= [Automobile (Original)].[Country].[Country].[Country]->:[BW].[ZQ1AUTCTR].[CANADA]

The solution is to ensure that the filter is a model filter, remove the filter from the dimension, and then add the filter to the package. The filter is then available to the report authors but does not interfere when querying for the child members within the dimension.512354

BEx Queries Do Not Pass Back Hierarchies in a Characteristic Structure When you create BEx queries that contain embedded hierarchies in the characteristic structures, the queries will not pass back those hierarchies to Cognos 8 because they are not exposed (by SAP) through the OLAP BAPI. Consequently when you try to report on that hierarchy data using one of the studios, the reports will not get back data.

44


Errors When Running a Report from the Find Report Dependencies WindowIf a report name or package name contains spaces, errors will occur in Framework Manager when you try to run a report from the Find Report Dependencies window.

In the studios, the solution is to remove the spaces in the report names.

In Framework Manager, the solution is to remove the spaces in the package name.546871

Insufficient Memory to Export a Large InfoCube A large CSV extract can sometimes consume a lot of memory.

The solution is to export data in multiple extracts using SAP filters and variables to limit the data volume for each extract. 445082

Embedded Externalize Method Does Not FunctionThe Embedded externalize method appears in Framework Manager but does not represent functionality for the current release.nbna

Default Setting for SQL Generation Has Been ChangedThe default setting for SQL Generation is to not use INNER JOIN syntax. This is because inner joins impede some relational database management system (RDDBMS) optimizers.

Cognos 8 Go! OfficeThis section contains known issues about Cognos 8 Go! Office.

Workbook Closes Unexpectedly If Name Contains Square BracketIf you install the COM add-in and your Microsoft Excel workbook name contains a square bracket Excel hangs or closes unexpectedly after opening.

To resolve this problem, rename the workbook so that it does not contain any square brackets.525725

Cannot Open a Report in Excel in Cognos Connection If You Have a COM Add-in Workbook Open

When you run a report in Cognos Connection with the Format (output) set to Excel and a Cognos 8 Go! Office workbook is opened that uses the COM Add-in, the report in Cognos Connection does not load and hangs until you close Excel.

Before running a report in Cognos Connection with the Format (output) set to Excel ensure that you do not have any Cognos 8 Go! Office workbooks open. You must save changes and close the workbook before running the report.525414

Readme 45


The Cognos Action Pane Disappears When Using the Smart Client and You Run a Report in Excel in Cognos Connection

You run a report in Cognos Connection with the Format (output) set to Excel and a Cognos 8 Go! Office that uses the smart client is opened, but when you go back to Excel the Cognos Action Pane does not show with the workbook any more.

There are three ways to work around this behavior:• Switch to another open workbook and then switch back to the original one.• Close and reopen the workbook.• Create a new workbook and then switch back to the original one.525425

No Report Content Is Imported When the Report Name Contains a Single Quote (')

If the report name has a single quote and the Create new worksheets for report pages option is set, the report content is not imported.

You must rename the report without the single quote.525286

COC-ERR-2607 During initialization you receive an error, COC-ERR-2607, and, in some instances, a Microsoft Office message, such as "File or assembly name Microsoft.Office.Interop.ApplicationName, or one of its dependencies, was not found." This error indicates that a required application or the .NET support for one of the required Microsoft Office applications is not installed.

Microsoft Office Excel, PowerPoint, and Word and Microsoft .NET Programmability support for all three of these applications is required for Cognos 8 Go! Office to work properly.

Ensure that you have installed all three Microsoft Office applications and than the Microsoft .NET support has been enabled. For more information, see the Cognos 8 Installation and Configuration Guide.523953

Incorrect Format for the Prompt Value in Prompted ReportsWhen you refresh a prompted report using the Specified Value type, the prompt value does not display properly in the UseValue field.

Not all prompt values are affected. Some of the prompt properties appear as expected while others may look like this:

[great_outdoors_company].[Products].[Products].[Product line]->:[PC].[@MEMBER].[5~236]

In this example, the selected prompt value was "Golf Equipment" which is displayed properly in the Display Value prompt property.

In cases where this occurs, you must know that the equivalent format in the Specified Value is the value with which you want to refresh the report. In the example, that [great_outdoors_company].[Products].[Products].[Product line]->:[PC].[@MEMBER].[5~236] is equivalent to Golf Equipment.

To refresh the report, we recommend that you use the Always Prompt option. That way users can select the value from the report’s own prompt dialog box.

Steps1. From the Manage Data tab, click the report to display the report properties.2. Expand the prompt properties.

46


3. In the Type box, click Always Prompt.4. Refresh the report.

The report refreshes with the requested parameters. Note: This does not affect the import of prompted reports.510323

DPR-ERR-2079 Firewall Security Rejection Error While Running Report After Expired Session

If you run a report after your session has expired and then try to navigate off the first page of the report, you encounter the following error message: DPR-ERR-2079 Firewall Security Rejection. Your request was rejected by the security firewall. CAF rejection details are available in the log. Please contact your administrator.

After an expired session, you must log on again.

Steps1. In the report list, right-click the top node item.2. Click Log On.3. Provide your authentication credentials as prompted and click OK.

522441

Cognos 8 Go! Office Does Not Start in Microsoft WordYou open a Cognos 8 Go! Office session in Microsoft Word, but nothing appears to happen.

This can occur if Microsoft Outlook has opened a session of Microsoft Word to edit email messages. To check whether you are using Word to edit emails, in Microsoft Outlook, click Tools, Options, Mail Format. In the Message format section of the dialog box, verify the options for editing your emails.

To resolve this problem, close Microsoft Outlook before opening the Microsoft Word document configured for Cognos 8 Go! Office.nbna

Readme 47


48

Chapter 2: Cognos 8 Documentation Updates

This section contains information about Cognos 8 BI documentation updates.

GeneralIf Cognos 8 documentation refers to the Impromptu Catalog and Report Migration User Guide or the Cognos 8 Migration User Guide, please note that these books have been replaced by the Cognos 8 Migration and Upgrade User Guide.

Build Application Wizard HelpThis section contains additions and corrections that will appear in the next version of the help for the Build Application Wizard that is available in Cognos Configuration.

Select the Application to BuildCognos 8 files must be packaged into an archive file that will be used to deploy Cognos 8 in the application server environment.

Begin this task after you have configured Cognos 8 to run within the application server.

Steps1. Select the Cognos 8 check box to deploy the Cognos 8 dispatcher application files to the

application server.2. Select the Include static files from the Webcontent folder check box if you are using the

application server to service your static content.Choose this option if you are deploying the entire application, which includes both run-time components (servlets) and static pieces (HTML files and graphic images).Otherwise, if you are using other components in your topology, such as a Web server or servlet gateway to serve static components, do not select this option.

3. Clear the Include the documentation and samples files from the Webcontent folder check box only if your application deployment fails. By default, if the Include static files from the Webcontent folder check box is selected, the documentation and sample files are included. We recommend that you ensure that this option is selected if you are deploying static content.

4. Select the Servlet gateway check box if you are using the application server as a gateway.5. Clear the Include the documentation and samples files from the Webcontent folder check box

only if your application deployment fails. By default, if the Include static files from the Webcontent folder check box is selected, the documentation and sample files are included. We recommend that you ensure that this option is selected if you are deploying static content.

6. Select the Application Server Type.Select JBOSS for a JBoss application server only.

7. Click Next to proceed to the next page of the wizard.542722

Readme 49


Cognos 8 Architecture and Deployment GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Architecture and Deployment Guide.

Server LocaleThe server locale ensures that all log messages are in one language. It is configured during installation. In a distributed environment, each Cognos 8 server obtains the server locale from Content Manager.

Do not change the server locale after specifying any Cognos groups or roles as part of security modeling within your environment. As well, if more than one Content Manager exists in your Cognos 8 installation, ensure that the server locale is set to the same value for all Content Managers.

Cognos 8 Installation and Configuration GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Installation and Configuration Guide.

Configure Cognos Components to Run Within the Application ServerCognos 8 must be configured with the application server configuration information, and the configuration must be saved to create new cryptographic keys. Cognos Configuration uses the JVM that is defined by the JAVA_HOME environment variable.

Important: You must set the JAVA_HOME environment variable to the JVM supplied or used by the application server and then copy the security provider files before you run Cognos Configuration.

Steps1. From the c8_location/bin directory, start Cognos Configuration:

• On Windows, type cogconfig.bat in a command window or select Cognos Configuration from the Start menu.

• On UNIX or Linux, type cogconfig.shIf you have existing incompatible encryption keys, you will be prompted to automatically generate new ones at this time.Tip: Ensure that the existing keys are backed up to a secure location before proceeding. There is no undo action available after you generate new keys.

2. Use the Build Application Wizard to create the application file that will be deployed to the application server. To launch the Build Application Wizard from Cognos Configuration under Actions, click Build Application Files. The wizard allows you to select the type of application to build and the context root used to access the application.You must build the application file on the same computer on which you will be deploying the file. The context root value entered in the wizard must be the same as is entered in the Environment tab, and used to deploy to the application server. The default context root and application directory name is p2pd, which can be used in most cases. Other default application deployment values, such as the application name, may be changed to better suit your environment.Tip: It is not necessary to rebuild or redeploy the archive file when you make configuration changes because configuration information is stored externally. For WebLogic and JBoss, you can use the Build Application wizard in Cognos Configuration to build the application to an expanded directory.

50


For example, for WebLogic, you put the application in C:\bea\user_projects\domains\apps\p2pd, where p2pd is the name of the application. When deploying the application from the WebLogic Administration Console, you would select the p2pd directory.Important:For JBoss, if you use the Expand files into a folder option, you must include the .war extension in the name of the folder where the wizard will create the p2pd application. When the wizard prompts for the folder location, go to JBoss_location/server/instance_name/deploy and create a folder named p2pd.war. For information about which type of application file, WAR or EAR, is supported in your environment, see your application server documentation.

3. In the Explorer window of Cognos Configuration, expand Environment and then change the following properties to use the port number and host name or IP address of the server where the Cognos 8 component and application server are installed. • All URIs for the dispatcher, including

Dispatcher URIs for GatewayExternal dispatcher URIInternal dispatcher URIDispatcher URI for external applications

• Gateway URI• Content Manager URIsThe application server must be configured to listen on the host name or IP address entered in the URI. For more information, see your application server documentation.If you change the context root from the default value of p2pd, you must change the URI as well.

4. Under Environment, Cognos 8 service, right-click Cognos 8, and then click Delete.The entry for the Cognos 8 service is used to configure environment settings for running under Tomcat. The entry is not required when using a different application server.

5. Complete other required configuration changes such as• specifying properties for the Content Manager database• entering user IDs and passwordsIf you used the default settings for the Cognos installation, you may only have to make minor changes to the default configuration settings. You can review the configuration for single computer installations or for distributed installations to determine if there are any additional changes required.

6. Save the configuration. New cryptographic keys are created using the JVM that is defined by the JAVA_HOME variable.

7. Close Cognos Configuration.542722

Enable or Disable Cognos 8 Go! Office Functionality for COM Add-in UsersUsers who deploy Cognos 8 Go! Office using the COM add-in can enable or disable the Cognos 8 Go! Office functionality using a tool bar option. The functionality is enabled or disabled the next time the document is opened.

The tool bar option for COM Add-in Users is available only if you installed Cognos 8 Go! Office using the Just Me option. If you installed it using the Everyone option, the following steps do not apply.

Steps1. Start your Microsoft Office application.2. From the Tools menu, click Customize.3. Click the Commands tab.4. Under Categories, click Tools.

Readme 51


5. Under Commands, click COM Add-Ins and drag it up to a toolbar.6. Click Close.7. In the toolbar, click COM Add-Ins.8. If Cognos 8 Go! Office is not in the list under Add-Ins available, do the following:

• Click Add.• Browse to where you installed the Cognos 8 Go! Office files.• Select the add-in file, which uses one of the following name formats, depending on your

system:COMAddInShim.dllCOMAddInShimXP.dllCOMAddInShim2K3.dll

• Click OK.9. Select or clear the Cognos 8 Go! Office check box, and click OK.

The changes are applied the next time you open a Cognos 8 Go! Office file.

Cognos 8 Administration and Security GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Administration and Security Guide.

Access PermissionsNote: This topic will include the following addition in the next version of the Cognos 8 Administration and Security Guide.

Accessing Objects Associated with Data Sources Secured Against Multiple NamespacesData sources in Cognos 8 can be secured against multiple namespaces. In some environments, the namespace used to secure the data source is not the primary namespace used for access to Cognos Connection. When you try to access an object, such as a report, a query, or an analysis, that is associated with a data source secured against multiple namespaces, and you are not logged on to all of the required namespaces, a prompt for authentication appears. You must enter the required credentials to log on to the namespace before you can access the object.

When single signon (SSO) is enabled, the prompt for authentication does not appear. You are automatically logged on to the namespace.

This functionality applies to Cognos Viewer only. If you run into a similar situation in a Cognos 8 studio, you must quit your task and log on to all the namespaces that you want to use in the current session.

Set Query PrioritizationThis topic will be added to the Server Administration chapter in the Administration and Security Guide in a future release.

When a report with prompt controls is run, all parameter information is retrieved, including parameter information defined in the report, the model, and the data source. This is required for data typing and to align capabilities for a prompt control with those of its associated parameter. This operation can impact performance, especially when there are many or complex queries. From the user perspective, it can take too long to present the first prompt page or report page.

52


To increase speed, report authors can set a query hint in Report Studio, Use For Parameter Info, to give a query priority in determining parameter information. In addition, queries are prioritized based on where they are used and whether they contain filters. A priority group is the set of queries sharing similar attributes, such as a filter. Instead of retrieving the parameters for all the queries at the same time, parameters for queries with author-defined priority are retrieved first, regardless of how automated query prioritization is set. For more information about parameters, filters, and prompt controls, see the Report Studio User Guide.

To specify a system-wide configuration that defines how queries and query groups are processed, you can set the report server advanced setting RSVP.PROMPT.RECONCILIATION with the settings shown next. By assigning either a setting value or name to RSVP.PROMPT.RECONCILIATION, you specify the degree of reconciliation between prompt control capabilities and data type to that of the associated parameter. The setting you choose determines whether reconciliation accuracy or speed is more important. For example, if the report author ensures that parameters are defined with the same datatype and capabilities (i.e., optionality, cardinality, and discreteness), across all queries, specifying CHUNKED or 3 would likely achieve the best performance in the widest variety of situations.

RSVP.PROMPT.RECONCILIATION.CHUNKSIZE lets you specify chunk size. This setting is applicable when you use CHUNKED GROUPED and CHUNKED. The default chunk size is 5.

The report server advanced properties and Report Studio query hints work cooperatively to provide the best performance.

RSVP.PROMPT.RECONCILIATION SettingsCOMPLETE or 0

All queries are sent at once. This is the slowest, most accurate form of reconciliation. This is the default setting.

GROUPED or 1

Queries are sent by priority group. This setting works best for reports that have many unfiltered queries and few filtered queries. It provides medium speed and high reconciliation accuracy.

CHUNKED GROUPED or 2

Queries are sent by priority group with a maximum number per request. The queries do not span groups. This setting works best on reports that have many queries with similar filter expressions. It provides maximum speed and low reconciliation accuracy.

CHUNKED or 3

Queries are sent by priority group with a maximum number per request. The queries can span groups.

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.

Steps1. In Cognos Connection, in the upper-right corner, click Tools, Server Administration.2. Click the Monitor tab.3. Select Services.4. Click the set properties button for the Report or the Batch Report service.5. Click the Settings tab.6. Click Edit next to Advanced Settings.7. Select Override the settings acquired from the parent entry.8. In the Parameter column, enter a parameter name.9. In the Value column, enter the setting that you want to use.10. Click OK.11. On the Set properties page, click OK.

Readme 53


Model-based vs. Report-based Drill-through AccessNote: This topic will include the following corrections in the next version of the Cognos 8 Administration and Security Guide, the chapter "Drill-through Access". • In the following sentence, the name "Report Studio" must be replaced with "Analysis

Studio":A model-based drill-through can be performed between any combination of Report Studio, Query Studio, and Cognos Viewer reports.

• The following sentence must be modified: This type of drill-through can be used when you want to drill from Analysis Studio or Query Studio to any of the Report Studio, Query Studio, or Cognos Viewer target reports in the same, or different package.The correct version is:This type of drill-through can be used when you want to drill between any combination of Analysis Studio, Query Studio, or Cognos Viewer reports in the same or different package.

• The following paragraphs must be modified:The drill-through definition, if it exists, appears as a hyperlink in the source report. Usually this area of the report shows the data to be passed as a parameter. However, other values can be passed as well, or instead. The report-based drill-through is limited to Report Studio source reports and any target reports. This type of drill-through can be used when you want to pass the parameter results within a source report to the target report, the results of a report expression to a target report, or a URL link as a part of the drill-through.The correct version is:The drill-through definition, if it exists, appears as a hyperlink in the source report when it is run.The report-based drill-through is limited to Report Studio source reports and any target reports. This type of drill-through can be used when you want to pass the data item values or parameter results within a source report to the target report, the results of a report expression to a target report, or a URL link as a part of the drill-through definition.

Members and ValuesNote: This topic will include the following corrections in the next version of the Cognos 8 Administration and Security Guide, the chapter "Drill-through Access".

The following sentences must be modified:

If the target parameter is a value, the source can be either a value or a member. The source can be a member if the level is mapped to the data item correctly, or if the business key from which the member is sourced matches the business key in the relational target.

The correct version is:

If the target parameter is a value, the source can be either a value or a member. If the source is a dimensional member, you must ensure that the level or dimension is mapped to the target data item correctly in the drill through definition. The business key from which the member is sourced must match the value in the relational target, which is most often the business key.

Business KeysNote: This topic will include the following corrections in the next version of the Cognos 8 Administration and Security Guide, the chapter "Drill-through Access".• The following sentences must be modified:

When performing a drill-through from a member to a relational value, the business key of the member is passed. This means that your relational target parameter must be set up using the business key data item.The correct version is:

54


When performing a drill-through from a member to a relational value, the business key of the member is passed. This means that your relational target parameter must be set up using the data item with a matching value, which is most often the business key data item.

• The following sentence must be added to the topic:MSAS 2005 multi-part business keys are not supported in drill-through operations.

ScopeNote: This topic will include the following corrections in the next version of the Cognos 8 Administration and Security Guide, chapter "Drill-through Access".

The following sentence must be modified:

It defines when the drill-through path is made available, or when the target report is shown to the users based on the items they have in the source report.


It defines when the target report is shown to the users, based on the items they have in the source report.

Set Up Drill-through Access in a PackageNote: This topic will include the following corrections in the next version of the Cognos 8 Administration and Security Guide, chapter "Drill-through Access".

The following sentence must be modified:

The drill-through path defined in the drill-through definition appears in any report based on the source package.


The drill-through path defined in the drill-through definition is available for any report based on the source package.

Cognos 8 Analysis Studio User GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Analysis Studio User Guide.

Suppressing Empty CellsNote: This topic will include the following additional information in the next version of the Analysis Studio User Guide

Early versions of Analysis Studio remove empty cells from crosstabs using totals-based suppression. This method is a convenient way to remove rows or columns where the total results in a null or zero value throughout the analysis. However, there are instances when this method is impractical. For instance, both the rows and columns in the crosstab must be made up of non-measure sets, such as names, countries, dates, and so on. Analysis Studio cannot use the totals-based suppression feature for a row or column if the opposite row or column contains a measure set or multiple measure sets. You create measure sets when you insert a measure such as Revenue as a row or column instead of in the top left cell.

For example, you create a crosstab in which you insert Employees for the rows and Revenue for the column. Because the set on the opposite axis from Employees contains a measure set, the suppression feature is unavailable.

Another issue concerns the summary lines in nested sets. When using totals-based suppression in nested sets, the crosstab retains the summary line of the suppressed subgroup.

Readme 55


For example, you create a crosstab that contains products nested in sales years in the rows and sales territories in the columns, with revenue as the default measure. The uppermost subgroup of the nested rows contains a zero for all values. You apply the suppression feature to the rows. Even though the top row contains nothing but zero, it does not go away.

Selection-based suppression is an alternative approach that gives you control over the individual rows and column you want to suppress. This is practical when working with nested and multi-measure crosstabs.

For example, you could suppress the top row in the previous example by selecting a column and clicking Suppress Rows from the right-click menu.

The suppression functionality available to you is determined by a setting configured by the administrator, and may be either totals-based or selection-based.

Cognos 8 Analysis Studio Quick TourThe next version of the Analysis Studio Quick Tour will include the following corrections.• The suppress button shown on the toolbar is incorrect. The correct icon appears in Analysis

Studio.

Cognos 8 Event Studio User GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Event Studio User Guide.

There are no documentation updates at this time.

Framework Manager User GuideThe Framework Manager User Guide includes procedures, examples, notes, tips, and other background information to help you create a project, prepare a model for reporting, and create and publish a package.

Additions and corrections will appear in the next version of this document.

Upgrading the ModelNote: This topic will include the following addition in the next version of the Guidelines for Modeling Metadata and the Framework Manager User Guide.

When upgrading a model to Cognos 8, it is important to understand that if you upgrade query subjects to dimensions, you are changing the names of the query items in your model. For example, a query item previously qualified as namespace.query subject.query item now has the name namespace.dimension.hierarchy.level.query item.

Because this name change is likely to invalidate existing reports, we recommend upgrading query subjects to dimensions only when you want to leverage an existing model to build a new application that requires dimensional capability. 504978.1

Converting Query Subjects with Dimension Information to Regular DimensionsNote: This topic will include the following addition in the next version of the Guidelines for Modeling Metadata and the Framework Manager User Guide.

After conversion, you must also review the _businessKey role. This role represents the key for the level and can be assigned to only one attribute in a level. It is also used to drill through from one data source to another because the business key should be consistent across your organization.

56


Note: Unlike dimension information, determinants are effectively inherited between data source and model query subjects. We now recommend that determinant information be specified as early as possible in the model, typically on the data source query subject. In cases where different determinants will be specified for different granularity control, you should either • create multiple instances of the data source query subject • remove determinants from the data source query subject and create new determinants on each

model query subject requiring different granularity control.504978.1

DeterminantsThe order in which determinants are specified governs the order in which they are evaluated. Only one determinant is applied at a time. Unlike a hierarchy with levels, it is not sufficient to specify the determinants in a particular order because they are evaluated individually at run time. The evaluation is based on the joins and query items that are relevant in the context of a query. You must ensure that the key for each determinant includes the key that identifies the data set as well as the key for other data sets that exist at higher levels and might be queried simultaneously.

Use determinants in the following cases:• Joins exist at multiple levels of granularity for a single query subject.

An example is the Time dimension in the Go Data Warehouse sample model. There are joins to the Time dimension on the day key and on the month key. Determinants are used for the Time dimension when you want to prevent double-counting for multiple-fact queries. In this case, you should specify at least two determinants, one at the month_key for reports requesting data at the grain of month. Select the Group By check box for this determinant because it is not the lowest level. The second determinant should be at day_key for reports at the day grain. The second determinant should include the month_key as well.Specifying determinants for time to clearly capture the functional dependency between month and day as a minimum prevents double-counting for those facts that join at the month key. It also ensures that the lowest-level determinant (day) is selected in a case where a query requests data below the common grain (that is, at the day grain).

• BLOB data types exist in the query subject. Querying blobs requires additional key or index type information. If this information is not present in the data source, you can add it using determinants. Override the determinants imported from the data source that conflict with relationships created for reporting.You cannot use multiple-segment keys when the query subject accesses blob data. With summary queries, blob data must be retrieved separately from the summary portion of the query. To do this, you need a key that uniquely identifies the row and the key must not have multiple segments.For example, there are determinants on two query subjects for multiple columns but the relationship between the query subjects uses only a subset of these columns. Modify the determinant information of the query subject if it is not appropriate to use the additional columns in the relationship.

• A join is specified that uses fewer keys than a unique determinant that is specified for a query subject. If your join is built on fewer columns than what is stored in Framework Manager within the determinants, there will be a conflict. Resolve this conflict by modifying the relationship to fully agree with the determinant or by modifying the determinant to support the relationship.

nbna

Defining DeterminantsNote: This topic will include the following addition in the next version of the Guidelines for Modeling Metadata and the Framework Manager User Guide.

Use determinants to ensure that the aggregation in reports is correct and that queries generate correctly.

Readme 57


For example, you have the following Time dimension:

Year Key Month Key Month Name Day Key Day Name

2006 200601 January 06 20060101 Sunday, January 1, 2006

2006 200601 January 06 20060102 Monday, January 2, 2006

You can definethree determinants for this data set as follows -- two non-unique determinants (Year and Month) and one unique determinant (Day). The concept is similar but not identical to the concept of levels and hierarchies.

The Year determinant will use the Year Key. It will have no attributes. The Uniquely Identified check box is cleared. The Group By check box is selected.

The Month determinant will use the Year Key and the Month Key. It will have the Month Name attribute. The Uniquely Identified check box is cleared. The Group By check box is selected.

The Month determinant is also a key but it is not unique, so the Uniquely Identified check box is not selected. Again, although only Month Key is needed to identify a month in the data, Year Key is included to ensure that the Month determinant is selected in a query that uses Year or an attribute of Month. If you want to query month from this Time dimension, you write a query that uses the select distinct syntax. This query would also be grouped by Month Key because the values are repeated. This is why the Group By check box is selected. The same logic is applied to the Year determinant.

The Day determinant will use the Year Key, the Month Key, and the Day Key. Because Day is the lowest grain of the table, you can associate all the columns in the table to this determinant. Because the day key is a unique key, the Uniquely Identified check box is selected. The Group By check box is not selected because it is not needed when data is unique. Year Key and Month Key are included in the key of the Day determinant to ensure that a query using either Year or Month as well as Day or an attribute of Day will use the Day determinant.

There is no concept of a hierarchy in determinants, but there is an order of evaluation. This means that when you write a query that uses columns from the previous table, Cognos 8 looks for references to those columns by examining each determinant, one at a time. Cognos 8 stops when it finds a match. For this reason, if a determinant has the Uniquely Identified check box selected, it automatically has all items in the query assigned as attributes, and it becomes the default determinant. nbna

Work with SAP BW Data in Cognos 8 PlanningNote: This topic will include the following additions in the next version of the Framework Manager User Guide.

Detailed fact query subjects are supported only for SAP BW InfoCubes. They are not supported for InfoQueries or MultiProviders.

It is possible to have more than one SAP BW InfoCube in a Framework Manager model and to create a detailed fact query subject for each of them. It is then possible to publish this entire model as a package. However, Cognos 8 Planning can only use the package if the Planning user selects one InfoCube per link. You can work around this by publishing each InfoCube within a model in its own package.

When you create and publish the package, the detailed fact query subject and its related SAP star schema folder must be marked as hidden in the package because these objects are not supported for the Cognos 8 studios. Cognos 8 Planning can access hidden objects in the package.

Cognos 8 Getting StartedThis section contains additions and corrections that will appear in the next version of Cognos 8 Getting Started.


58


Cognos 8 Go! Office User GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Go! Office User Guide.


Cognos 8 Metric Studio User GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Metric Studio User Guide.

Equations (.equ)Note: This topic will be added to the Metric Studio User Guide in a future release.

The .equ file contains the components for formula-based equations (for metric types). This file is for internal use during data export and data import. You must import the equation items (.eqi) file when you import the equations (.equ) file.

Do not manually modify the .equ file. Changes to this file are not supported by Cognos.

Equation Items (.eqi)Note: This topic will be added to the Metric Studio User Guide in a future release.

The .eqi file contains the components for formula-based equations (for metric types). This file is for internal use during data export and data import. You must import the equation items (.eqi) file when you import the equations (.equ) file.

Do not manually modify the .eqi file. Changes to this file are not supported by Cognos.

Cognos 8 Query Studio User GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Query Studio User Guide.


Cognos 8 Report Studio User GuideThis section contains additions and corrections that will appear in the next version of the Cognos 8 Report Studio User Guide.

ReportOptionNote: This topic will include the following corrections in the next version of the Report Studio User Guide and the Framework Manager User Guide.

In the Using the Expression Editor appendix, this topic in the Report functions section indicates that the syntax for the ReportOption function isReportOption(optionName)

The correct syntax to use isReportOption('optionName')520550, 546444

Readme 59


Applying Filters to Dimensional ReportsNote: This topic will be added to the Report Studio User Guide in a future release.

Dimensional data sources do implicit rollup at all levels of each dimensional hierarchy. Detail filters, summary filters, and slicers with more than one member invalidate any precomputed rollup of members at hierarchy levels above the level at which the filter applies. Because of this, we recommend that you avoid combinations of filters and slicers with members at these hierarchy levels.

You can apply the following filters to a dimensional report:• Detail filters and summary filters in grouped list reports with no dimensional expressions

other than members or attributes of a level.• Detail filters and summary filters in crosstabs, applied to the detail level of the report,

combined with the aggregation type within detail or within aggregate.Each crosstab row or column must represent only one level.

• Dimensional expressions that use the filter function, provided that the condition is independent of context.The condition in the filter function must be written so that it returns the same value regardless of what it intersects with elsewhere in the report. One way to do this is to use the completeTuple function.For example, you may have one of the following expressions:filter([Products], [Revenue]>1000)filter([Products], tuple([Revenue], currentMember(hierarchy([Products]))) >1000)If you do, change it to the following expression:filter([Products], completeTuple([Revenue], currentMember(hierarchy([Products]))) >1000)This ensures that the default member of all other dimensions is used in the condition, which returns the same result at all intersections.

• Slicers with a single member per dimension.

When you use any of these filters with a calculated fact or measure, you may see #Error! as values for some or all of the cells in the report that represent an aggregate that is calculated in the database (aggregate function is set to Automatic). This means that the data source is unable to compute these values. You can work around this by using an explicit rollup rule or aggregation function such as Total. However, do this only if you are familiar with the data and absolutely certain that this is the correct answer for that report.nbna

Setting Object PropertiesNote: This topic will include the following additions in the next version of the Report Studio User Guide.

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.• The Text indent value in the Spacing and Breaking dialog box.

Creating Burst Reports Using a Dimensional Data SourceNote: This topic will include the following additions in the next version of the Report Studio User Guide.

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.

60


491948 491952

Connecting Queries Between Different Data SourcesNote: This topic will be added to the Working with Queries section in the Report Studio User Guide in a future release.

Cognos 8 supports the following:• 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

You cannot create the following types of joins:• cube-to-cube (homogeneous)• cube-to-cube (heterogeneous)• cube-to-RDBMS• cube-to-SAP BW• SAP-BW-to-RDBMS

Remove Upgrade MessagesNote: This topic will include the following corrections in the next version of the Report Studio User Guide.

When you open a report that was created in a previous version of Report Studio, any problems detected during the upgrade process appear in the Upgrade Information dialog box. You must fix any errors in the report and then validate the report before you can run it. If only warnings and information appear in the dialog box, these will disappear when you click OK.

Tip: To view this dialog box again as you are fixing errors, from the File menu, click Upgrade Information.

Set OptionsNote: This topic will include the following corrections in the next version of the Report Studio User Guide.

The following options in the Options dialog box were deleted.• Group properties• Show hidden layout objects

The following option was added to the Options dialog box:• Use system clipboard

If Report Studio is running in Internet Explorer, uses the Windows clipboard instead of the internal application clipboard.Tip: If Report Studio is running in Firefox, the internal application clipboard is always used.

Report Studio PropertiesNote: This topic will include the following corrections in the next version of the Report Studio User Guide.

The Report Studio property Allow Is Missing was deleted.548298

Readme 61


Visual Aids ButtonNote: This topic will include the following corrections in the next version of the Report Studio User Guide.

The description for the Show hidden objects option is as follows:

Shows objects for which the Box Type property was set to None or for which the Visible property was set to No.

Set Up Drill-through Access in a ReportNote: This topic will include the following corrections in the next version of the Report Studio User Guide and the Administration and Security Guide.

The following steps in this topic will be updated:

Step 3In the Usage box, specify what to do when the target parameter is not fulfilled as part of a drill-through:• To specify that users must click a value in the source report, click Required.

If the parameter is not fulfilled and it is required, users are prompted to choose a value.• To specify that users do not need to click a value in the source report, click Optional.

Users are not prompted to click a value if the parameter is not fulfilled.• To specify not to use the parameter, click Disabled.

The parameter is not used during the drill-through.

Step 6If you want the report to be used as the source during a package drill-through, do the following:• From the Data menu, click Drill Behavior.• Select the Allow drill through from a package check box and click OK.

Cognos 8 Troubleshooting GuideThis section contains additions and corrections that will appear in the next version of Cognos 8 Troubleshooting Guide.


62

Chapter 3: Deprecation Notices

This section contains information about Cognos 8 BI deprecation notices.

Supported EnvironmentsThe following list describes important information related to Cognos 8 supported environments:• SAP ended mainstream maintenance support for SAP BW versions 3.1c and 3.0b in December

2006. Cognos will continue compatible support for these versions in this Cognos 8 release. Cognos will deprecate support for SAP BW 3.1c and 3.0b in the next major release of Cognos 8.

• Informix ended support for Dynamic Server version 9.3 in April 2005. Cognos has deprecated support for this version in this Cognos 8 release.

• Informix ended support for Dynamic Server version 9.4 in April 2006. Cognos will continue compatible support for this version in this Cognos 8 release. Cognos will deprecate support for Dynamic Server version 9.4 in the next major release of Cognos 8.

• Informix ended support for Red Brick Decision Server version 6.2 in April 2006. Cognos will continue compatible support for this version in this release. Cognos will deprecate support for this version in the next major release of Cognos 8.

• Cognos will discontinue support for Netscape browsers in the next major release of Cognos 8.• Sun ended support for Sun ONE Directory Server version 5 in June 2004. Cognos will

continue compatible support for this version in this Cognos 8 release. Cognos will deprecate support for Sun ONE Directory Server version 5 in the next major release of Cognos 8.

• Cognos support for SAP NetWeaver Portal 7.0 (SAP NetWeaver 2004s) is pending in this Cognos 8 release.

nbna

Framework Manager Security Filters for SAP BW: Notice of Intent to Change the Default Setting

In all shipped versions of Cognos ReportNet and Cognos 8 including Cognos 8.2, the following behavior has been enabled by default.

Multiple security filters defined within Framework Manager on metadata imported from SAP BW sources are combined using 'AND' logic, effectively an intersection of a particular user's permissions. This behavior is contradictory to corresponding behavior on relational data sources where similar filters are combined using 'IN' and 'OR' (union) logic to facilitate cases where users belong to one or more group and require a union of their permissions. The current default behavior for SAP BW datasources has been determined to be a product defect and will be changed in the Cognos 8.3 release to align with the behavior of relational data sources. In the Cognos 8.1 Mr2 and Cognos 8.2 releases, it will be possible to get the union of filters behavior by modifying the following switches in the qfs_config.xml configuration file. Under <provider name="OlapQueryProvider" libraryName="oqp">, add the following new <parameter> element:<parameter name="ORingSecurityFiltersWhenUserBelongsToMultipleGroups" value="true"/>

Readme 63

Chapter 3: Deprecation Notices

EffectWhen multiple security filters are defined in the Data Security setting in Framework Manager for a query subject, if a user belongs to more than one user group associated with these filters, the effect of this switch is to perform a union of these filters instead of an intersection. For example, if a user Joe belongs to a corporate group allowing him to see data for Asia, Europe, and America, and also belongs to a regional group allowing him only to see data for Europe, the effect of the switch will be to let Joe see data for Asia, Europe, and America (as compared to just Europe) when logging on Cognos 8 and authoring or running a report. Note that security filters that are based on other security filters in the Data Security settings for a query subject continue to be intersected, just as before, independent of whether or not the new switch is activated.

As of Cognos 8.3, this behavior will become the new default for SAP BW metadata in Framework Manager. There will be no change to the behavior of security filters applied on relational sources. The switch will continue to be available and can be set to false by your administrator if required to maintain existing application behavior.

64

Index

Symbols.eqi, 59.equ, 59.pro files, 56

Aa socket reported a communication error, 17accented characters

not displayed properly, 12access permissions

documentation updates, 52accessing data sources, 22, 23actions

notification email, 34Administration and Security Guide, 52Adobe Acrobat

Web link errors in 7.x, 20Adobe Reader

versions required for printing reports, 21aggregate type

rollup, 28aggregates

footers calculated differently, 28AIX

version, IBM WebSphere, 15Allow Is Missing property, 61Analysis Studio

context filter limitations, 30custom sets, 30dashes appearing instead of values, 30empty dimensions, 44Excel reports, 30instability with MS SQL Server 2005, 11Japanese Internet Explorer, 30limitations, 29User Guide doc update, 55wrong currency symbol, 30

Analysis Studio quick tour, 56Analysis Studio User Guide, 55Apache

Web server and help problems, 21application servers

selecting in the Build Application Wizard, 49applying

filters to dimensional reports, 60Architecture and Deployment Guide, 50as percentage

values, 32attribute-based sorting, 32

Bbackslashes appear instead of currency, 12BEx queries

hierarchies in characteristic structures, 44blank values

appearing instead of totals, 28BME script player

errors, 41Build Application Wizard

documentation updates, 49selecting the application server, 49

burstingMOLAP data, 60

business keysdocumentation updates, 54

Ccalculated

metrics, 34calculated key figures, 25calculated metrics

constants, 35calculations

CognosViewer, 32format rules, 55in filters, 43SAP BW, 42SAP BW data sources, 24user-defined functions, 42

calendardelete periods, 36

calendar settingsmetric types, 35

changes to decimal formats, 18changing

package reference, 32character display

incorrect, 35character encoding

and help problems with Apache Web server, 21characteristic structures

hierarchies, 44characters improperly displayed, 12charts not appearing, 16COC-ERR-2607, 46Cognos 8

integration with Cognos Planning, 15Cognos 8 Go! Office

disabling for COM add-in users, 51DPR-ERR-2079 Firewall Security Rejection error, 47expired sessions, 47incorrect format for prompt values, 46

Readme 65

Index

installation and configuration issues, 45known issues, 45opening in Microsoft Word, 47

Cognos 8 Go! Office errorsCannot Open a Report in Excel in Cognos Connection If

You Have a COM Add-in Workbook Open, 45No Report Content Is Imported When the Report Name

Contains a Single Quote, 46The Cognos Action Pane Disappears When Using the

Smart Client and You Run a Report in Excel in Cognos Connection, 46

Workbook Closes Unexpectedly If Name Contains Square Bracket, 45

Cognos 8 Mobile Analysischoosing the installed product language, 14

Cognos 8 Planning and SAP BW data, 58Cognos 8 Transformer

choosing the installed product language, 14Cognos Planning

integration with Cognos 8, 15Cognos Planning - Contributor

connecting to data source, 17Cognos PowerCubes

open slowly, 17Cognos Viewer

calculations, 32configuration settings, 32configuring

Cognos 8 for application servers, 50issues with Cognos 8 Go! Office, 45

context filter limitations, 30, 31converting

query subjects, 56copyright, 2creating package

fails, 33crosstabs

aggregate values not appearing, 28incorrect running totals, 27no data returned when same dimension used on both

edges, 24set expressions that depend on current measure return

incorrect data, 27cubes

PowerCubes open slowly, 17currency

won, 12yen, 12

currency valuesappear as numbers in reports, 19

custom formattingnot appearing for empty cells, 24

custom sets in Analysis Studio, 30

Ddashes

appearing instead of values in Analysis Studio, 30data sources

connecting to Cognos Planning - Contributor, 17unable to open a cube using 8.2 DB2 OLAP, 23unable to open a cube using Essbase 7.1, 23

date formatSQL Server 2005, 34

DB2incorrect average value, 23incorrect count value, 23Metric Studio, 33

DB2 data sourcesproblems accessing, 22

DB2 OLAPquery failure using DB2 OLAP Server, 22unable to load library, 12unable to open a cube using 8.2 DB2 OLAP, 23

DB2-ERR-0028, 12decimal formats

changes, 18default setting

SQL Generation, 45delete

time periods, 36detailed fact query subjects, 58determinants, 57diagram

error, 33dimensional functions, 43dimensions, 56

converting from query subjects, 56empty in Analysis Studio, 44functions, 43order of members, 44overlapping named set levels, 19testing, 43

documentationAdministration and Security Guide, 52Analysis Studio quick tour, 56Analysis Studio User Guide, 55Architecture and Deployment Guide, 50broken links, 18Getting Started, 58help for Build Application Wizard, 49Installation and Configuration Guide, 50Metric Studio User Guide for Authors, 59Query Studio User Guide, 56, 59Report Studio User Guide, 59Troubleshooting Guide, 62

documentation CD, 18documentation updates

access permissions, 52business keys, 54drill-through access, 54, 55Framework Manager User Guide, 56scope, 55

double-byte charactersimproperly displayed, 12

DPR-ERR-2002 error message, 12DPR-ERR-2079 Firewall Security Rejection error, 47drill-through access

documentation updates, 54, 55setting up in a report, 62

drill-through performance, 18

66

Index

Eembedded externalize method, 45environments

supported, 63error messages

COC-ERR-2607, 46errors

a socket reported a communication error, 17DB2-ERR-0028, 12opening Web browser, 35TR0118, 44

Essbaseincorrect average value, 23incorrect count value, 23

EssBase 7.1unable to open a cube, 23

Essbase changes, 21Event Studio

parsing error, 29Excel functions, 20Excel reports

Analysis Studio, 30expand command in Analysis Studio, 30expired sessions

Cognos 8 Go! Office, 47export

failing in a distributed installation, 35exporting

InfoCube, 45IQD files, 44

Expression EditorReportOption function, 59

externalized dimensions, 44externalizing query subjects, 45extracting

InfoCube, 45

Ffail

creating package, 33file not found errors, 18files

adding multiple IQD, 38filter expressions

no data, 25filters, 44

applying to dimensional reports, 60calculations, 43invalid, 37

Find Report Dependencies window, 45footers

aggregate computed differently, 28not working for some semi-additive measures, 21

format rulescalculations, 55

formatschanges to decimals, 18

Framework ManagerIQDs and Oracle stored procedures, 44issues, 40missing connections and credentials, 37

security filters change for SAP BW, 63TR0118 error, 44unable to load DB2 OLAP library, 12user language preference, 37

Framework Manager User Guidedocumentation updates, 56

full outer joinsOracle, 42

functionsdimensions, 43order of members, 44ReportOption, 59user-defined, 42

GGetting Started

documentation updates, 58grouping

first level in a list, 27grouping columns

SAP BW data sources, 24

Hhelp

problems with Apache Web server, 21hierarchies

characteristic structures, 44history chart

error, 33hyperlinks

errors in Acrobat 7.x, 20

IIBM WebSphere

AIX version, 15import

failing in a distributed installation, 35importing

system objects, 41incorrect average value using DB2 or Essbase, 23incorrect count value using DB2 or Essbase, 23InfoCube

exporting, 45Informix

isolation level, 42Informix Dynamic Server

supported environments, 63Informix Red Brick Decision Server

supported environments, 63inner joins

SQL Generation setting, 45instability

in MS SQL Server 2005, 11installation

choosing the language for Cognos 8 Mobile Analysis, 14choosing the language for Cognos 8 Transformer, 14

Installation and Configuration Guide, 50installation and configuration issues

cannot load DB2 OLAP library, 12run-time errors, 12

Readme 67

Index

installingCognos 8 on Linux, 12issues with Cognos 8 Go! Office, 45

Internet Explorerissues with charts in version 6.x, 16

IQD filesadding multiple, 38problems exporting, 44replace function, 38

isolation level, 42issetup

corrupt Japanese characters, 12

JJapanese

incorrect import, 37Japanese characters corrupted, 12Japanese currency, 12Japanese Internet Explorer

Analysis Studio, 30JBoss

selecting in the Build Application Wizard, 49join relationships

creating in Report Studio, 61joins

Oracle, 42SQL Generation setting, 45

Kkey figures, 25, 44known issues

administration, 16Analysis Studio, 29Cognos 8 Go! Office, 45Cognos 8 Transformer, 25Cognos Connection, 22DB2 data sources, 22Event Studio, 29Framework Manager, 40general, 17installation and configuration, 11Metric Studioknown issues, 33Query Studio, 26Report Studio, 27SAP BW data sources, 23security, 15Series 7 integration, 15software development kit, 45

Koreantilde, 35

Korean currency, 12

Llanguage

choosing for Cognos 8 Mobile Analysis, 14choosing for Cognos 8 Transformer, 14

languagesOLAP data sources, 31

limitations in Analysis Studio, 29links

errors in Acrobat 7.x, 20Linux

characters not displayed properly, 12lists

grouping on first level, 27locales

server, 50logon problems

SAP namespace, 15, 16lost settings

after import, 33

Mmeasures, 44

SAP BW data sources, 24semi-additive and footers, 21

members, order of, 44memory footprint, 45metadata query failure with DB2 OLAP server, 22Metric Designer

construct functions, 39data sources not supported, 39day level time period filter, 40error for extract containing static text-type scorecard

levels, 39error when query items mapped to metrics qualifiers are

referenced in scorecard filters, 39extracts, 37filters on parent-child hierarchies not supported for

OLAP, 39known issues, 36metric filters invalid after upgrading a model, 37metrics scope page does not work, 39missing connections and credentials, 37problem executing extract from a Teradata database, 38qualifiers for PowerCube import sources, 39scorecard tree preview does not work, 39typed-in constant metric attribute values, 39user language preference, 37

metric filters not updated correctly, 37Metric Studio

additional columns in Project tab-delimited file, 56DB2, 33lost settings, 33

Metric Studio User Guide for Authors, 59metric types

calendar settings, 35lost settings, 33

metricsnot created, 34

Microsoftsecurity patch causes server failure, 11

Microsoft .NET programmability support, 46Microsoft SQL Server 2005

stability issues, 11missing

calculated metrics, 34Mozilla Firefox

problems with help using Apache Web server, 21

68

Index

Nnamed sets

nested or parallel sets overlapping, 19nested reports

changes to SAP BW rules for set expression evaluation, 19Netscape

supported browsers, 63Netscape Navigator

problems with help using Apache Web server, 21

OOLAP data sources

languages, 31Oracle

full outer joins, 42NLS_LANG environment variable, setting, 35package creation, 33replace function, 38running on 10g, 34

order of members, 44outer joins

Oracle, 42

Ppackage

creation fails, 33package reference

changing, 32parsing error in Event Studio, 29passwords

SAP namespace, 15PDF

unsupported style properties, 60PDFs

Web link errors in Acrobat 7.x, 20performance

drill-through, 18optimizing PowerCubes for Cognos 8, 17

permissionschanging, 41

pivoting to a crosstab, 28ports

setting the maximum number for program use, 22PowerCubes

multiple hierarchies, 25open slowly, 17

printer friendly pagecharacter display, 35

printingafter restarting dispatcher, 35

printing reportsAdobe Reader versions required, 21

prioritizing queries, 52problems

report options, 32SAP namespace, 16searching, 32

problems accessing DB2 data sources, 22problems accessing SAP BW data sources, 23prompted reports

Cognos 8 Go! Office errors, 46prompts

key figures, 44

Qqueries

do not execute, 25prioritizing, 52

query failure with DB2 OLAP server, 22query items

retargeting, 41upgrading, 56

Query Studio User Guide, 56, 59query subjects

converting to dimensions, 56detailed fact, 58determinants, 57dimensional functions, 43externalizing, 45upgrading, 56

quick toursdocumentation update, 56

Rragged hierarchies

Report Studio, 20refreshing

segments, 41regular dimensions

order of members, 44relational data sources

footers and semi-additive measures, 21relationships

creating joins in Report Studio, 61replace function

IQD, 38report options

problems, 32report server settings, 52Report Studio

aggregate values not appearing, 28Allow Is Missing property, 61bursting on MOLAP Data, 60creating join relationships, 61Key Transformation validation level returns partial

information, 28no data returned when same dimension used on both

edges of crosstab, 24ragged hierarchies, 20set options, 61style properties not supported, 60unable to run Cognos 8.2 reports in Cognos 8.1, 27unbalanced hierarchies, 20

Report studiopivoting to a crosstab, 28

Report Studio User Guide, 59ReportNet 1.1 documentation updates

Framework Manager User Guide, 56ReportNet 1.1 issues

Framework Manager issues, 40ReportOption, 59

Readme 69

Index

reportsapplying filters to dimensional reports, 60currency values appear as numbers, 19errors when running, 45no data returned when same dimension used on both

edges of crosstab, 24report execution fails, 12setting up drill-through access, 62unable to run Cognos 8.2 reports in Cognos 8.1, 27upgrade messages, 61

retargeting query items, 41rollup

aggregate type, 28RSVP.PROMPT.RECONCILIATION settings, 52running

reports, 45running totals

incorrect in crosstabs, 27run-time errors, 12

Ssamples

error in ELM Returns Agent sample, 29SAP

password policy, 15SAP BW

key figures, 25security filter change in Framework Manager, 63set expression evaluation rules changes, 19supported environments, 63

SAP BW calculations, 42SAP BW data and Cognos 8 Planning, 58SAP BW data sources

calculations, 24grouping columns, 24measures, 24problems accessing, 23sectioning reports, 24summary rows, 25

SAP namespacelogon problems, 15, 16repeated prompts for authentication, 16

SAP NetWeaver Portalsupported environments, 63

scopedocumentation updates, 55

scorecardslost settings, 33

script playererrors, 41

searchingproblems, 32

sectioning reportsSAP BW data sources, 24

securityfilter change in Framework Manager for SAP BW, 63issues with Internet Explorer 6.x security level, 16Microsoft update causes server failure, 11problems logging on to an SAP namespace, 15

segments, 41server

locales, 50server error, 20servers

failing to start, 11instability with MS SQL Server 2005, 11

set expressionschanges to SAP BW rules, 19returns incorrect data when dependent on current

measure, 27set options

Report Studio, 61sets

nested or parallel sets overlapping, 19setting

SQL Generation, 45Show hidden objects

visual aids button, 62socket reported a communication error, 17sorting

attribute based, 32SQL Generation default setting, 45SQL Server

import Japanese characters, 37SQL Server 2005, 40

date format, 34stored procedures

error in ELM Returns Agent sample, 29studios

Essbase changes, 21style properties missing in PDF reports, 60summary rows

SAP BW data sources, 25Sun ONE Directory Server

supported environments, 63supported environments, 63suppress items, 32Sybase

system objects, 41synchronizing

errors, 41system objects, 40, 41

Ttab-delimited files

Japanese characters, 37Teradata

executing a Framework Manager-based extract, 38Teradatasystem objects, 41testing

calculations, 42dimensions, 43imported functions, 42

third-party data sources8.2 DB2 OLAP, 23EssBase 7.1, 23

tildeKorean, 35

toolbar buttons, unable to launch, 18total values

SAP BW data sources, 25Transformer

70

Index

pcoptimizer setting, 17using an IQD created in Framework Manager, 44

Troubleshooting Guide, 62

Uunable to run reports, 12unbalanced hierarchies

Report Studio, 20unreadable characters, 35unsupported Cognos Planning 7.3 features, 15upgrade messages

reports, 61upgrading, 56

Cognos 8 fails to start, 11upgrading models

key figures, 44user-defined functions, 42

Vvalues

as percentage, 32version of document, 2visual aids button

Show hidden objects, 62

Wwatchlist

emails for actions, 34Web browser

errors when opening, 35Web servers

Apache and help problems, 21won character, 12

Yyen character, 12

Readme 71

Index

72

Date post:	21-Nov-2020
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

Cognos(R) 8 Business Intelligence...

Documents