Cognos® 8 Business Intelligence Readme Updatespublic.dhe.ibm.com/software/data/cognos/documentation/docs/en/c… · Non-ASCII Characters in Install Directory Will Cause Run-Time

Cognos® 8 Business Intelligence

README UPDATES

Product InformationThis document applies to Cognos® 8 Version 8.2 and may also apply to subsequent releases. To check for newer versions of this document,visit the IBM Cognos Customer Service Center (http://www.ibm.com/software/data/support/cognos_crc.html).

CopyrightCopyright © 2008 Cognos ULC (formerly Cognos Incorporated). Cognos ULC is an IBM Company.Portions of Cognos ULC software products are protected by one or more of the following U.S. Patents: 6,609,123 B1; 6,611,838 B1; 6,662,188B1; 6,728,697 B2; 6,741,982 B2; 6,763,520 B1; 6,768,995 B2; 6,782,378 B2; 6,847,973 B2; 6,907,428 B2; 6,853,375 B2; 6,986,135 B2;6,995,768 B2; 7,062,479 B2; 7,072,822 B2; 7,111,007 B2; 7,130,822 B1; 7,155,398 B2; 7,171,425 B2; 7,185,016 B1; 7,213,199 B2; 7,243,106B2; 7,257,612 B2; 7,275,211 B2; 7,281,047 B2; 7,293,008 B2; 7,296,040 B2; 7,318,058 B2; 7,325,003 B2; 7,333,995 B2.Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated) in the United States and/or other countries. IBMand the IBM logo are trademarks of International Business Machines Corporation in the United States, or other countries or both. Othercompany, product, or service names may be trademarks or service marks of others.While every attempt has been made to ensure that the information in this document is accurate and complete, some typographical errors ortechnical inaccuracies may exist. Cognos does not accept responsibility for any kind of loss resulting from the use of information containedin this document.This document shows the publication date. The information contained in this document is subject to change without notice. Any improvementsor changes to the information contained in this 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 dis-closure by the Government is subject to the restrictions in subparagraph (C)(1)(ii) of the Rights in Technical Data and Computer clause atDFARS 252.227-7013, or subparagraphs (C)(1) and (2) of the Commercial Computer Software - Restricted Rights at 48CFR52.227 as applicable.The Contractor is Cognos Corporation, 15 Wayside Road, Burlington, MA 01803.This document contains proprietary information of Cognos. All rights are reserved. No part of this document 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 priorwritten consent of Cognos.

http://www.ibm.com/software/data/support/cognos_crc.html

Table of Contents

Introduction 11

Chapter 1: Readme Updates By Date 13Updated: August 28, 2008 13

Documentation Update - Cognos 8 Go! Office 13Known Issue - Cognos 8 Go! Office 13

Updated: February 11, 2008 13Updated: November 2, 2007 13Updated: June 27, 2007 13

Documentation Update - Installation and Configuration 13Updated: June 20, 2007 13

Documentation Update - Installation and Configuration 14Known Issue - Installation and Configuration 14

Updated: May 28, 2007 14Documentation Update - Installation and Configuration 14



Updated: March 30, 2007 14Known Issues - Metric Studio 14

Updated: March 8, 2007 14Documentation Updates - Installation and Configuration 15

Updated: March 7, 2007 15Documentation Updates - Administration and Security 15

Updated: February 28, 2007 15Known Issues - Framework Manager 15Known Issues - Metric Designer 15Documentation Updates - Architecture and Deployment 15Documentation Updates - Installation and Configuration 15Documentation Updates - Administration and Security 15Documentation Updates - Report Studio 16Documentation Updates - Metric Studio 16Documentation Updates - Framework Manager 16

Chapter 2: Cognos 8 Known Issues 17Installation and Configuration 17

Cognos 8 Service Does Not Start or Fails After Starting 17Stability Problems with MS SQL Server Analysis Services 2005 in Cognos 8 17Cognos 8 Server May Fail to Start 18Unable to Load DB2 OLAP Library in Framework Manager 18Accented or Double-Byte Characters May Not Display Correctly When Installing Cognos 8

on Linux 18Non-ASCII Characters in Install Directory Will Cause Run-Time Errors 19

Readme Updates 3

Japanese Characters Corrupted When Running issetup 19Yen and Won Characters Appear as Backslashes in Charts and PDFs 19Cannot Publish Series 7 Cubes to Cognos 8 Following Upgrade 21Choosing Only One Language When Installing Cognos 8 Transformer and PowerPlay 22Issues with IBM WebSphere 6.0 on AIX 5.3 22

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

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

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

Administration 24Unable to Connect to a Cognos Planning - Contributor Data Source 24

General 25Not Yet Optimized Cognos PowerCubes May Open Slowly in Cognos 8 25Drill-Through Performance Slower 26Changes to Decimals in Currency Formats 27Currency Values in a Report Appear as Numbers 27Different Results for List Reports and Crosstabs that Use the Same Set Expression 28Relationships Not Maintained in a Report With Overlapping Set Levels 28Ragged or Unbalanced Hierarchies Result In Unexpected Behavior 29Excel Functions Used in the MDX Result in Server Error 29Web Links Do Not Work In Acrobat 7.x 29Adobe Reader Versions for Server Printing on Windows 30Problems Using Web Help with an Apache Web Server 30Metadata Change in Essbase Not Reflected in Studios 30A Filter Definition Returns Character Set Mismatch Error Against Oracle Sample Data-

base 31No Results are Returned for Footer Cells When Using Semi-Additive Measures in Dimen-

sionally Modeled Relational Data Sources 31DB2 Data Sources 31

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

SAP BW Data Sources 34Incorrect Units of Measure in Calculations 34Grouping Columns That Have the Count Summary 34Missing Measures in Crosstab Reports 34Crosstab with the Same Dimension on Both Edges Returns No Data 34Custom Formatting for Empty Cells Does Not Appear in Cognos 8 35Creating Sections on Reports That Access SAP BW Data Sources 35Summary Rows Return Incorrect Total Values 35Calculated Key Figures Appear with the Non-aggregate Icon 35Filter Expressions Using Report Items and Smart Prompts Do Not Return Values 35

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

Execute 36Query Studio 36

Cannot Use Hierarchies from Dimensionally Modeled Relational Models 36

4

Table of Contents

Text and Border Styles Are not Applied to Empty Reports 37Functions not Available 37Unable to Insert Data Items from Two Hierarchies of a Single Dimension 37Background Color in Template Does not Appear 37Subtotals in Grouped Lists 37

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

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

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

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

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

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

Metric Studio 45Scores Are Incorrect After Upgrade 45Model and Report Changes for Performance Improvement 45Error When Viewing a History Chart or Diagram on a DB2 Server with the 8.2 JDBC

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

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

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

Readme Updates 5

Table of Contents

Oracle 9.2 Package Initialization Error if NLS_LANG Environment Variable is Not SetAppropriately Before Starting Up Cognos 8 Tomcat Server 50

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

Metric Store 51Full-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 52Unable to Delete Time Periods from the Calendar 52

Metric Designer 52Missing or Incorrect Metric Values 52CCL Unknown Error Occurs When Executing an Extract From OLAP Import Sources 53Cannot Edit or Run an Extract 53Japanese Characters Do Not Display Correctly After Import into SQL Server 53Framework Manager - Import Source and Anonymous User Language Preference 53Framework Manager - Import Source Connections and Credentials 54Metric Filters are Still Invalid After Upgrading a Model and Retargeting Broken Refer-

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

Database 54IQD Import Source - Error Reading IQD file that Contains the Oracle 'Replace' Function 55Adding Multiple IQD files to an Import Source 55Data Sources Not Supported 55Filters on Parent-Child Hierarchies Are Not Supported for Dimensional (OLAP) Data

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

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

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

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

Designer 57Computer Hangs When Executing a Metrics Extract 57

Framework Manager 57Cannot Define a Segment for a Namespace That Contains the SAP Cube Name 57Errors Occur When Importing from Teradata 3.4 or 3.5 57System Objects for SQL Server 2005 Do Not Appear 58Duplicate Schemas and System Tables When Using Teradata and Sybase 58Changes Made to a Child Segment Not Reflected in the Parent 58Running the BME Script Player Can Result in Errors 58Dynamic Retargeting of Query Items Fails 58Full Outer Joins Not Sent to Oracle 9 and 10G 59Framework Manager Hangs When Using the Isolation Level for Informix Data Sources 59Error Results When Testing a User-defined Function in a Stand-alone Calculation 60

6

Table of Contents

Cannot Test the Key Figures Dimension with an Embedded Calculation 60Cannot Test a Calculation When the Active Language Is Not English 60Dimensional Functions and Members Are Not Always Supported 60Cannot Test a Dimension with an Embedded Filter That Refers to a Stand-alone Calculation

Returning a Member 61Cannot Specify the Order of Members When Defining a Level 61Dimension Appears Empty in Analysis Studio 62BEx Queries Do Not Pass Back Hierarchies in a Characteristic Structure 62Errors When Running a Report from the Find Report Dependencies Window 63Insufficient Memory to Export a Large InfoCube 63Embedded Externalize Method Does Not Function 63Default Setting for SQL Generation Has Been Changed 63

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

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

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

Session 65Cognos 8 Go! Office Does Not Start in Microsoft Word 65Server Change Affects Prompted Reports 66

Chapter 3: Cognos 8 Documentation Updates 67General 67Build Application Wizard Help 67

Select the Application to Build 67Cognos 8 Architecture and Deployment Guide 68

Cognos Products That Interoperate with Cognos 8 68Server Locale 68

Cognos 8 Installation and Configuration Guide 68Upgrading from ReportNet®, Metrics Manager, or Earlier Versions of Cognos 8 68

Enable SSL on the Web Server 69Servlet Gateway Not Supported Under Sun ONE and Sun Java Web Servers 70Uninstall Cognos Content Database 70JDBC Driver Conflict for Oracle 71Manually Create a Cognos Application File 71Cognos Products That Interoperate with Cognos 8 74Generate Keys and Certificate Signing Requests 75Upgrade .NET Security for Cognos 8 Go! Office Smart Client 78Configuring Cognos 8 Go! Office 79Add Microsoft .NET Framework Functionality to Microsoft Office Components 80Configure Cognos Components to Run Within the Application Server 81Configure the Gateway for Cognos Apache Web Server Module 83Enable or Disable Cognos 8 Go! Office Functionality for COM Add-in Users 85

Cognos 8 Administration and Security Guide 86

Readme Updates 7

Table of Contents

Setting Up Logging 86Change the Suppression Functionality in Analysis Studio 86Deploying Cognos 8 Go! Office Client 87Access Permissions 87Set Query Prioritization 88Model-based vs. Report-based Drill-through Access 89Members and Values 90Business Keys 90Scope 91Set Up Drill-through Access in a Package 91

Cognos 8 Analysis Studio User Guide 91Suppressing Empty Cells 91

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

Set Governors 93Upgrading the Model 93Converting Query Subjects with Dimension Information to Regular Dimensions 93Determinants 94Defining Determinants 95Work with SAP BW Data in Cognos 8 Planning 96

Cognos 8 Getting Started 96Cognos 8 Go! Office User Guide 96

Change Prompt Values 96Cognos 8 Metric Studio User Guide 98

Create a Metric Type 98Choose the Period to Monitor 102Equations (.equ) 103Equation Items (.eqi) 103

Cognos 8 Query Studio User Guide 104Cognos 8 Report Studio User Guide 104

Grouping by an Attribute is Not Supported 104ReportOption 104Applying Filters to Dimensional Reports 104Setting Object Properties 105Creating Burst Reports Using a Dimensional Data Source 106Connecting Queries Between Different Data Sources 106Remove Upgrade Messages 106Set Options 106Report Studio Properties 107Visual Aids Button 107Set Up Drill-through Access in a Report 107

Cognos 8 Troubleshooting Guide 108Data Manager Installation and Configuration Guide 108

Install the SAP Gateway Functions 108Cognos 8 SDK Developer Guide 108

Report Specification Reference 108

8

Table of Contents

Chapter 4: Deprecation Notices 111Supported Environments 111Framework Manager Security Filters for SAP BW: Notice of Intent to Change the Default Set-

ting 111

Index 113

Readme Updates 9

Table of Contents

10

Table of Contents

Introduction

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

known issues.

Visit the Cognos Global Customer Services Web site for

● updates to this Readme and product documentation

● the fix list, which is a list of the known issues that were addressed in this release

Updates to the software are made available on the Cognos Global Customer Services Web site (http:

//support.cognos.com). These updates contain the latest set of quality improvements that were

completed after the release of this software. We recommend that you review these updates and

apply them once you have completed the installation.

Readme Updates 11

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


12

Introduction

Chapter 1: Readme Updates By Date

This section contains cross references to known issues and documentation updates that were dis-

covered after the last release.

Updated: August 28, 2008The following documentation update and known issue were added on August 28, 2008.

Documentation Update - Cognos 8 Go! Office● "Cognos 8 Go! Office User Guide" (p. 96)

Known Issue - Cognos 8 Go! Office● "Server Change Affects Prompted Reports" (p. 66)

Updated: February 11, 2008The following documentation update was added on February 11, 2008.

● "Grouping by an Attribute is Not Supported" (p. 104)

Updated: November 2, 2007The bug number was changed from 548382 to 567492 for the following known issue on November

2, 2007.

● "Relationships Not Maintained in a Report With Overlapping Set Levels" (p. 28)

Updated: June 27, 2007The following documentation update was added on June 27, 2007.

Documentation Update - Installation and Configuration● "Upgrading from ReportNet®, Metrics Manager, or Earlier Versions of Cognos 8" (p. 68)

Updated: June 20, 2007The following documentation update and known issue were added on June 20, 2007.

Readme Updates 13

Documentation Update - Installation and Configuration● "Enable SSL on the Web Server" (p. 69)

Known Issue - Installation and Configuration● "Cognos 8 Service Does Not Start or Fails After Starting" (p. 17)

Updated: May 28, 2007The following documentation update was modified on May 28, 2007.

Documentation Update - Installation and Configuration● "Servlet Gateway Not Supported Under Sun ONE and Sun Java Web Servers" (p. 70)

Updated: May 25, 2007The following documentation update was modified on May 25, 2007.

Documentation Update - Installation and Configuration● "Cognos Products That Interoperate with Cognos 8" (p. 74)

Updated: May 3, 2007The following documentation update was added on May 3, 2007.

Documentation Update - Installation and Configuration● "Uninstall Cognos Content Database" (p. 70)

Updated: March 30, 2007The following known issues were added on March 30, 2007.

Known Issues - Metric Studio● "Scores Are Incorrect After Upgrade" (p. 45)

● "Model and Report Changes for Performance Improvement" (p. 45)

Updated: March 8, 2007The following documentation updates were added on March 8, 2007.

14


Documentation Updates - Installation and Configuration● "JDBC Driver Conflict for Oracle" (p. 71)

● "Manually Create a Cognos Application File" (p. 71)

Updated: March 7, 2007The following known issue was added on March 7, 2007.

Documentation Updates - Administration and Security● "Change the Suppression Functionality in Analysis Studio" (p. 86)

Updated: February 28, 2007The following known issues and documentation updates were added on February 28, 2007.

Known Issues - Framework Manager● "Cannot Define a Segment for a Namespace That Contains the SAP Cube Name" (p. 57)

● "Errors Occur When Importing from Teradata 3.4 or 3.5" (p. 57)

Known Issues - Metric Designer● "Missing or Incorrect Metric Values" (p. 52)

● "CCL Unknown Error Occurs When Executing an Extract From OLAP Import Sources" (p. 53)

Documentation Updates - Architecture and Deployment● "Cognos Products That Interoperate with Cognos 8" (p. 68)

Documentation Updates - Installation and Configuration● "Cognos Products That Interoperate with Cognos 8" (p. 74)

● "Generate Keys and Certificate Signing Requests" (p. 75)

● "Upgrade .NET Security for Cognos 8 Go! Office Smart Client" (p. 78)

● "Configuring Cognos 8 Go! Office" (p. 79)

● "Add Microsoft .NET Framework Functionality to Microsoft Office Components" (p. 80)

● "Configure the Gateway for Cognos Apache Web Server Module" (p. 83)

Documentation Updates - Administration and Security● "Setting Up Logging" (p. 86)

Readme Updates 15


● "Change the Suppression Functionality in Analysis Studio" (p. 86)

● "Deploying Cognos 8 Go! Office Client" (p. 87)

Documentation Updates - Report Studio● "Report Studio Properties" (p. 107)

Documentation Updates - Metric Studio● "Create a Metric Type" (p. 98)

● "Choose the Period to Monitor" (p. 102)

Documentation Updates - Framework Manager● "Set Governors" (p. 93)

16


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

Cognos 8 Service Does Not Start or Fails After StartingYou start the Cognos 8 service but services either do not start correctly or are very slow to start.

After services start, the system fails a short time afterwards. While services are starting, Java uses

100 percent of the CPU time. You may also receive multiple occurrences of error messages such as

the following:

● DPR-DPR-1035 Dispatcher detected an error.

● CAM-CRP-1157 Unable to synchronize the local common symmetric key store with Content

Manager.

If you use a DB2 database for the content store, ensure that the database version and Java version

are compatible. For DB2 version 8.2, Java 1.5 is not supported.

To review an up-to-date list of environments supported by Cognos products, such as operating

systems, patches, browsers, Web servers, directory servers, database servers, and application servers,

visit the Cognos Global Customer Services Web site (http://support.cognos.com).546816

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

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

Readme Updates 17


● 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

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.

Steps

1. 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 InstallingCognos 8 on Linux

If you are using issetup under a UTF-8 locale, accented or double-byte characters may not display

correctly.

18


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:

Steps

1. When you install Cognos 8 on a UNIX computer, open the console display.

2. Type LANG=C and LC_ALL=C to specify English only for the installation.

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.

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.

Readme Updates 19


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 GlobalRe-

portStyles.css file.

Steps the Install the Fonts for Yen and Won Characters

1. 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 Configur-

ation 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 Sheet

1. 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;

}

20


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.

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 Directories

1. 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 Path

1. Start Cognos Configuration.

2. Click Actions, Edit Global Configuration, and click the Server tab.

3. In the Path box under Cookie Setting, type

/

4. Click OK.

5. Save your configuration.

Readme Updates 21


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 andPowerPlay

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.

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 extension

nbna

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

22


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 function-

ality that automatically converts all password characters to uppercase. To ensure that all previously

created passwords can still provide successful logon to Cognos Connection, set the value of the

bapiPasswordConv parameter to true.

Steps to Change the Setting of the bapiPasswordConv Parameter

1. Open the file bapiint_config.xml.

This file is located in the c8_location\bin directory.

2. Change the value of the bapiPasswordConv parameter to true, as shown in the following

fragment of code:

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

4. Restart the Cognos 8 service.

For more information, see the following SAP Notes:

● 792850 - Preparing ABAP systems to deal with incompatible passwords

● 862989 - New password rules as of Web AS ABAP 7.0/NetWeaver 2004

nbna

Users Are Repeatedly Prompted for Credentials When Trying to Log On to anSAP 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 para-

meter for the SAP authentication provider to use a non-Unicode code page, such as SAP CP 1100.nbna

Readme Updates 23


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 admin-

istration secured feature and traverse permission for the Administration secured function. For more

information, see "Securing Functions and Features" in the Administration and Security Guide.

Steps

1. In Cognos Connection, click Tools, Server Administration.

2. Click the Configure tab.

3. In the Name column, click the dispatcher you want.

4. For ReportService, in the Actions column, click the set properties button.

5. Click the Settings tab.

6. For the Environment category, next to Advanced settings, click the Edit link.

7. If it appears, select the Override the settings acquired from the parent entry check box. Other-

wise, 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.

Unable to Connect to a Cognos Planning - Contributor Data SourceAttempting to connect to a Cognos Planning - Contributor Data Source may result in a failed con-

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

24


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 component 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 8

1. Back up your target PowerCube, then navigate to the Cognos_8_installation_location/bin

directory.

2. On Windows, open a command line window and run PCOptimizer.exe.

3. On UNIX, enter the following line to run the optimization command line utility:

pcoptimizer [-t] [-v] [-h] <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:

Readme Updates 25


● -t or test mode; it tests whether the metadata was extracted and loaded into the PowerCube.

The return code indicates the status.

● 0 if the metadata was extracted and loaded

● 10 if the metadata was not loaded

● 20 if an error occurred while accessing the PowerCube

● -v or verbose mode; text is output to standard output (stdout), indicating what was done,

including 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 Sub-sequent Releases

1. 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 SlowerDrill-through performance in Cognos 8 may be slower than in ReportNet for the same reports.493659

26


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 places

In all other calculations of this type, the number of decimals in the resulting value will be

determined by the number of decimals in the currency value. The following examples illustrate

this new behavior:

● $4.00 / $2.00 = $2.00

● $4 / $3.0000 = $1.3333

● $4 / $3 = $1.333

● $4.0 / $3.00 = $1.333

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

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

Readme Updates 27


Different Results for List Reports and Crosstabs that Use the Same Set ExpressionIn 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:

● X and Y together as ungrouped report details

● Y nested under X

● Y appended as an attribute of a group based on X

When using named sets, or sets that cover more than one level of a hierarchy, do not use sets from

the same dimension in more than one place in the same report. They should appear on only one

level of one edge.567492

28


Ragged or Unbalanced Hierarchies Result In Unexpected BehaviorIn 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 sup-

ported 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 ErrorYou 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.

Readme Updates 29


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:support.

[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

30


A Filter Definition Returns Character Set Mismatch Error Against Oracle SampleDatabase

A filter definition may return a character set mismatch error when run against the Oracle version

of a sample database.

The following Oracle error appears:

ORA-12704: character set mismatch

To fix this error, the modeler must fix the filter definition in Framework Manager. In Framework

Manager, cast the item you want to filter as nvarchar, and then republish the package to Cognos

Connection.

No Results are Returned for Footer Cells When Using Semi-Additive Measuresin 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.

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.

Steps

1. 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 man-

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

Readme Updates 31


The error probably occurred because Windows did not have enough remote procedure call (RPC)

ports available. This lack of sufficient RPC ports can cause data retrieval from DB2 OLAP and

Essbase data sources to fail because of network communication errors.

To resolve this problem, you must increase the number of RPC ports that are available for program

use. Hyperion and Microsoft propose that you add two registry entries, MaxUserPort TCP/IP and

TcpTimedWaitDelay in Microsoft Registry Editor.

For more information about these parameters, see http://www.microsoft.com/resources/

documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/

Windows/2000/server/reskit/en-us/regentry/58811.asp.

Important: Use Registry Editor at your own risk. Incorrect use may cause problems that require

you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems

that result from using Registry Editor incorrectly.

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

Steps to Add Entries in Microsoft Registry Editor

1. From the Start menu, click Run.

2. Type regedit and then click OK.

3. In the Registry Editor window, click the following directory:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

4. From the Edit menu, click New, DWORD Value.

The new value appears in the list of parameters.

5. Type MaxUserPort and then press Enter.

Double-click MaxUserPort.

6. In the Edit DWORD Value window, do the following:

● Click Decimal.

● Type a value between 30000 and 65534.

Tip: We recommend the maximum value, 65534.

● Click OK.

7. From the Edit menu, click New, DWORD Value.

The new value appears in the list of parameters.

8. Type TcpTimedWaitDelay and then press Enter.

9. Double-click TcpTimedWaitDelay.

10. In the Edit DWORD Value window, do the following:

● Click Decimal.

● Type a value between 30 and 300 seconds.

32


The default is 240 seconds (4 minutes).

● Click OK.

11. Close the Registry Editor window.

12. Restart the Microsoft CRM server or reboot your computer for these settings to take effect.

Steps to Edit the Cognos qfs_config.xml Configuration File

1. Open the qfs_config.xml configuration file from the configuration directory.

2. Add the following parameters under the appropriate provider section, such as <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 fol-

lowing additional steps when installing your DB2 OLAP 8.2 client software.

Steps to Access the Run-time Library

1. In the DB2 OLAP 8.2 client installation wizard, select the Custom installation type, and then

click Next.

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

proceed through the remaining pages of the installation wizard.

3. When the installation is finished, locate libdb42.dll in the folder db2olap_installation_loca-

tion\api\redist, and copy this file to the client installation folder db2olap_installation_loca-

tion\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

Readme Updates 33


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.

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 aggrega-

tions), 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 Suppressed

1. In the report layout, right-click the crosstab and click Go to Query.

2. In the Properties pane, click the Suppress property and click None.

3. Save the report.

545657, 545661

34


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.

Lowest-level Query Item in a Ragged Hierarchy

The solution is to remove the section from the lowest-level query item.443696

Several Multicubes with SAP Variables

The 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 IconCalculated 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 ValuesIf 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:

Readme Updates 35


● Fully qualify the item by using items from the metadata tree instead of the report item tree

● Build smart prompts in the report instead of hand coded prompts

495958496340

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 NotExecute

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.

Note: When you create the new special categories, you can accept the default property values.

To view an example of a Transformer model with the relative time categories in a new special cat-

egory, go to the Cognos Global Customer Services Web site, and in the Documentation/Utilities

section, search on Product: Cognos 8 Business Intelligence 8.2/Type of Document: Utilities to

download the Great Outdoors Company sample model.

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

36


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, theCalculatemenu does not show the following

functions:

● Rank

● % of total

● Percentile

● Quartile

481930

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

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.

Readme Updates 37


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 DataIf 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

38


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 Values

1. Access the query in Query Explorer.

2. In the Properties pane, set the Override Dimension Info property to Yes.

3. Click the Dimension Info tab.

4. For each level of the original dimension, create a separate dimension with a single hierarchy

and single level.

5. Include all necessary facts.

6. Lay out the query items in the report as per the original layout.

When you run the report, the aggregate values appear as expected.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 Trans-

formation validation level, you will get back all errors and warnings, but you may get little or no

Readme Updates 39


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 AttributeYou have a list style report or query and you have grouped by an attribute of a dimension.

Grouping by attributes is not supported in this release. Thus, when you turn a report that is grouped

by attributes into a crosstab, you see the member to which the attribute belongs. This can affect

summaries, particularly in cases where attribute values are repeated across members.

For example, the report contains a dimension with this structure: Product=level, Product Id=Id,

Product Name=caption, Color=attribute. Grouping on the attribute Color will give a different result

than grouping on Product Name/Product Id.

We recommend that report authors avoid creating crosstab reports with grouped attributes for the

current release.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:nof: "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.

40


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.

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 inAnalysis 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/

Readme Updates 41


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 Transformer

1. In Transformer, from the File menu, click Currency Table, and click OK.

2. Right-click each currency measure, and click Allow currency conversion.

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>

42




<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 ExcelWhen 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 lan-

guages that represent the data contained in the cube. If you add a language to the model after the

cube is published, users with locales that match the added language locale may find that Analysis

Studio does not recognize references to the member unique names. There is no impact on users

whose locale matches the original language list.499296

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

values as a percentage.494291

Readme Updates 43


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 ConnectionYou 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 ProduceUnexpected 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 UsingMicrosoft 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.

44


501235

Metric StudioThis section contains known issues about Metric Studio.

Scores Are Incorrect After UpgradeAfter upgrading to Metric Studio 8.2, metric types with the performance pattern set to On Target

is Positive may have incorrect scores. This occurs because of a change in how scores are calculated.

To correct the scores, follow these steps.

Steps

1. Run a stored procedure.

● For Oracle, run the following command from SQL*Plus

BEGIN

loader_util.add_event ('MARK_FOR_RECALC');

END;

● For SQL Server, run the following command from Query Analyzer

exec lsp_add_event 'MARK_FOR_RECALC'

● For DB2, run the following command from Control Centre

call lsp_add_event('MARK_FOR_RECALC')

2. Run the Metric Maintenance job, Recalculate metric store derived values.

555500

548923

Model and Report Changes for Performance ImprovementTo improve report performance and address disk space consumption problems when loading the

metric store, changes were made to hot site 8.2.43.56 that affect the metric store schema, the

Framework Manager model that is created for metric packages, and the reports that are supplied

with Metric Studio.

Metric Store Schema Changes

To improve query performance, a new set of database views was created. These views are used by

the Import View in the Framework Manager model created with each metric package. The names

of these views begin with MODEL_ . For customers who upgrade, the new views are created during

the upgrade process. For new customers, these views are created within the metric store during

metric package creation.

Existing views remain the same but will not be used by the new model. The names of existing views

began with VW_MODEL.

Readme Updates 45


Framework Manager Model Changes

The model contains the two namespaces, Content and Staging. Changes were made only to the

Content namespace. The Staging namespace is unchanged.

The Content namespace contains the following new query subjects:

● All Time Periods

This query subject contains all the time periods existing in the metric store calendar. It has a

one-to-many relationship with the Metric History query subject: All Time Periods (1.1) <- ->

Metric History(0.n).

When a report must show time periods including those for which there is no history data, the

time-related query items should be selected from All Time Periods.

● Scorecard Group

This query subject is under the Scorecards folder. It contains scorecard group information that

you use when working with Group and Group Type information related to Scorecard Group

History and Scorecards.

● Action Comment

This query subject is under the Metrics folder and contains comment information related to

actions.

● Project Comment

This query subject is under the Project folder and contains comment information related to

projects.

● Task Comment

This query subject is under the Project folder and contains comment information related to

tasks.

● Action Critical Success Factor

This query subject is under the Metrics folder and contains critical success factor information

related to actions. This information was found previously under the query subject, Actions.

● Project Critical Success Factor

This query subject is under the Project folder and contains critical success factor information

related to projects. This information was found previously under the query subject, Project.

● Task Critical Success Factor

This query subject is under the Project folder and contains critical success factors related to

tasks. This information was found previously under the query subject, Tasks.

Other changes to the Content namespace include the following

● The relationship between the Metric Type and Metric is set to Metric Type (1.1) <- -> Metric'

(1.n), as a workaround for an Oracle bug (ORA-600).

46


This means that a simple query will not return metric types for which there are no metrics.

However, this link can be overwritten by creating a link in the report. Use Report Studio to

create the 1.1 <- > 0.n join between Metric Type and Metric.

● The query item, Metric SID, is added to the Scorecard query subject. This query item is the SID

of the metrics that are linked to the scorecard. This query subject returns all of the scorecards,

regardless of whether they have metrics linked to them.

As a workaround for an Oracle bug (ORA-600), the relationship between the Scorecard and

Metric is set to Scorecard (1.1) <- -> Metric (1.1).

Report Changes

To take advantage of the model changes and to return the accurate results, some changes were

made to the reports supplied with Metric Studio.

● Where appropriate, report fields, filters and prompts are updated to use time-related items from

the All Time Periods query subject instead of using the time items from the Metric History

query subject.

For example, in the Metric History report, time periods are now taken from All Time Periods

but metric SIDs are taken from the Metric History query subject. The updated time filters are

[Content].[All Time Periods].[Period Level Code] = ?Level?

[Content].[All Time Periods].[Period Start Date] >= ?Start Date?

[Content].[All Time Periods].[Period Start Date] <= ?End Date?

● Because the Metric History query subject now contains only the time periods with history data,

the existing reports using this model query subject will show only the time periods for which

there is history data. The reports included with Metric Studio are updated to display the time

periods that have no history data. For example, to allow blank rows, you can do one of the

following:

● change the filters on the Metric SID field to allow null SID-s, such as using the SID to match

the filter defined for metric history

[Content].[Metric History].[METRIC SID] = ?metric?

or

[Content].[Metric History].[METRIC SID] is null

● set the filter above to optional to allow all metrics

● create a left outer join on time period SID between All Time Periods and Metric History

● Conditional formatting changes were required for fields that have no data, such as the Metric

Status URL field.

Testing the Changes

After upgrading to the hot site, we recommend that you test all reports that use the updated metric

packages. To do this:

Readme Updates 47


● create a new metrics package that references your existing metric store data source and execute

all packaged reports.

● update your exiting Metric Studio 8.2 metric package and execute all pre-existing reports.

545084

541408

Error When Viewing a History Chart or Diagram on a DB2 Server with the 8.2JDBC 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 Exportand 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 Exportand 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

48


GRANT EXECUTE ON UTL_FILE TO CMM_USER524622

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

sequently 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 calcu-

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

Readme Updates 49


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

Oracle 9.2 Package Initialization Error if NLS_LANG Environment Variable isNot 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

50


Right-clicking to Follow a Link in a New Web Browser Window Is Not SupportedA 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 Window

1. 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 DB2After 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.499392

Korean Full-width Tilde Changes to Half-width Tilde After Being Imported intoa 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 Table

1. 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 the conversion table for codepage 970.

3. Replace the default conversion table with the alternative conversion table by following the

instruction from IBM499392

Readme Updates 51


Full-width Tilde and Full-width Hyphen Characters Change to the "?" CharacterAfter 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 Table

1. 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 inad-

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

Missing or Incorrect Metric ValuesIf a time period filter is specified in a metrics extract based on an OLAP (Powercube) import source

which cannot compute the dynamic rollup because the parent values are not computed from their

children, then metric values are incorrect or missing for "higher" time levels.

The workaround is to specify Total as the value for the Aggregate Function and Rollup Aggregate

Function attributes in the metrics mapping page of the metrics extract.538372

52


CCL Unknown Error Occurs When Executing an Extract From OLAP ImportSources

A CCL Unknown Error occurs when you execute an extract from OLAP (Powercube) import sources

that contain scorecard levels whose mapped attributes are all text mappings.

The workaround is to create the scorecards directly in the Metric Studio application, or by using

an objects extract. You must specify the metric package as the import source.

Then, rather than defining a scorecard level in the metrics extract's scorecards mapping, specify the

scorecard as the root scorecard.537509

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

Steps

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

operating system before running the metric maintenance task

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

Readme Updates 53


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 BrokenReferences

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

Problem Executing an Extract Created From a Framework Manager Model Usinga 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:

Steps

1. "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

54


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.

Metric Designer does not recognize joins where more than one column is required for a join condi-

tion. 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.497977

Readme Updates 55


Error Occurs for a Metrics Extract Containing Static Text-type Scorecard LevelsMetrics 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 NotDeliver 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 forPowerCube Import Sources

Construct functions including "IF THEN ELSE" and "CASE" are not supported in expressions for

scorecard identifiers for PowerCube import sources.508879

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

56


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

Cannot Define a Segment for a Namespace That Contains the SAP Cube NameWhen importing from an SAP cube, two namespaces are generated by default: one contains the

data source name and the other contains the cube name. If you define a segment for the namespace

that contains the cube name, Framework Manager will close without prompting you to save your

changes.

When you import an SAP cube, manually define a new namespace. Then move necessary objects

into the new namespace and define a segment for the new namespace or folder.548830

Errors Occur When Importing from Teradata 3.4 or 3.5If you are importing from a Teradata 3.4 or 3.5 data source, errors occur if the table name contains

an underscore and the Teradata database is in Unicode.

Select the Ignore Search Patterns option when defining the ODBC connection.526682

Readme Updates 57


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

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

58


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.

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 DataSources

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 committed

515913

Readme Updates 59


Error Results When Testing a User-defined Function in a Stand-alone CalculationTesting 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 calcu-

lation in the expression editor if the expression has a decimal.

The solution is to test the calculation in the studios or the project viewer.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

60


● 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-aloneCalculation 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

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

Readme Updates 61


● 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 StructureWhen 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.

62


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 InfoCubeA 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 function-

ality 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-inWorkbook 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.

Readme Updates 63


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

The Cognos Action Pane Disappears When Using the Smart Client and You Runa 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-2607During 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.

64


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.

Steps

1. From the Manage Data tab, click the report to display the report properties.

2. Expand the prompt properties.

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

Steps

1. 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,

Readme Updates 65


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

Server Change Affects Prompted ReportsIf you change the server from which you are reading reports, prompted reports are returned to the

default option, Specified Value, and you must manually reset the report to Always Prompt or Cell

Value, even if the package and report names are identical.597003

66


Chapter 3: 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 MigrationUser 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.

Steps

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

Readme Updates 67

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

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.

Cognos Products That Interoperate with Cognos 8The following subsection replaces the subsection of the same name.

Transformer

You can use Cognos PowerCubes and Transformer models that were generated by Transformer

7.3 or later directly in Cognos 8. The cubes and models are upwards compatible and require no

migration or upgrade tools. You can run reports and analyses in Cognos 8 against the Cognos

PowerCubes. We recommend that you optimize the cubes for use in Cognos 8 by using the

pcoptimizer utility.

For more information about optimizing PowerCubes, see the Troubleshooting Guide. You can use

Transformer models directly in Framework Manager.

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.

Upgrading from ReportNet®, Metrics Manager, or Earlier Versions of Cognos 8In the following section, the bulleted item is in addition to the items already documented.

68


Report Studio

The upgrade does not account for the following:

● changes in chart behavior from ReportNet to Cognos 8

In ReportNet, if a chart is created with a user-specified minimum value and all data values are

below the minimum value, the chart starts at the user-specified minimum value and contains

no data.

In Cognos 8, the same parameters result in a chart that ignores the user-specified minimum

value and uses a range that includes all of the data values for the chart.

558836

Enable SSL on the Web ServerThe following steps replace the steps in the topic of the same name.

Steps

1. Configure the Web server for SSL and start the Web server.

For more information, see your Web server documentation

2. On each Application Tier Components computer that points to the gateway on the Web server,

in Cognos Configuration, change the gateway URI from HTTP to HTTPS, and save the config-

uration.

Important: Do not start the Cognos 8 service yet.

3. On each Application Tier Components computer, go to the c8_location/bin directory and import

all of the certificates that make up the chain of trust, in order starting with the root CA

certificate, into the Cognos trust store.

Import the certificates by typing the following command:

On UNIX or LINUX, type

ThirdPartyCertificateTool.sh -T -i -r certificate_fileName -D ../configuration/signkeypair -ppassword

On Windows, type

ThirdPartyCertificateTool.bat -T -i -r certificate_fileName -D ../configuration/signkeypair -ppassword

Note: The password should have already been set. If not, the default password is NoPassWord-

Set.

4. On each Application Tier Components computer, in Cognos Configuration, start the Cognos

8 service.

554654

Readme Updates 69


Servlet Gateway Not Supported Under Sun ONE and Sun Java Web ServersThe servlet gateway is not supported under Sun ONE and Sun Java Web servers. The servlet gateway

is supported only under one of the following application servers:

● BEA WebLogic Server

● IBM WebSphere Application Server

● Oracle Application Server

● Red Hat JBoss

● SAP Web Application Server

For more information about supported third-party products, visit the Cognos Global Customer

Services Web site (http://support.cognos.com).505016

Uninstall Cognos Content DatabaseIf you want to uninstall only Cognos Content Database and leave other Cognos 8 components on

your computer, you must use the following procedure. After you uninstall Cognos Content Database

you must configure a new content store before you can restart the Cognos 8 service.

If you installed only Cognos Content Database, use the manual procedures for uninstalling Cognos 8

on UNIX or Linus or Window. For more information, see the Installation and Configuration Guide.

Steps

1. On the computer where you installed Cognos Content Database, go to the c8_location\bin

directory, and type the following command:

● On Windows, type

derby.bat uninstall

This command removes the Cognos Content Database service.

● On UNIX, type

derby.sh stop

This command stops the Cognos Content Database service.

2. In the c8_location directory, delete the derby10.1.2.1 directory.

3. In the c8_location\bin directory, delete the following files:

● On Windows, derby.bat

● On UNIX, derby.sh and derbyenv.sh

4. On Windows, in the c8_location\logs directory, delete the derby.service file.

5. In the c8_location directory, open the cmplst.txt file in a text editor.

70



6. Remove lines containing Cognos Content Database values. The lines contain CCD and

CMDERBY. For example:

C8BISRVRCCD_version=

C8BISRVRCCD_name=

CCD_version=

CCD_name=

CMDERBY_version=

CMDERBY_name=

Tip: You can also comment the lines out by inserting # at the start of each line.

7. Save the file.

8. Start Cognos Configuration and under Data Access, Content Manager, do the following:

● Delete the Cognos Content database.

● Configure a new database resource to point to a new content store.

For more information, see the Installation and Configuration Guide.

9. Restart Cognos 8.

553987

JDBC Driver Conflict for OracleIf you use Oracle for data source, import source, logging database, or the content store database,

you must ensure that there is no conflict with the JDBC driver file. In earlier releases of Cognos 8,

Oracle databases required a classes12.jar file. In Cognos 8 Version 8.2, Oracle databases require

an ojdbc14.jar file.

To ensure that there is no conflict, check the c8_location\webapps\p2pd\WEB-INF\lib directory on

each computer where Content Manager, the Application Tier, Framework Manager, or Metric

Studio is installed. If both the classes12.jar file and the ojdbc14.jar file are present, you must delete

the obsolete classes12.jar file.547145

Manually Create a Cognos Application FileCognos 8 and the servlet gateway must be packaged into an application file for deployment to

supported third-party application servers. Cognos 8 provides a Build Application wizard that you

can use to create the application file.

You can create a Web archive (.war) file, an Enterprise archive (.ear) file, or an expanded directory

that includes all the files necessary for the application. For information about WAR and EAR files

or expanded directories and to determine what is supported by your application server, see the

documentation provided with the application server.

If you choose not to use the Build Application wizard, you must complete the following steps to

create the application file.

Readme Updates 71


If the application server is not being used as a web server, you do not need to include the Cognos

static content (html pages, images, and so on) in the application file. Excluding the static content

when creating the application file reduces the size of the file.

Steps to Create a Cognos 8 Application File

1. Go to the c8_location/war/p2pd directory.

2. Run the build script by using the following command syntax:

● For Windows,

build.bat file_type option

● For Unix or Linux,

build.sh file_type option

where file_type can be one of the following:

● war

WAR file with static content

● war_without_webcontent

WAR file with no static content

● war_without_docsamples

WAR file with static content and with no documentation and sample files

● ear

EAR file with static content

● ear_without_webcontent

EAR file with no static content

● ear_without_docsamples

EAR file with static content and with no documentation and sample files

● expand

directory containing the application with static content

● expand_without_webcontent

directory containing the application with no static content

● expand_without_docsamples

directory containing the application with static content and with no documentation and

sample files

and where option can be one or more of the following:

● -Dappserver_type=value

72


with a value of jboss (perform actions for a JBoss application server) or other (default,

perform actions for a non-JBoss application server)

● -Dcontext_root=value

with a value of p2pd (default, preset a context root value for the application)

● -Dwar_name=path/filename

with a default of ../../p2pd.war (path and name of the WAR file to be created)

● -Dear_name=path/filename

with a default of ../../p2pd.ear (path and name of the EAR file to be created)

● -Dexpand_location=path/directory

with a default of ../../temp/expand (path to directory where the application files are to be

expanded)

Steps to Create a Servlet Gateway Application File

1. Go to the c8_location/war/gateway directory.

2. Run the build script by using the following command syntax:

● For Windows,

build.bat file_type option

● For Unix or Linux,

build.sh file_type option

where file_type can be one of the following:

● gateway_war

WAR file with static content

● gateway_war_without_docsamples

WAR file with static content and with no documentation and sample files

● gateway_ear

EAR file with static content

● gateway_ear_without_docsamples

EAR file with static content and with no documentation and sample files

● gateway_expand

directory containing the application with static content

● gateway_expand_without_docsamples

directory containing the application with static content and with no documentation and

sample files

Readme Updates 73


and where option can be one or more of the following:

● -Dappserver_type=value

with a value of jboss (perform actions for a JBoss application server) or other (default,

perform actions for a non-JBoss application server)

● -Dcontext_root=value

with a value of ServletGateway (default, preset a context root value for the application)

● -Dwar_name=path/filename

with a default of ../../ServletGateway.war (path and name of the WAR file to be created)

● -Dear_name=path/filename

with a default of ../../ServletGateway.ear (path and name of the EAR file to be created)

● -Dexpand_location=path/directory

with a default of ../../temp/expand (path to directory where the application files are to be

expanded)

Cognos Products That Interoperate with Cognos 8The following subsection replaces the subsection of the same name.

Some Cognos products provide functionality that is not available in Cognos 8. You can continue

to use these products in the same environment as Cognos 8 and access the different types of cubes

in the Cognos 8 portal.

You can install different Cognos 8 products in separate locations within the same environment and

then configure the products to share some resources. When you do so, both products must be at

the same version.

Cognos 8 Controller

You can access Cognos 8 to create Cognos Controller Standard Reports by using a predefined

Framework Manager package of standard reports that is created when Cognos Controller is installed.

You can also access published Controller data and structures in Framework Manager for custom

reporting and analysis.

If you install Cognos 8 Controller in the same environment as Cognos 8 and configure it to share

resources with Cognos 8, both products must be the same version.

Transformer

You can use Cognos PowerCubes and Transformer models that were generated by Transformer

7.3 or later directly in Cognos 8. The cubes and models are upwards compatible and require no

migration or upgrade tools. You can run reports and analyses in Cognos 8 against the Cognos

PowerCubes. We recommend that you optimize the cubes for use in Cognos 8 by using the

pcoptimizer utility.

For more information about optimizing PowerCubes, see the Troubleshooting Guide. You can use

Transformer models directly in Framework Manager.

74


Generate Keys and Certificate Signing RequestsUse the command line utility to generate all the keys for the Cognos key stores and to generate the

certificate signing requests (CSR).

The following list shows the options for the command-line tool used to generate keys and signing

requests:

● Main operation mode

● -c

Create a new CSR

● -i

Import a certificate

● Operation modifiers

● -s

Work with the signing identity

● -e

Work with the encryption identity

● -T

Work with the trust store (only with -i)

● Information flags

● -d

DN to use for certificate

● -r

CSR or certificate file location (depends on mode)

● -t

certificate authority certificate file (only with -i)

● -p

Key Store password (must be provided)

● -a

Key pair algorithm. RSA or DSA.

Default: RSA

● -D

Directory location

The following sample values are used:

● For Signing certificate DN,

Readme Updates 75


CN=SignCert,O=MyCompany,C=CA

● For Encryption certificate DN,

CN=EncryptCert,O=MyCompany,C=CA

● For Keystore password,

password

Steps

1. In the c8_location\configuration directory, back up the cogstartup.xml file to a secure location.

2. Back up the contents of the following directories to a secure location:

● c8_location\configuration\signkeypair

● c8_location\configuration\encryptkeypair

3. Using Cognos Configuration, export the configuration in clear text by doing the following:

● Open Cognos Configuration.

● From the File menu, click Export As.

● When prompted about exporting decrypted content, click Yes.

● In the Export As dialog box, select cogstartup.xml and then click Save.

● When prompted about replacing the existing file, click Yes.

● When the tasks are complete, close the Cognos Configuration dialog box.

● Save the configuration.

● Close Cognos Configuration.

4. Go to the c8_location\bin directory.

5. Create the certificate signing request for the signing keys by typing the following command:

On UNIX or Linux, type

ThirdPartyCertificateTool.sh -c -s -d "CN=SignCert,O=MyCompany,C=CA" -r signRequest.csr

-D ../configuration/signkeypair -p password

On Windows, type

ThirdPartyCertificateTool.bat c -s -d "CN=SignCert,O=MyCompany,C=CA" -r signRequest.csr

-D ../configuration/signkeypair -p password

Tip: UNIX or Linux filenames are case-sensitive and must be entered exactly as shown.

You can safely ignore any warnings about logging.

The command creates the jSignKeystore file in the signkeypair directory, sets the specified

password, creates a new keypair and stores it in the keystore, and exports the signRequest.csr

file to the c8_location\bin directory.

76


6. Create the certificate signing request for the encryption keys by typing the following command:


ThirdPartyCertificateTool.sh -c -e -d "CN=EncryptCert,O=MyCompany,C=CA" -r

encryptRequest.csr -D ../configuration/encryptkeypair -p password

On Windows, type

ThirdPartyCertificateTool.bat -c -e -d "CN=EncryptCert,O=MyCompany,C=CA" -r

encryptRequest.csr -D ../configuration/encryptkeypair -p password


The command creates the jEncKeystore file in the encryptkeypair directory, sets the specified

password, creates a new keypair and stores it in the keystore, and exports the encryptRequest.csr

file to the c8_location\bin directory.

7. Copy the signRequest.csr and encryptRequest.csr files that were generated in steps 6 and 7 to

a directory that is accessible by your third-party certificate authority.

8. Input the signRequest.csr and encryptRequest.csr files into the third party certificate authority.

For more information, see your third-party CA documentation.

The certificate authority produces a signing certificate and an encryption certificate.

9. Copy the contents of the signing certificate into a file called signCertificate.cer.

10. Copy the contents of the encryption certificate into a file called encryptCertificate.cer

11. Find the root CA certificate for the certificate authority and copy the contents into a file called

ca.cer.

12. Copy ca.cer, signCertificate.cer, and encryptCertificate.cer to c8_location/bin.

These files must be PEM (Base-64 encoded ASCII) format.

13. Import the signing certificate from step 10 into the Cognos signing key store by typing the fol-

lowing command:


ThirdPartyCertificateTool.sh -i -s -r signCertificate.cer -D ../configuration/signkeypair -p

password -t ca.cer

On Windows, type

ThirdPartyCertificateTool.bat-i -s -r signCertificate.cer -D ../configuration/signkeypair -p

password -t ca.cer


The command reads the signCertificate.cer and ca.cer files in the c8_location\bin directory and

imports the certificates from both files into the jSignKeystore file in the signkeypair directory

using the specified password.

14. Import the encryption certificate from step 11 into the Cognos encryption key store by typing

the following command:

Readme Updates 77



ThirdPartyCertificateTool.sh -i -e -r encryptCertificate.cer -D ../configuration/encryptkeypair

-p password -t ca.cer

On Windows, type

ThirdPartyCertificateTool.bat -i -e -r encryptCertificate.cer -D ../configuration/encryptkeypair

-p password -t cacert.cer


The command reads the encryptCertificate.cer and ca.cer files in the c8_location\bin directory

and imports the certificates from both files into the jEncKeystore file in the encryptkeypair

directory using the specified password.

15. Import the CA certificate from step 12 into the Cognos trust store by typing the following

command:


ThirdPartyCertificateTool.sh -i -T -r ca.cer -D ../configuration/signkeypair -p password

On Windows, type

ThirdPartyCertificateTool.bat -i -T -r ca.cer -D ../configuration/signkeypair -p password

The command reads the ca.cer file and imports the contents into the jCAKeystore file in the

signkeypair directory using the specified password.

The certificates are new ready to be configured for Cognos 8. For instructions, see the topic about

configuring Cognos 8 components to run within a third-party certificate authority in the Installation

and Configuration Guide.

Upgrade .NET Security for Cognos 8 Go! Office Smart ClientIf you use the Cognos 8 Go! Office smart client, you must upgrade the .NET security to be able

to use the new version.

Steps

1. From the Start menu, click Settings, Control Panel.

2. Start Administrative Tools.

3. Start the Microsoft .NET Framework 1.1 Configuration tool.

4. Expand the Runtime Security Policy, User, Code Groups node or the Runtime Security Policy,

Machine, Code Groups, All_Code node.

5. Right-click the group you created for Cognos 8 Go! Office, and click Properties.

6. Click the Membership Condition tab.

7. Click Import, and then browse to the location on the server where the new ExcelSmartClient.

dll or WordSmartClient.dll file is located.

78


If you can access the directory where Cognos 8 is installed, you can browse to the c8_loca-

tion\webcontent\coc directory and select either ExcelSmartClient.dll or WordSmartClient.dll.

Otherwise, you can browse to the directory using a Web path, such as

http://server_name/cognos/coc. You may have to type the name of the file, either

ExcelSmartClient.dll or WordSmartClient.dll.

8. Select the ExcelSmartClient.dll or WordSmartClient.dll file and click Open.

The public key is imported from the file along with the name and version of the key. The same

public key is used for both files. Do not select these options. They must remain cleared.

9. Click OK.

You can now use the new version of Cognos 8 Go! Office. Ensure that the CognosGateway custom

property has been updated if it has changed.548712

Configuring Cognos 8 Go! OfficeThe following text replaces the introductory text for Chapter 8: Configuring Cognos 8 Go! Office.

Cognos 8 Go! Office is automatically installed with all Cognos 8 server products, except for Cognos 8

Metrics Manager.

To use Cognos 8 Go! Office, you must perform some or all of the configuration tasks described

below, depending on your environment. You must set custom properties in template files from

which Microsoft Office users will create documents, spreadsheets, and presentations or you must

set custom properties in a document, spreadsheet, or presentation. Template files for Microsoft

Excel, Microsoft Word, and Microsoft PowerPoint are provided with Cognos 8.

Deployment Options for Cognos 8 Go! Office

Cognos 8 Go! Office uses the Microsoft .NET Framework to allow users to interact with server-

based components. All Cognos 8 Go! Office users must have Microsoft .NET Framework version

1.1 SP1 installed on their computers. Client computers must also have Microsoft .NET Framework

configured for the Microsoft Office applications they will use with Cognos 8 Go! Office.

Cognos 8 Go! Office provides two types of clients: a smart client, and a COM add-in client. A

Cognos 8 installation can support both smart client and COM add-in deployments.

A deployment using the smart client provides easier maintenance because users do not have to

install Cognos 8 Go! Office on their computers. If Cognos 8 Go! Office is upgraded with a later

release, users of the smart client automatically use the new version after updating the Microsoft

.NET Framework security. To use Cognos 8 Go! Office with the smart client requires configuring

custom properties in a worksheet, document, or template file. It also requires configuring the

Microsoft .NET Run-time security policy to allow the Cognos 8 Go! Office smart client to run.

A deployment using the COM add-in client requires that an installation be run on user computers

and that custom properties be configured in Microsoft Office files or templates. If Cognos 8 Go!

Office is upgraded with a later release, COM add-in users must install the newer version.

Microsoft Excel and Microsoft Word users with Microsoft Office 2003 Professional can use the

Cognos 8 Go! Office smart client or the COM add-in client.

Readme Updates 79


Microsoft Office XP and Microsoft Office 2003 Standard users and all Microsoft PowerPoint users

must use the COM add-in client.

Microsoft Office files or templates that are configured for Cognos 8 Go! Office can be stored in a

central location, emailed to other users, or published to Cognos Connection. The deployment

options that you choose for these files depends on your environment. Users can also configure their

own files with the appropriate custom properties to access Cognos 8 Go! Office.

To deploy Cognos 8 Go! Office with PowerPlay, you can configure gateway mappings so that

Cognos 8 Go! Office users can access PowerPlay reports that reside on a PowerPlay server. You

can also configure the size of report that can be imported from Cognos 8 to Cognos 8 Go! Office.

For more information about gateway mappings and report size limits, see the Administration and

Security Guide.548712

Add Microsoft .NET Framework Functionality to Microsoft Office ComponentsMicrosoft .NET Framework functionality for smart client users is added to Microsoft Office 2003

Professional components using the Add or Remove Programs utility for your Windows operating

system.

For users of the COM add-in, an installation program must be run on each computer where Cognos 8

Go! Office will be used. The COM add-in provides .NET Framework functionality for the following

users:

● Microsoft Office XP users

● Microsoft Office 2003 Standard users

● Microsoft Office 2003 Professional users who use the COM add-in deployment of Cognos 8

Go! Office

● Microsoft PowerPoint users

The installation utility is provided in the c8_location\webcontent\coc directory. The installation

establishes a COM object and copies required Microsoft .NET programmability files specific to the

user’s environment. The installation utility can be run remotely or copied to user computers to be

run locally.

Steps for Smart Client Users

1. From the Start menu, click Settings, Control Panel.

2. Start Add or Remove Programs.

3. Click Microsoft Office Professional Edition 2003 and click Change.

The Microsoft Office 2003 Setup dialog box appears.

4. Click Add or Remove Features, and click Next.

5. Select the Choose advanced customization of applications check box.

80


6. Expand each Microsoft Office component, click .NET Programmability Support and click Run

from My Computer.

You must select this for Microsoft Excel, Microsoft Word, and Microsoft PowerPoint.

7. Click Update.

8. If a dialog box appears requesting the location of the Microsoft Office Professional Edition

2003 disk, specify the location of a PRO11.MSI file that can be used to install Microsoft Office

and than click OK.

You must also follow the steps below if you are using Microsoft PowerPoint with Cognos 8 Go!

Office.

Steps for COM Add-in Users

1. Run the installation utility, which is located in the c8_location\webcontent\coc directory:

● For Microsoft Office XP, double-click COCOfficeXPAddinSetup.msi.

● For Microsoft Office 2003 Standard users, Microsoft PowerPoint for Microsoft Office

2003 Professional users, or Microsoft Office 2003 Professional COM add-in users, double-

click COCOffice2003AddinSetup.msi.

The file is located in the c8_location\webcontent\coc directory. Users can run the file from this

location if they have access, or the file can be copied to a central location and run from there.

2. Follow the instructions in the installation utility.

If you install Cognos 8 Go! Office for Everyone, the Cognos 8 Go! Office will not appear in

the COM add-in menu in your Microsoft Office product. If you install it for Just Me, you will

be able to see Cognos 8 Go! Office in the COM add-in menu.

548712

Configure Cognos Components to Run Within the Application ServerCognos 8 must be configured with the application server configuration information, and the con-

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

Steps

1. 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.sh

If you have existing incompatible encryption keys, you will be prompted to automatically

generate new ones at this time.

Readme Updates 81


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.

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 Gateway

External dispatcher URI

Internal dispatcher URI

Dispatcher URI for external applications

● Gateway URI

● Content Manager URIs

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

82


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 passwords

If 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

Configure the Gateway for Cognos Apache Web Server ModuleCognos 8 provides two Apache modules. The Cognos Apache module requires Apache Server 1.3.x

and the Cognos Apache 2 module requires Apache Server 2.0.x.

Steps

1. Stop Apache Web Server.

2. Append the c8_location/cgi-bin directory to the appropriate environment variable:

● On Solaris or Linux, LD_LIBRARY_PATH

● On HP-UX,

For Apache 1.3, SHLIB_PATH

For Apache 2.0, SHLIB_PATH and LD_LIBRARY_PATH

● On AIX, LIBPATH

3. On HP-UX PA-RISC, do the following:

● Ensure that the LD_PRELOAD environment variable contains /usr/lib/libcl.2.

● For Apache 1.3, set the COG_CGIBIN_DIR environment variable to c8_location/cgi-bin.

4. Go to the Apache_installation/conf directory.

5. Open the httpd.conf file in an editor.

Readme Updates 83


6. Add the following to the end of the load module list:

LoadModule cognos_module "c8_location/cgi-bin/module_name"

where module_name is as follows:

Apache 2.0moduleApache 1.3moduleOperating system

mod2_cognos.dllmod_cognos.dllWindows

mod2_cognos.somod_cognos.soSolaris, AIX, or

Linux

mod2_cognos.slmod_cognos.slHP-UX PA-RISC

mod2_cognos.so(not supported)HP-UX IA

On Linux, Apache 2.0 module is required.

7. For Apache 1.3, add the following to the end of the add module list:

AddModule mod_cognos.cpp

8. Add the following to the aliases section:

ScriptAlias /cognos8/cgi-bin "c8_location/cgi-bin"

Alias /cognos8 "c8_location/webcontent"

<Directory "c8_location/webcontent">

Options Indexes MultiViews

</Directory>

The <Directory> directive is optional.

Tip: Ensure that you define the cognos8/cgi-bin alias before the cognos8 alias.

9. Add the following to the server status reports section:

<Location /cognos8/cgi-bin/cognos_module>

SetHandler cognos-handler

</Location>

10. To enable the gateway diagnostic page, add the following to the server status reports section:

<Location /cognos8/cgi-bin/diag_cognos_module>

SetHandler cognos-handler

</Location>

The diag_ string is required.

11. For Apache 1.3, on Windows, Solaris, and AIX, add the following to the user directory section:

<IfModule mod_cognos.cpp>

CGIBinDir "c8_location/cgi-bin"

</IfModule>

84


12. For Apache 2.0, add the following to the user directory section:

<IfModule mod_cognos.c>

CGIBinDir "c8_location/cgi-bin"

</IfModule>

13. Save and close the file.

14. For Apache 2.0, on HP-UX, enable searching for LD_LIBRARY_PATH by running the following

command in the Apache_installation/bin directory:

chatr +s enable +b enable httpd

15. Start Apache Web Server.

16. In Cognos Configuration, configure the Gateway URI property to use the apache_mod gateway:

http://host_name:port/cognos8/cgi-bin/filename

where filename matches the name that you used in step 9.

550194

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.

Steps

1. Start your Microsoft Office application.

2. From the Tools menu, click Customize.

3. Click the Commands tab.

4. Under Categories, click Tools.

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:

Readme Updates 85


COMAddInShim.dll

COMAddInShimXP.dll

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

Setting Up LoggingNote: This topic will include the following corrections in the next version of the Administration

and Security Guide.

Currently, this topic contains references to the file crnserver.log. The file name is incorrect and must

be changed to cogserver.log.

Change the Suppression Functionality in Analysis StudioNote: This topic will be added to the Customizing the Functionality of Cognos 8 section in the

Cognos 8 Administration and Security Guide in a future release.

Cognos 8.0 uses totals-based suppression to remove rows or columns throughout the analysis where

the total result is a null or zero value. This approach has several limitations. For more information,

see "Suppressing Empty Cells" (p. 91).

In Cognos 8.2, the default suppression functionality uses selection-based suppression. You can

select a single row or column to remove rows or columns in the opposite axis of the crosstab that

contain only empty cells.

However, you can change back to the original Cognos 8.0 functionality of totals-based suppression.

Steps

1. Go to the c8_location/configuration directory.

2. Locate the file named ansproperties.xml.sample, and rename it to ansproperties.xml.

3. Open the ansproperties.xml file, and locate the following code:

<structure></structure>

4. Remove the comment tags () from the Enable8Dot0Suppression property.

5. Change the value from 0 to 1.

6. Save the ansproperties.xml file.

7. Restart the Cognos 8 server.

Deploying Cognos 8 Go! Office ClientThe following paragraphs replace the paragraphs in the same topic on page 185 of theAdministration

and Security Guide.

Cognos 8 Go! Office is automatically installed with Cognos 8. After Cognos 8 is installed and

configured, you can deploy Cognos 8 Go! Office to client workstations.

Cognos 8 Go! Office uses the Microsoft .NET Framework to allow users to interact with server-

based components. All Cognos 8 Go! Office users must have Microsoft .NET Framework version

1.1 SP1 installed on their computers. Client computers must also have Microsoft .NET Framework

configured for the Microsoft Office applications they will use with Cognos 8 Go! Office.

Cognos 8 Go! Office provides two types of clients: a smart client, and a COM add-in client. A

Cognos 8 installation can support both smart client and COM add-in deployments.

A deployment using the smart client provides easier maintenance because users do not have to

install Cognos 8 Go! Office on their computers. If Cognos 8 Go! Office is upgraded with a later

release, users of the smart client automatically use the new version after updating the Microsoft

.NET Framework security. To use Cognos 8 Go! Office with the smart client requires configuring

custom properties in a worksheet, document, or template file. It also requires configuring the

Microsoft .NET Run-time security policy to allow the Cognos 8 Go! Office smart client to run.

A deployment using the COM add-in client requires that an installation be run on user computers

and that custom properties be configured in Microsoft Office files or templates. If Cognos 8 Go!

Office is upgraded with a later release, COM add-in users must install the newer version.

Microsoft Excel and Microsoft Word users with Microsoft Office 2003 Professional can use the

Cognos 8 Go! Office smart client or the COM add-in client.

Microsoft Office XP and Microsoft Office 2003 Standard users and all Microsoft PowerPoint users

must use the COM add-in client.

Use the following tables to determine the configuration tasks required for the deployment method

you want to use. Both deployment methods require Microsoft .NET Framework to be installed on

all Cognos 8 Go! Office user computers.548712

Access PermissionsNote: This topic will include the following addition in the next version of the Cognos 8 Adminis-

tration and Security Guide.

Readme Updates 87


Accessing Objects Associated with Data Sources Secured Against Multiple Namespaces

Data 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 para-

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

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.

88


RSVP.PROMPT.RECONCILIATION Settings

COMPLETE 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 admin-

istration secured feature and traverse permission for the Administration secured function.

Steps

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

Model-based vs. Report-based Drill-through AccessNote: This topic will include the following corrections in the next version of the Cognos 8 Admin-

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

Readme Updates 89


● 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 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 Admin-

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


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 Admin-

istration and Security Guide, the chapter "Drill-through Access".

● The following sentences must be modified:

90


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.


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 Admin-

istration 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 Admin-

istration 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

Readme Updates 91


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 sup-

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

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 admin-

istrator, 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 back-

ground information to help you create a project, prepare a model for reporting, and create and

publish a package.

92


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

Set GovernorsNote: This topic will include the following additions in the next version of the Framework Manager

User Guide.

SQL Join Syntax

You can control how SQL is generated for inner joins in the current model by selecting the Use

model specific SQL join syntax check box. You then specify one of the following settings:

● The Implicit setting uses the WHERE clause. This is the default setting.

An example is the following:

SELECT publishers.name, publishers.id,books.title FROM publishers, books WHERE publishers.id= books.publisher_id ORDER BY publishers.name, books.title ;

● The Explicit setting uses the FROM clause with the keywords INNER JOIN in an ON predicate.

An example is the following:

SELECT publishers.name, publishers.id,books.title FROM publishers INNER JOIN books ON publishers.id= books.publisher_id ORDER BY publishers.name, books.title ;

If you do not set this governor, Framework Manager uses the default setting.

Regardless of the setting you use for this governor, the Explicit setting is used for left outer joins,

right outer joins, and full outer joins.

This governor has no impact on typed-in SQL.

Upgrading the ModelNote: This topic will include the following addition in the next version of the Guidelines for Mod-

eling 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 Mod-


Readme Updates 93


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.

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 rela-

tionship between the query subjects uses only a subset of these columns. Modify the determinant

94


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 Mod-


Use determinants to ensure that the aggregation in reports is correct and that queries generate cor-

rectly.

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 define three 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

Readme Updates 95


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 automat-

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


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.

Change Prompt ValuesAfter prompts are set the first time in the IBM Cognos Viewer window and the report is imported

into a Microsoft Office document, you can change prompt answers or set answers for prompts.

The default setting is Specified Value. If you change the server from which you are reading reports,

prompted reports are returned to this default and you must manually reset the report to Always

Prompt or Cell Value, even if the package and report names are identical.

Specified Value

Sets the answer to the prompt. Users must provide a prompt value, which appears in the Use Valuebox. The value is saved for future renditions of the Office document.

Applies to Excel, Word, and PowerPoint.

96


Always Prompt

Requires the user to be prompted. No value is saved and the user is prompted each time the report

is refreshed.


Cell Value

Specifies an Excel cell for the prompt answer and requires that the cell reference is typed into the

Cell Reference box, where the worksheet, column, and row location is saved for future renditions

of the workbook.

Applies only to Excel.

Custom Property

Specifies the name of the user-defined custom document property that is stored with the workbook

or document. The name must match the name that is entered in the Microsoft Office custom docu-

ment property, and is saved for future renditions of the Office document.

The prompt answer is assigned to the custom property. If the <prompt> value is entered in the

Microsoft custom document property, users are prompted the first time the report is run or refreshed,

and that value is saved.


Steps

1. In the IBM Cognos 8 pane, on the Manage Data tab, in the Properties pane, expand the Promptlist.

The list of parameters appears.

2. Expand each of the parameters.

3. Choose one of the prompt options:

● To define the value for a prompt, in the Type box, click Specified Value, and then, in the

Use Value box, type the prompt answer, which is saved for future renditions of the Microsoft

Office document.

● To define the Excel cell reference for the prompt value, in the Type box, click Cell Value,

and then, in the Cell Reference box, click the ellipsis (...) button, type the cell location,

such as Sheet1!A7, and click OK. In the cell location that you specified, type the prompt

value.

● To prompt the user for a value whenever the report is imported into the Microsoft Office

document, in the Type box, click Always Prompt.

● To prompt the user for an initial value that is used for the same prompt in multiple reports

in a document, in the Type box, click Custom Property, and then, in the Custom Propertybox, type the name of the custom document property.

Readme Updates 97


From the File menu, click Properties, and then click the Custom tab. In the Name box,

type a name for the custom document property. The name you enter must match the name

in the Custom Property box in the Properties pane.

In the Type box, click the data type for the property that you want to add.

In the Value box, type the prompt answer based on the data source:

If the data source is dimensionally modeled relational data that does not contain a member

unique name (MUN), type <prompt> or the prompt answer.

If the data source is PowerCubes, copy the Member Unique Name (MUN) from the Use

Value property box. The MUN contains the fully qualified path to where the member exists

in the multidimensional structure.

The value you enter is saved for future renditions of the Microsoft Office document. Users

are prompted the first time the report is run or refreshed.

Tip: You can use VBA and a command line interface to set the value of a custom document

property. The API can be called within the Microsoft document using VBA to run through

the list of prompt answers to get the results that you want.

In some cases, the display value for the prompt is not the same as the use value. The use value

is the value in the data source and this must be used for any cell references created in Excel.

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.

Create a Metric TypeYou create metric types to define attributes and calculations for a collection of related metrics.

Trend calculation is a global setting and not set for each metric type.

Importing a Metric Type

You can also import a metric type from an external data source using Metric Designer or an ETL

tool and a metric type stage file (.cmm).

Status Calculation Methods

Metric Studio determines status by using either a single target and a tolerance or multiple thresholds.

In the tolerance-based method, the target determines the point at which the status turns green. The

tolerance determines a range above or below the target at which the status is yellow. If you use 5-

state status indicators, the tolerance also determines the range for the half-red and half-green states.

In the threshold-based method, the target and user-defined columns determine the status color.

98


Rollups

A rollup defines how values for actual, target, user-defined column, and tolerance metrics are

summarized.

Steps for General Settings

1. At the bottom of the left pane, click Metric Types, and then click the new metric type button

on the toolbar.

2. Click the General tab.

3. Under Language, select the language that you want.

4. In the Name box, type a descriptive name for the metric type.

5. If you want, in the Description box, type a description of the metric type.

6. If you want, in the Technical description box, type a technical description of the metric type.

7. If you want to change the owner, do the following:

● Click Change Owner.

The Select User window appears.

● On the Navigate tab, click the owner that you want.

Tip: You can instead click the Search tab, type all or part of the name of the owner, and

then click the string criterion, the Scope item, Search, and the owner that you want.

8. If you want, in the Identification code box, type a code for this metric type.

If you leave this box blank, Metric Studio automatically generates an identification code.

9. Click the Default group view value that you want.

10. Under Calendar Details, do the following:

● Click the Business calendar level value that you want.

The level that you choose sets the lowest level at which Metric Studio stores data. For

example, if you select quarterly, Metric Studio does not load monthly values.

If you add a lower calendar period to your calendar, such as adding days to a calendar that

contained years and months, you must reload your metric data for the data to be allocated

to the new level.

● Click the Business calendar level for most recent values view level that you want.

The level that you choose sets the level of data that Metric Studio shows in the latest data

view. For example, if you choose monthly, Metric Studio shows data for the latest month

for which there is a score. If there is no score for the latest month, Metric Studio shows

the latest month with actual values. If a metric has no score or actual value, then Metric

Studio shows the period based on the last time a score was successfully generated for other

metrics. If the metric store has never had scores calculated, then Metric Studio displays No

data.

Readme Updates 99


11. Under Number Format, do the following:

● Under Unit, click the unit of measurement for the metric type.

If you choose Currency, General, or a user-defined unit as the unit of measurement, the

default Tolerance type, on the Value Types tab, is Percentage.

If you choose Percent as the unit of measurement, the default Tolerance type, on the Value

Types tab, is Absolute.

● Under Unit Symbol, click Display unit symbol or Do not display unit symbol.

If you choose Currency, General or a user-defined unit as the unit of measurement, the

default Tolerance type, on the Value Types tab, is Percentage.

If you choose Percent as the measurement, the default Tolerance type, on the Value Types

tab, is Absolute.

● Under Decimal Places, click the number of decimal places to show for the metric type.

12. Under History Chart Properties, do the following:

● Type the value for Minimum value.

● Type the value for Maximum value.

● If you want, select the Show zero value check box.

13. Click OK or continue by specifying how metric values are calculated.

Steps to Specify How Metric Values Are Calculated

1. Click the Value Types tab for the metric type that you are creating.

2. Under Metric type default calculation, click No calculation - this value will be loaded or entered

or Define calculation.

3. If you select Define calculation, do the following:

● Click Edit.

● Define the expression for the calculation.

● Click OK.

4. Under Actual and Target, do the following:

● Click the Business calendar rollup calculation to use.

Metric Studio rejects data that is loaded and entered at a level other than the one you specify

unless you select Rollup is supplied by client and the data entry levels are equal to or greater

than the business calendar level for the metric type.

If you define a calculation for actual, target, tolerance, or user-defined columns, the values

for business calendar rollup calculations change to reflect the after rollup and before rollup

behaviors of the calculated metric types. The rollup is supplied by client value is not avail-

able.

100


● Click the Business calendar level for loading and entering data level that you want.

● Click the type of Value calculation to use.

If you select Define Calculation, see step 3.

5. Under Tolerance, do the following:

● Select the Tolerance type to use.


For more information, see step 4.


● Click the type of Value calculation to use.

If you select Define Calculation, see step 3.

6. Under User Defined Columns, do the following:


For more information, see step 4.


● Click the columns to which these settings apply.

7. Click OK or continue by specifying performance behavior for the metric type.

Steps to Specify Performance Behavior

1. Click the Status Indicator tab for the metric type that you are creating.

2. Click the Performance pattern value that you want.

3. Under Score Settings, do the following:

● Click Use default score calculation or Set target boundaries with user defined columns.

● If you select Set target boundaries with user defined columns, you must set the target

thresholds that define the status of a metric.

The available thresholds are either user-defined columns or targets.

In a 3-state environment, from the list of available thresholds, click the criteria for changing

the status from red to yellow and from yellow to green.

In a 5-state environment, from the list of available thresholds, click the criteria for changing

the status from green to partially green, from partially green to yellow, from yellow to

partially red, and from partially red to red.

4. Click OK or to set security for the metric type, click the Permissions tab.

Steps to Set Metric Type Security

1. Click the Permissions tab for the metric type that you are creating.

Readme Updates 101


2. To change or add users, click Edit.

3. Click OK.

Choose the Period to MonitorYou can select the period to monitor using the calendar control. For example, if your business cal-

endar supports years, quarters, months, and weeks, you can choose to view metric values at the

monthly level. Metric Studio shows the metric values for the chosen month. Weekly values, if

available, are displayed as the rollup values for monthly level. No quarterly or yearly values are

shown.

Latest Data View

If you select the latest data, Metric Studio shows the most recent metric values that it can. For

example, you can have some metric values shown as of the last quarter and some metric values

shown for last month.

The latest period is always the period for which there is a score. For example, you have a metric

value for the last month and a score for the last quarter. Metric Studio shows the score, even though

it is older, because it is more meaningful than a value. If no period has a score then the latest actual

is used. If a metric has no score or actual value, then Metric Studio shows the period based on the

last time a score was successfully generated for other metrics. If the metric store has never had

scores calculated, then Metric Studio displays No data.

You can set the calendar level for a history chart, a history list, and a metric list on a scorecard,

metric type, group, or objective.

To-date Status

If you select the Show the to-date status and values for open periods as of date option, you can

make more precise comparisons between actual data and target data. This option changes the target

value to reflect the target up to the current open period from one calendar level below rather than

to the end of the current period. It also changes all user-defined columns. The to-date target values

are the aggregation of lower calendar level values up to the current open period and cannot be

loaded.

For example, assume that the sales target for the quarter is to sell 1000 radios, and by mid-quarter

500 radios are sold. If you do not select this option, your status is red because you are comparing

the 500 radios sold to the target for the end of the quarter, which is 1000 radios. If you select this

option, the status is green because you are comparing the 500 radios sold to the sales target up to

this mid-quarter date, which is 500 radios.

If you select the Show the to-date status and values for open periods as of date option, Metric Studio

uses the most recently loaded actuals date as the date to which all targets are calculated. Any date

after the current system date is reset to today’s date.

If the results are not as you expect, it may be because of one of the following;

● To-date status does not exist for the lowest level in the time hierarchy.

For example, there is no monthly to-date status when the minimum grain is month.

102


● The time level of the metric used for actual calculation is at a higher level than the target data

for the metric that you are monitoring.

For example, the metric that you are monitoring has target values at the month level but no

actuals for the month level. The metric that Metric Studio uses to calculate the to-date status

has quarters as its lowest time level. Therefore Metric Studio displays the to-date status at the

year level.

● In the most recent data view, there is no to-date data that matches the latest period. That could

be because the most recent data is a future date.

● Actual data is entered at the year level, in which case no to-date values are available.

● Data was staged for all calendar levels of a metric type.

● The data is being viewed at a calendar level that is lower than the calendar level at which data

was entered.

● In the history chart and metric history list, you are viewing future dates.

Steps

1. Click the business calendar options button next to Business calendar period.

2. Click

● Select a period to view

To view values at a specific calendar level, click View values at specified business calendar

level and calendar period and click the calendar level that you want.

● View most recent values

3. If you want to compare actual data against target data up to the current open period, select

the check box next to Show the to-date status and values for open periods as ofdate.

4. Click OK.

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.

Readme Updates 103


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.

Grouping by an Attribute is Not SupportedNote: This topic will be added to the Report Studio User Guide and the Query Studio User Guide

in a future release.

When working with dimensional data sources, grouping by attributes is not supported. If you group

by an attribute, the corresponding member is grouped instead, and there may be duplicate rows.

For example, a list report contains the columns Color and Product Code, where Color is an attribute

of Product Code. When you run the report, some colors, such as black, appear multiple times

because several products are available in black. Each product is available in only one color, so the

list has only one row for each product. Grouping the Color column does not change the output

because the grouping is done on the Product Code column, and there is only one row for each

product in the list. If the Product Code column is deleted, the output shows duplicate rows for some

colors, such as black.

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 is

ReportOption(optionName)

The correct syntax to use is

ReportOption('optionName')

520550, 546444

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.

104


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.

Readme Updates 105


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

106


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.

Allow Is Missing

The Report Studio property Allow Is Missing was deleted.548298

SQL join syntax

Controls the syntax to generate for joins. Click Implicit to generate joins in the WHERE clause.

Click Explicit to generate INNER JOIN syntax. If unspecified, the value of the corresponding

governor in the model is used.

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 3

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

Readme Updates 107


● 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 6

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


Data Manager Installation and Configuration GuideThis section contains additions and corrections that will appear in the next version of the Data

Manager Installation and Configuration Guide.

Install the SAP Gateway FunctionsSAP ERP Central Components are incorrectly identified as SAP ERP Core Components.

The topic will be corrected in the next version of the guide.

Cognos 8 SDK Developer GuideThis section contains additions that will appear in the next version of the Cognos 8 SDK Developer

Guide.

Report Specification Reference

useSQLJoinSyntax

Specifies whether to use explicit or implicit join syntax in Cognos SQL. The explicit join syntax is:

select a.a, b.b from inner join b on (a.c=b.c). The implicit join syntax is: select a.a, b.b from a, b

where a.c = b.c.

If you do not specify this governor on the query in the report specification, the syntax is determined

by the setting in the package. When you specify this governor on the query, it overrides the setting

in the package. When this governor is not specified in either the query or the package, the default

is to use implicit join syntax.

108


When a query involves an outer join as defined in either the model or the query, then all the joins

in the query are expressed using explicit join stoats. A FULL OUTER JOIN that is generated to

support a multi-fact query does not cause all other joins to use explicit join syntax.

value attribute

Specifies a value for this query hint or governor.

enumeration values for the value attribute:

explicit

The Cognos SQL uses explicit join syntax.

implicit

The Cognos SQL uses implicit join syntax.

Readme Updates 109


110


Chapter 4: 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 ofIntent 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

Readme Updates 111

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"/>

Effect

When multiple security filters are defined in the Data Security setting in Framework Manager for

a query subject, if a user belongs to more than one user group associated with these filters, the effect

of this switch is to perform a union of these filters instead of an intersection. For example, if a user

Joe belongs to a corporate group allowing him to see data for Asia, Europe, and America, and also

belongs to a regional group allowing him only to see data for Europe, the effect of the switch will

be to let Joe see data for Asia, Europe, and America (as compared to just Europe) when logging on

Cognos 8 and authoring or running a report. Note that security filters that are based on other

security filters in the Data Security settings for a query subject continue to be intersected, just as

before, independent of whether or not the new switch is activated.

As of Cognos 8.3, this behavior will become the new default for SAP BW metadata in Framework

Manager. There will be no change to the behavior of security filters applied on relational sources.

The switch will continue to be available and can be set to false by your administrator if required

to maintain existing application behavior.

112

Chapter 4: Deprecation Notices

Index

Symbols.eqi, 103

.equ, 103

.NET

security upgrade for Cognos 8 Go! Office Smart

Client, 78

.pro files, 92

Aaccented characters

not displayed properly, 18

accessing data sources, 31, 34

access permissions

documentation updates, 87

actions

notification email, 49

Administration and Security Guide, 86

Adobe Acrobat

Web link errors in 7.x, 29

Adobe Reader

versions required for printing reports, 30

aggregates

footers calculated differently, 39

aggregate type

rollup, 39

AIX

version, IBM WebSphere, 22

aliases

configuring on Apache Web Server, 83

Allow Is Missing property, 107

Analysis Studio

changing suppression default, 86

context filter limitations, 41

custom sets, 41

dashes appearing instead of values, 41

empty dimensions, 62

Excel reports, 41

instability with MS SQL Server 2005, 17

Japanese Internet Explorer, 41

limitations, 41

User Guide doc update, 91

wrong currency symbol, 42

Analysis Studio quick tour, 92

Analysis Studio User Guide, 91

Apache

Web server and help problems, 30

Apache gateways

configuring, 83

Apache Web servers

configuring as gateways, 83

application servers

selecting in the Build Application Wizard, 67

applying

filters to dimensional reports, 104

Architecture and Deployment Guide, 68

a socket reported a communication error, 24

as percentage

values, 43

attribute-based sorting, 44

Bbackslashes appear instead of currency, 19

BEx queries

hierarchies in characteristic structures, 62

blank values

appearing instead of totals, 39

BME script player

errors, 58

Build Application Wizard


selecting the application server, 67

bursting

MOLAP data, 106

business keys


Ccalculated

metrics, 49

calculated key figures, 35

Readme Updates 113

calculated metrics

constants, 50

calculations

CognosViewer, 44

format rules, 91

in filters, 61

SAP BW, 60

SAP BW data sources, 34

user-defined functions, 60

calendar

delete periods, 52

calendar levels

latest data view, 102

specifying view, 102

calendar settings

metric types, 50

CAM-CRP-1157 error, 17

certificate signing requests

generating, 75

changes to decimal formats, 27

changing

package reference, 44

changing suppression default

Analysis Studio, 86

character display

incorrect, 50

character encoding

and help problems with Apache Web server, 30

characteristic structures

hierarchies, 62

character sets

Oracle mismatch and filters, 31

characters improperly displayed, 18

charts not appearing, 24

classes12.jar file, 71

COC-ERR-2607, 64

Cognos 8

integration with Cognos Planning, 22

service does not start, 17

Cognos 8 Go! Office

adding .NET Framework functionality to Microsoft

Office components, 80

changing prompt values in, 66, 96

disabling for COM add-in users, 85, 108


DPR-ERR-2079 Firewall Security Rejection error, 65

expired sessions, 65

incorrect format for prompt values, 64

installation and configuration issues, 63

known issues, 63

opening in Microsoft Word, 65

Cognos 8 Go! Office errors

Cannot Open a Report in Excel in Cognos Connec-

tion If You Have a COM Add-in Workbook

Open, 63

No Report Content Is Imported When the Report

Name Contains a Single Quote, 64

The Cognos Action Pane Disappears When Using

the Smart Client and You Run a Report in Excel

in Cognos Connection, 64

Workbook Closes Unexpectedly If Name Contains

Square Bracket, 63

Cognos 8 Go! Office Smart Client

upgrade .NET security, 78

Cognos 8 Mobile Analysis

choosing the installed product language, 22

Cognos 8 Planning and SAP BW data, 96

Cognos 8 Transformer

choosing the installed product language, 22

Cognos Content Database

uninstalling, 70

Cognos Planning

integration with Cognos 8, 22

Cognos Planning - Contributor

connecting to data source, 24

Cognos PowerCubes

open slowly, 25

Cognos product compatibility, 68, 74

Cognos Viewer

calculations, 44

cogserver.log


configuration settings, 44

configuring

Cognos 8 for application servers, 81

Cognos 8 Go! Office, 79, 87

issues with Cognos 8 Go! Office, 63

content store

compatible versions of DB2 and Java, 17

context filter limitations, 41, 43

converting

query subjects, 93

114

Index

creating

metric types, 98

creating package

fails, 48

crnserver.log


crnserver.log, See cogserver.log

crosstabs

aggregate values not appearing, 39

incorrect running totals, 38

no data returned when same dimension used on both

edges, 34

set expressions that depend on current measure

return incorrect data, 38

cryptographic keys

generating for third-party certificate authorities, 75

cubes

PowerCubes open slowly, 25

currency

won, 19

yen, 19

currency values

appear as numbers in reports, 27

custom formatting

not appearing for empty cells, 35

custom sets in Analysis Studio, 41

Ddashes

appearing instead of values in Analysis Studio, 41

databases

Oracle character set mismatch, 31

Data Manager Installation and Configuration Guide, 108

data sources

connecting to Cognos Planning - Contributor, 24

unable to open a cube using 8.2 DB2 OLAP, 33

unable to open a cube using Essbase 7.1, 33

date format

SQL Server 2005, 49

DB2

incorrect average value, 34

incorrect count value, 34

Metric Studio, 48

supported Java versions, 17

DB2 data sources

problems accessing, 31

DB2-ERR-0028, 18

DB2 OLAP

query failure using DB2 OLAP Server, 31

unable to load library, 18

unable to open a cube using 8.2 DB2 OLAP, 33

decimal formats

changes, 27

default setting

SQL Generation, 63

delete

time periods, 52

detailed fact query subjects, 96

determinants, 94, 95

Developer Guide, 108

diagram

error, 48

dimensional data sources

grouping by attributes, 104

dimensional functions, 60

dimensions, 93

converting from query subjects, 93

empty in Analysis Studio, 62

functions, 60

order of members, 61

overlapping named set levels, 28

testing, 61

documentation

Administration and Security Guide, 86

Analysis Studio quick tour, 92

Analysis Studio User Guide, 91

Architecture and Deployment Guide, 68

broken links, 26

Cognos 8 Go! Office, 96

Data Manager Installation and Configuration

Guide, 108

Getting Started, 96

help for Build Application Wizard, 67

Installation and Configuration Guide, 68

Metric Studio User Guide for Authors, 98

Query Studio User Guide, 92, 104

Report Studio User Guide, 104

SDK, 108

Troubleshooting Guide, 108

documentation CD, 26

documentation updates

access permissions, 87

Readme Updates 115

Index

business keys, 90

drill-through access, 89, 90, 91

Framework Manager User Guide, 92

scope, 91

double-byte characters

improperly displayed, 18

DPR-DPR-1035 error, 17

DPR-ERR-2002 error message, 19

DPR-ERR-2079 Firewall Security Rejection error, 65

drill-through access

documentation updates, 89, 90, 91

setting up in a report, 107

drill-through performance, 26

EEAR files, See Enterprise archive files

embedded externalize method, 63

Enterprise archive files

deploying Cognos 8, 71

environments

supported, 111

error messages

COC-ERR-2607, 64

errors

a socket reported a communication error, 24

DB2-ERR-0028, 18

opening Web browser, 51

TR0118, 61

Essbase

incorrect average value, 34

incorrect count value, 34

EssBase 7.1

unable to open a cube, 33

Essbase changes, 30

Event Studio

parsing error, 40

Excel functions, 29

Excel reports

Analysis Studio, 41

expand command in Analysis Studio, 41

expired sessions


export

failing in a distributed installation, 50

exporting

InfoCube, 63

IQD files, 61

Expression Editor

ReportOption function, 104

externalized dimensions, 62

externalizing query subjects, 63

extracting

InfoCube, 63

Ffail

creating package, 48

file not found errors, 26

files

adding multiple IQD, 55

filter expressions

no data, 35

filtering

and Oracle character set mismatch, 31

filters, 62

applying to dimensional reports, 104

calculations, 61

invalid, 54

Find Report Dependencies window, 63

footers

aggregate computed differently, 39

not working for some semi-additive measures, 31

format rules

calculations, 91

formats

changes to decimals, 27

Framework Manager

IQDs and Oracle stored procedures, 61

issues, 57

missing connections and credentials, 54

security filters change for SAP BW, 111

TR0118 error, 61

unable to load DB2 OLAP library, 18

user language preference, 53

Framework Manager User Guide


full outer joins

Oracle, 59

functions

dimensions, 60


ReportOption, 104

116

Index

user-defined, 60

GGetting Started


governors

SQL generation, 93

grouping

first level in a list, 37


grouping columns


Hhelp

problems with Apache Web server, 30

hierarchies

characteristic structures, 62

history chart

error, 48

hyperlinks

errors in Acrobat 7.x, 29

IIBM WebSphere

AIX version, 22

import

failing in a distributed installation, 50

importing

SAP cubes, 57

system objects, 58

Teradata, 57

incorrect average value using DB2 or Essbase, 34

incorrect count value using DB2 or Essbase, 34

InfoCube

exporting, 63

Informix

isolation level, 59

Informix Dynamic Server

supported environments, 111

Informix Red Brick Decision Server


inner joins

SQL Generation setting, 63

instability

in MS SQL Server 2005, 17

installation

choosing the language for Cognos 8 Mobile Ana-

lysis, 22

choosing the language for Cognos 8 Transformer, 22

Installation and Configuration Guide, 68

installation and configuration issues

cannot load DB2 OLAP library, 18

run-time errors, 19

installing

Cognos 8 on Linux, 18

issues with Cognos 8 Go! Office, 63

Internet Explorer

issues with charts in version 6.x, 24

IQD files

adding multiple, 55

problems exporting, 61

replace function, 55

isolation level, 59

issetup

corrupt Japanese characters, 19

JJapanese

incorrect import, 53

Japanese characters corrupted, 19

Japanese currency, 19

Japanese Internet Explorer

Analysis Studio, 41

Java

supported versions for DB2 content store, 17

uses all of CPU, 17

JBoss

selecting in the Build Application Wizard, 67

join relationships

creating in Report Studio, 106

joins, 93

Oracle, 59

SQL Generation setting, 63

Kkey figures, 35, 62

known issues

administration, 24

Analysis Studio, 41


Cognos 8 Transformer, 36

Readme Updates 117

Index

Cognos Connection, 31

DB2 data sources, 31

Event Studio, 40

Framework Manager, 57

general, 25

installation and configuration, 17

Metric Studio known issues, 45

Query Studio, 36

Report Studio, 37


security, 22

Series 7 integration, 22

software development kit, 63

Korean

tilde, 51

Korean currency, 19

Llanguage

choosing for Cognos 8 Mobile Analysis, 22

choosing for Cognos 8 Transformer, 22

languages

OLAP data sources, 43

latest data view, 102

limitations in Analysis Studio, 41

links

errors in Acrobat 7.x, 29

Linux

characters not displayed properly, 18

list reports


lists

grouping on first level, 37

locales

server, 68

logon problems

SAP namespace, 22, 23

lost settings

after import, 48

Mmeasures, 62


semi-additive and footers, 31

members, order of, 61

memory footprint, 63

metadata query failure with DB2 OLAP server, 31

Metric Designer

construct functions, 56

data sources not supported, 55

day level time period filter, 56

error for extract containing static text-type scorecard

levels, 56

error when query items mapped to metrics qualifiers

are referenced in scorecard filters, 56

extracts, 53

filters on parent-child hierarchies not supported for

OLAP, 55

known issues, 52

metric filters invalid after upgrading a model, 54

metrics scope page does not work, 55

missing connections and credentials, 54

problem executing extract from a Teradata data-

base, 54

qualifiers for PowerCube import sources, 56

scorecard tree preview does not work, 55

typed-in constant metric attribute values, 56

user language preference, 53

metric filters not updated correctly, 54

metrics

metric types, 98

not created, 49

Metric Studio

additional columns in Project tab-delimited file, 92

DB2, 48

lost settings, 48

model and report changes, 45

Metric Studio User Guide for Authors, 98

metric types

calendar settings, 50

creating, 98

lost settings, 48

Microsoft

security patch causes server failure, 18

Microsoft .NET programmability support, 64

Microsoft SQL Server 2005

stability issues, 17

missing

calculated metrics, 49

model changes

Metric Studio, 45

118

Index

Mozilla Firefox

problems with help using Apache Web server, 30

Nnamed sets

nested or parallel sets overlapping, 28

namespaces

SAP cubes, 57

nested reports

changes to SAP BW rules for set expression evalu-

ation, 28

Netscape

supported browsers, 111

Netscape Navigator

problems with help using Apache Web server, 30

Oojdbc14.jar file, 71

OLAP data sources

languages, 43

Oracle

driver file conflict, 71

filters and character set mismatch, 31

full outer joins, 59

NLS_LANG environment variable, setting, 50

package creation, 48

replace function, 55

running on 10g, 49


outer joins

Oracle, 59

Ppackage

creation fails, 48

package reference

changing, 44

parsing error in Event Studio, 40

passwords

SAP namespace, 22

PDF

unsupported style properties, 105

PDFs

Web link errors in Acrobat 7.x, 29

performance

drill-through, 26

optimizing PowerCubes for Cognos 8, 25

permissions

changing, 58

pivoting to a crosstab, 40

ports

setting the maximum number for program use, 31

PowerCubes

multiple hierarchies, 36

open slowly, 25

printer friendly page

character display, 50

printing

after restarting dispatcher, 50

printing reports

Adobe Reader versions required, 30

prioritizing queries, 88

problems

report options, 44

SAP namespace, 23

searching, 44

problems accessing DB2 data sources, 31

problems accessing SAP BW data sources, 34

prompted reports

Cognos 8 Go! Office errors, 64

prompts

key figures, 62

prompt values

changing in Cognos 8 Go! Office, 96


Qqueries

do not execute, 36

prioritizing, 88

query failure with DB2 OLAP server, 31

query items

retargeting, 58

upgrading, 93

Query Studio User Guide, 92, 104

query subjects

converting to dimensions, 93

detailed fact, 96

determinants, 94, 95

dimensional functions, 60

externalizing, 63

upgrading, 93

Readme Updates 119

Index

quick tours

documentation update, 92

Rragged hierarchies

Report Studio, 29

refreshing

segments, 58

regular dimensions


relational data sources

footers and semi-additive measures, 31

relationships

creating joins in Report Studio, 106

replace function

IQD, 55

report changes

Metric Studio, 45

ReportNet 1.1 documentation updates

Framework Manager User Guide, 92

ReportNet 1.1 issues

Framework Manager issues, 57

ReportOption, 104

report options

problems, 44

reports

applying filters to dimensional reports, 104

currency values appear as numbers, 27

errors when running, 63


edges of crosstab, 34

report execution fails, 19

setting up drill-through access, 107

unable to run Cognos 8.2 reports in Cognos 8.1, 38

upgrade messages, 106

report server settings, 88

Report studio

pivoting to a crosstab, 40

Report Studio

aggregate values not appearing, 39

Allow Is Missing property, 107

bursting on MOLAP Data, 106

creating join relationships, 106

Key Transformation validation level returns partial

information, 39


edges of crosstab, 34

ragged hierarchies, 29

set options, 106

SQL join syntax property, 107

style properties not supported, 105

unable to run Cognos 8.2 reports in Cognos 8.1, 38

unbalanced hierarchies, 29

Report Studio User Guide, 104

retargeting query items, 58

rollup

aggregate type, 39

RSVP.PROMPT.RECONCILIATION settings, 88

running

reports, 63

running totals

incorrect in crosstabs, 38

run-time errors, 19

Ssamples

error in ELM Returns Agent sample, 40

SAP

password policy, 22

SAP BW

key figures, 35

security filter change in Framework Manager, 111

set expression evaluation rules changes, 28


SAP BW calculations, 60

SAP BW data and Cognos 8 Planning, 96

SAP BW data sources

calculations, 34

grouping columns, 34

measures, 34

problems accessing, 34

sectioning reports, 35

summary rows, 35

SAP cubes

segments, 57

SAP namespace

logon problems, 22, 23

repeated prompts for authentication, 23

SAP NetWeaver Portal


120

Index

scope


scorecards

lost settings, 48

scores

upgrade, 45

script player

errors, 58

searching

problems, 44

sectioning reports


security

.NET upgrade for Cognos 8 Go! Office Smart Cli-

ent, 78

filter change in Framework Manager for SAP

BW, 111

issues with Internet Explorer 6.x security level, 24

Microsoft update causes server failure, 18

problems logging on to an SAP namespace, 22

segments, 58

SAP cubes, 57

server

locales, 68

server error, 29

servers

failing to start, 18

instability with MS SQL Server 2005, 17

Servlet Gateway, 70

Sun ONE, 70

set expressions

changes to SAP BW rules, 28

returns incorrect data when dependent on current

measure, 38

set options

Report Studio, 106

sets

nested or parallel sets overlapping, 28

setting

SQL Generation, 63

Show hidden objects

visual aids button, 107

socket reported a communication error, 24

sorting

attribute based, 44

SQL Generation default setting, 63

SQL generation governor, 93

SQL join syntax property, 107

SQL Server

import Japanese characters, 53

SQL Server 2005, 58

date format, 49

SSL

enabling on Web servers, 69

stored procedures

error in ELM Returns Agent sample, 40

studios

Essbase changes, 30

style properties missing in PDF reports, 105

summary rows


Sun Java Web server, 70

servlet gateway, 70

Sun ONE

servlet gateway, 70

Sun ONE Directory Server



suppress items, 44

Sybase

system objects, 58

synchronizing

errors, 58

system objects, 58

Ttab-delimited files

Japanese characters, 53

Teradata, 57

executing a Framework Manager-based extract, 54

Teradatasystem objects, 58

testing

calculations, 60

dimensions, 61

imported functions, 60

third-party data sources

8.2 DB2 OLAP, 33

EssBase 7.1, 33

tilde

Korean, 51

to-date

view, 102

Readme Updates 121

Index

toolbar buttons, unable to launch, 26

total values


Transformer, 68, 74

pcoptimizer setting, 25

using an IQD created in Framework Manager, 61

Troubleshooting Guide, 108

Uunable to run reports, 19

unbalanced hierarchies

Report Studio, 29

uninstalling

Cognos Content Database, 70

unreadable characters, 50

unsupported Cognos Planning 7.3 features, 22

upgrade

scores, 45

upgrade messages

reports, 106

upgrading, 93

.NET security for Cognos 8 Go! Office Smart Cli-

ent, 78

Cognos 8 fails to start, 18

Upgrading, 68

upgrading models

key figures, 62

user-defined functions, 60

Vvalues

as percentage, 43

view

to-date data, 102

views

specifying calendar level, 102

visual aids button

Show hidden objects, 107

WWAR files, See Web archive files

watchlist

emails for actions, 49

Web archive files

deploying Cognos 8, 71

Web browser

errors when opening, 51

Web servers

Apache and help problems, 30

enabling SSL, 69

won character, 19

Yyen character, 19

122

Index

Documents

Cognos® 8 Business Intelligence Readme Updatespublic.dhe.ibm.com/software/data/cognos/documentation/docs/en/c… · Non-ASCII Characters in Install Directory Will Cause Run-Time