Version Readme

(1)

IBM Cognos 8 Business Intelligence

PowerPlay

Version 8.4.1

(2)

This document applies to IBM Cognos 8 Version 8.4.1 and may also apply to subsequent releases. To check for newer versions of this document, visit the IBM Cognos Information Centers (http://publib.boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsp).

Copyright

Licensed Materials - Property of IBM © Copyright IBM Corp. 2005, 2010.

US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

IBM, the IBM logo, ibm.com, and Cognos are trademarks or registered trademarks of International Business Machines Corp., in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at www.ibm.com/legal/copytrade.shtml.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

(3)

Chapter 1: IBM Cognos 8 Business Intelligence

PowerPlay Server Readme

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

The documentation included in this release is current as of October 2009.

Review the Readme Updates

Issues that arise after the product is released are provided in the Readme Updates. To find updates to the Readme and product documentation, do the following:

Steps

1. Find your product's Information Center athttp://publib.boulder.ibm.com/infocenter/cogic/ v1r0m0/index.jsp

2. Search or navigate to Readme Updates for your product.

Review the Fix List

The fix list compiles the known issues that were addressed in this release. To find the fix list for your product, do the following:

Steps

1. Go to the Cognos Business Intelligence and Financial Performance Management Support Troubleshoot page athttp://www-01.ibm.com/software/data/cognos/support/troubleshoot.html. 2. Select your Cognos product from the drop-down list.

3. Click Troubleshoot.

4. Enter fix list in the Enter search term box, and click the blue arrow.

Depending on the product and version being accessed, some fix lists are available under the "product documentation" or "fix pack" links in the search results.

Limitations

The following limitations exist for this release.

Installation and Configuration Limitations

The following limitations affect the installation or configuration of IBM Cognos 8 PowerPlay.

(6)

Installing IBM Cognos 8 PowerPlay With IBM Cognos 8

In a distributed IBM Cognos 8 environment, you must install PowerPlay components on all com-puters. If the IBM Cognos 8 environment uses a computer with an operating system that is not supported for IBM Cognos 8 PowerPlay then IBM Cognos 8 PowerPlay Server is not supported in this environment.

For example, if you have IBM Cognos 8 BI Server application tier components installed on both an HP Itanium server and on a Windows server, you can not install IBM Cognos 8 PowerPlay into this environment.

To review an up-to-date list of environments supported by IBM Cognos products, such as operating systems, patches, browsers, Web servers, directory servers, database servers, and application servers, visit the IBM Cognos Resource Center (http://www.ibm.com/software/data/support/cognos_crc. html).

nba

PowerPlay Limitations

Administration

● Command line administration options are not supported.

Data Sources

● Like IBM Cognos Series 7, for PowerPlay Client we recommend that you use cubes on the same operating system and with the same encoding as used for building the cube.

● IBM Cognos PowerCubes are the only supported data source. 3rd party OLAP data sources are not supported.

IBM Cognos 8 Features

● Integration with IBM Cognos Go! components is not complete. ● Watch rules are not supported for PowerPlay reports.

Samples

● Sample cubes and reports are available on the IBM Cognos 8 Business Intelligence Samples CD.

Migration Limitations

Source Content

(7)

Drill Through Limitations

The IBM Cognos 8 PowerPlay Readme included with the product installation listed drill through limitations that were removed for the current release. The following is an updated list of drill through limitations.

Transformer

● Drill through targets that use non-English character sets are not supported.

Dynamic Filtering

● Drill through with dynamic filtering to reports created in Analysis Studio is not supported.

Installation and Configuration Known Issues

The following known issues exist for installation and configuration.

Error After Installing PowerPlay Administration With Existing PowerPlay Server

Installation

When you install PowerPlay Administration on top of an existing PowerPlay Server installation, and then click on the PowerPlay tab in IBM Cognos Administration, the following error may appear Unable to process the document, the target is not valid or the target was not received.

To access PowerPlay Administration, you must uninstall and reinstall PowerPlay Server including the PowerPlay Administration component. We recommended that you back up important files to ensure no data is lost during the reinstallation process. For more information about backing up files, see the IBM Cognos 8 PowerPlay Installation and Configuration Guide.

595925

Migration Known Issues

The following known issues exist for migration.

Migration Task Shows Error when Upfront not Installed

When migrating content from PowerPlay Enterprise Server or IBM Cognos Connection, the following error appears in the migration task when Upfront is not installed.

Cannot parse csx file.

The error occurs because the migration service looks for a provider of type "upfront" in the

S7_install/bin/cer5.csx file.

To resolve the problem, install Upfront or create an entry in the cer5.csx file for a dummy Upfront provider.

Steps to Create an Entry for Upfront in the cer5.csx File

1. Start IBM Cognos Configuration Manager.

Readme 7 Chapter 1: IBM Cognos 8 Business Intelligence PowerPlay Server Readme

(8)

2. Click the Server Configuration tab and then click All Server Groups.

3. From the Actions menu, click Add Server Group and select Upfront from the drop down list. 4. In the Configuration Manager toolbar, click the Create the server configuration (cer5.csx) file

button.

45561

Migrating a Report with a Single Measure on X or Y Axis Does not Run in Report

Studio

When migrating a PowerPlay Web or PowerPlay Studio report that has a single measure on the x or y axis to Report Studio, the report is not valid and does not run. The following error appears:

RSV-VAL-0003 Unable to find the item <measure name>_Summary in the query <query name>.

In Report Studio, a new node <measure name>_Summary is created in the crosstab. A red x appears on the node indicating a problem.

To resolve the problem, delete the new node from the report.

136043

Folders in Upfront Personal NewsBox not Migrated

Folders and their content that are in an Upfront personal NewsBox are not migrated if they were created by cutting and pasting folders from the Public folder. When the migration task is complete, no error is logged indicating that the folders were not migrated.

To work around the problem, copy the folders instead of cutting and pasting them. After the folders are copied, delete the original folders if they are no longer needed.

131160

Migration Error when Using Server Groups in an IBM Cognos 8 Distributed

Environment

When server groups are used in an IBM Cognos 8 distributed environment and you try to execute a migration task or open a report in Analysis Studio or Report Studio, the following error occurs:

DPR-ERR-2014

Unable to load balance the request because no nodes in the cluster are available, or no nodes are configured for the service: migrationService.

To work around the problem, do not use server groups.

(9)

Ranking Applied to an Axis having a Custom Subset and One or More Categories

not Migrated to Analysis Studio

Ranking applied to an axis having a custom subset and one or more categories, even if the categories are from the same dimension, is not migrated to Analysis Studio. After migration, the rank cells are empty for the subset.

To work around the problem, do one of the following: ● Migrate the report to Report Studio instead.

● In the original report, leave only the custom subset on the axis and remove the other categories.

121214

Cube Mapping Error when Using Asian characters in the Migration Target Folder

In the Migration Assistant, when you specify a target destination location for the migrated content that contains Asian characters in the folder name, proceed to the cube mapping screen and then click on the Select a package link in the Actions column, the following error message appear:

CM-REQ-4158 The search path "/content/folder[@name='xxx" is invalid. Details:

CM-REQ-4098 The syntax of the search path is incorrect. The search path predicate is invalid because the closing square bracket (]) character is missing.

xxx is a garbled version of the target folder you had selected. You can avoid this problem by doing one of the following:

● Use Firefox as your Web browser instead of Internet Explorer.

● Before clicking the Select a Package link, click the Back button and then the Next button. ● Migrate the content to the Public Folders first and then move it to the desired location.

123060

Error Migrating a PowerPlay Report Containing a Custom Subset with a Moveable

Calculation

If a PowerPlay report contains a custom subset with a moveable calculation, an error occurs when you try to migrate the report to Analysis Studio using the Open Report in Analysis Studio command. The following message appears:

RSV-SRV-0040: An application error has occurred. Contact your Administrator. Details: CCLRuntimeError:0:Fatal: the parent <member> doesn't have childrenRSV

This problem occurs with IBM Cognos 8 PowerPlay Studio reports and IBM Cognos Series 7 PowerPlay Web reports that were migrated to IBM Cognos 8 PowerPlay.

To work around the problem, do one of the following: ● Migrate the report to Report Studio instead. ● Make the calculation a non-moveable calculation.

(10)

122816

Upfront Report Created Using the Save As Command in PowerPlay Web Fails to

Run After Migration

An IBM Cognos Series 7 MR3 PowerPlay report that is created using the Save As command in PowerPlay Web fails to run after migration. The following error appears in the migration task history:

MGD-msg-0479 Cube mapping entry was not found for the following source mapping: <cube name>

This causes an error in the migration task and, although the report appears in the Cube Mapping page of the Migration Assistant and you can migrate it, the report does not run because the package link is unavailable. This is because the Upfront data source information points to the original report instead of to the data source. The Upfront data source information for the original report published from PowerPlay Enterprise Server correctly points to the data source.

To work around the problem, do one of the following: ● Upgrade to IBM Cognos Series 7 MR4.

● Include the original report in the migration task.

● In IBM Cognos Connection, click the Set properties button for the report and set the package link to the correct package.

128856

Empty Folder Named "cubes" Created After Migrating from IBM Cognos

Connec-tion

After performing a migration with IBM Cognos Connection as the migration source, an empty folder named "cubes" is created in the migrated content location. Objects are migrated successfully and the package related to cube references was migrated to the PowerPlay folder.

You can safely remove the empty folder.

11184

Starting the Series 7 Migration Service Returns an Error

Starting the IBM Cognos Series 7 migration service returns an error message. If the migration service is started from Windows Services, the following message appears:

The IBM Cognos Series 7 Migration Services on Local Computer started and then stopped.

If the migration service is started by running themigs7service_config -configcommand, the

following error message appears:

Failed to load csx file.

(11)

To resolve the problem, create the cer5.csx file by reapplying the configuration setting.

Steps to Reapply the Configuration Setting

1. In Configuration Manager, open the current configuration. 2. In the Components tab, select the root node.

3. From the Actions menu, click Apply Selection.

4. If the cer5.csx file is not created in the bin directory, reinstall PowerPlay Enterprise Server. 5. Start the Series 7 migration service.

141006

Unable to Run PowerPlay Studio Report Opened in Report Studio

When running a PowerPlay Studio that was opened in Report Studio using the Open with Report Studio command, an error like the following appears:

OP-ERR-0182 Invalid parameter '[T2549(non zero-suppressed on row)]' provided for 'filter' at position '1' for 'dataItem="T2549(zero-suppressed on row)"'.

This problem occurs when a parameter in a data item expression is of numeric type but the expected type is memberset. This may occur if the report contains a calculation to which zero suppression was applied.

To resolve the problem, in Report Studio, change the parameter's type from numeric to memberset. For example, the first parameter in the following expression is of numeric type.

filter([T2549(non zero-suppressed on row)],((tuple([cubes/0406Great Outdoors].[Years].[Years]. [Years]->:[PC].[@MEMBER].[CONVERSION_DATE]) <> 0) and (tuple([cubes/0406Great Outdoors].[Years].[Years].[Years]->:[PC].[@MEMBER].[CONVERSION_DATE]) is not null))) Changing the first parameter to the following changes its type to memberset.

member([T2549(non zero-suppressed on row)],'','',hierarchy([cubes/0406Great Outdoors]. [Locations].[Locations]))

92958

Custom Views and Shortcuts Migrated from Personal NewsBox Appear as Broken

Links

When migrating custom views and shortcuts from a personal NewsBox that were created from objects that are also located in a personal NewsBox, they appear as broken links in IBM Cognos Connection.

To resolve the problem, move the source objects to a public NewsBox, keeping the custom views and shortcuts in the personal NewsBox. When you migrate the contents of the public NewsBox and the personal NewsBox, custom views and shortcuts are successfully migrated.

Note: For custom views, ensure that you include the cubes that the reports reference in the migration task.

(12)

51038

Custom View Migrated a Second Time Appears as a Broken Link

When migrating the same custom view of a report a second time, the link is broken in IBM Cognos Connection.

To resolve the problem, do one of the following:

● Remove the migrated reports from the first migration and redo the migration.

● Use cut and paste to move the migrated reports to a new folder and redo the migration.

65396

Migration Errors when Cube or Folder Name Contains Certain Japanese Characters

When migrating a report that references a cube whose name is the Japanese Shift-JIS codepoint 0x8150, 0x815C, 0x815F, 0x8160, 0x8161, 0x817C, 0x818F, 0x8191, 0x8192, or 0x81CA, you may encounter the following error messages:

MGD-msg-0482 Unable to create the following path in IBM Cognos 8: ¢ MGD-msg-0413 The following messages are returned from IBM Cognos 8:

MGD-msg-0480 Invalid cube mapping. The target path does not exist or cannot be created. Source: /cubes/Japanese/¢/¢, target location: /content/folder[@name="??????"]/folder[@name="PowerPlay"]/ folder[@name="cubes"]/folder[@name="Japanese"]/folder[@name="¢"

where "??????" represents "Migrated Content" in Japanese.

In the last error message above, a folder already exists that is similar to the target path that could not be created. The existing folder is named U+FFE0 (full-width cent sign), and the migration task is attempting to create a folder named U+00A2 (cent sign). Both are potential Unicode renderings of the Shift-JIS codepoint 0x8191.

To resolve the problem, rename or delete the existing folder with the similar name and redo migration.

112792

Error Message not Clear when Migrating Upfront Content from a Series 7

Dis-tributed Installation Environment

When migrating Upfront content from a Series 7 environment where PowerPlay Enterprise Server services and Upfront services are on two different computers, the migration fails if the PowerPlay Enterprise Server services are stopped. The following error message appears:

MGD-msg-0440 A communication error has occurred with <host name> on port <port number>. Verify that the Series 7 migration server name and port number are correct.

The error message does not clearly indicate that the PowerPlay Enterprise Server could not be contacted.

(13)

"Bad Address" Error Appears in Migration Assistant on AIX

When running the Migration Assistant on AIX, one of the following error messages appears:

Bad Address

A memory address is not in the address space for the process.

To resolve the problem, obtain and install the fileset for APAR IY76141 on the Series 7 server. Then reboot your computer.

95582

Scheduled Migration Tasks Fail with Communication Error

When more than one migration task is scheduled to run at the same time, one task fails. The follow-ing error appears in the failed task's run history details:

MGD-msg-0440 A communication error occurred with host <host name> on port <port number>. Verify that the Series 7 migration server name and port number are correct.

To work around the problem, schedule the migration tasks to run in sequence.

111986

Problems Migrating Reports with Internal Path Names Exceeding 255 Characters

When migrating Upfront content, if the number of characters used for the folder name and report name exceeds 255 characters, the migration fails. Errors such as the following appear:

S7S-err-0813 Exception encountered parsing IBM Cognos Deployment Manager errors and warning from file: UNEXPECTED INTERNAL ERROR: CDM dump is missing the "PPES.packletLoca-tion" property.

S7S-err-0646 Exception caught: ./migratetoc8 --servicemode --userootastarget --acl 2 -N "S7_namespace_id" --rendition "/S7_install/cognos/cer5/bin" -U administrator /tmp/

m20080930T11342535210/cdm/a/d/d.dmp "/tmp/m20080930T11342535210/migs7Out" >> "/ tmp/m20080930T11342535210/log.txt" 2>&1 ==> 256: requestprocess.py: 383 (doMigration) requestprocess.py: 1485 (callMigratetoc8Cmd) migs7serviceutils.py: 239 (executeExternalCommand)

On UNIX, PowerPlay Enterprise Server may also generate a core file in the S7_install/bin/ directory. When path names exceed 255 bytes in length, the IBM Cognos Series 7 PowerPlay Enterprise Server process may overflow a buffer. In particular, you may want to check the length of your paths in the PPSRoot directory. For example, S7_install/ppserver/PPSRoot/...

This problem occurs

● on UNIX and Windows systems

UNIX usually permits path names of 1023 or more bytes. Windows limits path names to 260 bytes.

● when using a multi-byte language such as Japanese

A single character can occupy two or more bytes. Consequently, path names can reach the 255 byte limit with fewer characters.

(14)

To work around the problem, select to migrate only NewsBoxes containing reports with path names that are less than 255 characters in length and report file folders that are less than 248 bytes. Or rename the report and NewsBox names so that they use less than 255 bytes, republish to Upfront, and redo the migration.

45144, 116542

Problems Migrating Cubes with non-ASCII Characters on UNIX

If the IBM Cognos Series 7 PPES service is using a non-ASCII path name to access a PowerCube and the IBM Cognos 8 server is running in a locale that uses a different character set, then the IBM Cognos 8 server is unable to locate the referenced PowerCube on disk. For example, the PPES service is using a Japanese name encoded in Shift-JIS using the Solaris locale ja_JP.PCK and the IBM Cog-nos 8 server is running in the locale ja_JP.UTF-8. As a result, the migration of reports that depend on the PowerCube fails with error messages like the following:

MGD-msg-0424 IBM Cognos 8 is unable to create the following data source: cubes/Japanese/ <Japanese characters>

MGD-msg-0422 MigDeploy Exception: MGD-msg-0432 Invalid data source parameters. The path to the physical cube is not specified.

The procedure to work around the problem depends on whether you want to use the same or dif-ferent locale setting in IBM Cognos 8 as in IBM Cognos Series 7.

If you want to use the same locale setting in IBM Cognos 8 as in Series 7, set language environment variables to match those used when starting Series 7 PPES.

Steps to Set Language Environment Variables

1. Set the LANG, LC_ALL, and if applicable, LC_CTYPE environment variables to match those that were used when starting IBM Cognos Series 7 PPES.

For example, LANG= ja_JP.UTF-8. 2. Launch c8_install/bin/cogconfig.sh. 3. Restart the IBM Cognos 8 service. 4. Redo the migration.

If you want to use a different locale setting in IBM Cognos 8, make a copy of the PowerCube under the locale's encoding. Note that you will probably need to use a custom shell or other file-copy utility because entering file names using two separate encodings at a shell command prompt may not work.

Steps to Copy the PowerCube Under a Locale's Encoding

1. Copy the PowerCube .mdc file on disk from its name under the old locale's encoding to its new name under the new locale's encoding.

(15)

to the new filename

"…/cubes/Japanese/\xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e\xe3\x81\xae\xe3\x82\xad\xe3\x83\ xa5\xe3\x83\x96.mdc"

2. Redo the migration.

109388

Unable to Migrate Reports on UNIX when Path Names Contain Certain European

Characters

An error occurs when migrating reports with path names that contain certain European characters on UNIX. The error occurs when the migration source is IBM Cognos Connection, and the reports were published to IBM Cognos 8 in the following way:

1. The source PPX reports are created under the Windows-1252 encoding.

2. The reports are transferred, using FTP, to UNIX running in the French locale fr_FR.8859-15 or the German locale de_DE.8859.15.

3. In one of the locales in the previous step, the PPES service is started. 4. The reports are inserted in PPES and then published to IBM Cognos 8.

The migration error occurs if the path name contains one of the following characters: ● 0xA4 (euro symbol)

● 0xA6 (S caron) ● 0xA8 (s caron) ● 0xB4 (Z caron) ● 0xB8 (z caron) ● 0xBC (OE) ● 0xBD (oe) ● 0xBE (Y umlaut)

An error message like the one below appears in the run history details or the migration log:

S7S-err-0646 Exception caught: …… 93 (__privateGetProperty) ppes_bridge.py: 72 (__privateEncode) /dap …./lib/python2.5/encodings/iso8859_15.py: 12 (encode)

To work around the problem, open the PPX report in a text editor and modify the encoding from Windows-1252 to the same encoding used by the PPES service. For example, change the encoding to ISO-8859-15.

114371

(16)

Missing Brackets in Bookmark Conversion Utility Script Function

In the Migration and Administration Guide, topic Run the Bookmark Utility as a Server, the code mentioned in step 5 of Steps to Allow Users to Change Bookmarks to IBM Cognos 8 is missing two brackets. As a result, the code will not execute properly.

Use the following code instead:

function custom1() {

var tparent = self.window;

if (typeof(topparent) == "undefined"){ tparent = parent;

} else {

tparent = topparent; }

var bkmURL = tparent.location.href; var bkmCGIURL = "<bookmarkcgi URL>";

if (bkmURL.indexOf('?') != -1)

bkmCGIURL += bkmURL.substr(bkmURL.indexOf('?')); tparent.location.href = bkmCGIURL;

}

PowerPlay Known Issues

The following known issues exist for PowerPlay.

Report Viewed from Output Versions List Always Opens in Cognos Viewer

When you view a saved PowerPlay report output version, it will always open in Cognos Viewer, even if the properties are set to PowerPlay Studio Viewer.

To view the report in PowerPlay Studio Report Viewer, run the report interactively from the IBM Cognos Connection folder using Run with options.

609597

Continuous Prompting for Data Source Selection When Running a PowerPlay

Report

A report author can create a report based on a package that uses more than one PowerCube data source connection. When you run this type of report using the Run in the background option from the advanced Run with options, you will repeatedly be prompted to select a data source and you will not be able to run or cancel the report.

You must end your browser session to cancel the attempt to run the report.

606173

Error When an Agent Runs a PowerPlay Report

If you have not been authenticated to the appropriate namespace prior to running the agent that runs a PowerPlay report based on a package with a secured data source, you will be prompted for

(17)

RSV-SRV-0042 Trace back:RSReportService.cpp(791): RSException: CCL_CAUGHT: Service::process()RSReportServiceMethod.cpp(239): RSException: CCL_RETHROW: RSReport-ServiceMethod::process(): asynchWait_RequestRSReportServiceHelper.cpp(831): RSException: CCL_THROW: RSReportServiceHelper::absoluteAffinityError()

To run the report without errors, log on to the appropriate namespace before you run the agent.

605964

Report Output Versions are not Accessible from View Run History for PowerPlay

Reports

After a PowerPlay report is run and the output saved, the View run history option is available on the Perform an action page. However, unlike output for other IBM Cognos 8 studios, you can not access Report outputs or Options from the View run history details page.

You can access saved report outputs using the View report output versions option.

598000

PowerPlay Administration Activities Do Not Appear in the PowerPlay Audit Logs

PowerPlay administrative activities, such as adding or removing cubes, are no longer logged to the PowerPlay audit log files or to the PowerPlay tables in the IBM Cognos 8 audit database. These actions are now performed outside of PowerPlay administration and written to the cogipf_action table in the IBM Cognos 8 audit database.

591326

Error When Running a PowerPlay Report View with Options

If you chose both the Save the report and Prompt for values run options for a PowerPlay Report View, you will receive the following error when you run the report.

Failed to load the pluggable shared library.

This error occurs even if the report does not use prompts.

To prevent this error, do not select the Prompt for values run option.

610576

Filters Are Not Applied When You Drill Through to a Report Based on a Different

Secured Cube

When you drill through to a report based on a different secured PowerCube filters are not applied as expected if you are not logged on to the appropriate namespace before you use the drill through option. This problem occurs even after you provide the required credentials when prompted by the drill through process. This situation applies when the drill through source uses an unsecured Pow-erCube or a PowPow-erCube secured to a different namespace than the drill through source.

To ensure that the correct filters are applied in the drill through target, log on to the appropriate namespace using the Log On link in the main header before you use the drill through option.

611320

(18)

Connection Error When PowerCube File Name Includes Simplified Chinese

Characters

When IBM Cognos 8 PowerPlay is installed on an IBM AIX computer, you may encounter the following error when connecting to a PowerCube that has Simplified Chinese characters in the file name. The error can occur when testing the data source connection or when opening a package based on the PowerCube.

The cube was not opened successfully.

PDS-PPE-0084 No error message is available. {0}ppdsweb/source/CExecCrosstab.cpp(1313): CPPWebException: CCL_THROW: CExecCrosstab::Execute

To prevent this error, rename the cube to use English characters, and remove native characters from the cube name. Another option is to use UTF-8 characters for Simplified Chinese (GB2312) code points when you create the data source connection. These characters will appear incorrectly in Cognos Connection, however, the connection will work correctly.

611994

Audit Database Scripts for IBM Series 7 Style Logging

The Set Up an Audit Database topic in the IBM Cognos 8 PowerPlay Migration and Administration

Guide shows the wrong installation location for the scripts you use to create the audit database for

IBM Cognos Series 7 style logging. The correct location is c8 location\ppserver\schemas.

n/a

Cognos Application Firewall Error When Saving a PowerPlay Studio Report

If your IBM Cognos 8 installation uses the Cognos Content Database you will receive the following error when you attempt to save a PowerPlay Studio report.

An error has occurred.

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.

To prevent this error use a different supported database for the IBM Cognos 8 content store.

616079

Customize the Appearance of IBM Cognos BI

The following provides updated instructions for creating a custom style in IBM Cognos BI PowerPlay. This information replaces the Customize the Appearance of IBM Cognos BI topic in the PowerPlay

Migration and Administration Guide.

You can customize the IBM Cognos BI interface to suit the needs of an international customer or a particular reseller. You can make changes to colors, fonts, images, and overall appearance of one or more IBM Cognos BI components. For more information, see the IBM Cognos BI Administration

(19)

One of the customization options you can use is creating custom styles. We recommend that you use the existing style resources as a starting point: business, classic, contemporary, modern, or presentation. For more information about the existing styles, see the IBM Cognos BI Administration

and Security Guide. Change style sheets, graphics, and fonts as required, but ensure that the structure

of the new custom style directory matches the structure of the predefined styles directories. To create a custom style for IBM Cognos PowerPlay you work with three folder locations. You must ensure that these folders have the files required to support the custom style.

To create a custom style for IBM Cognos PowerPlay, use the following steps instead of the Create

a Custom Style procedure in IBM Cognos BI Administration and Security Guide.

Steps

1. In the c8_location/webcontent/skins directory, make a copy of an existing style directory and rename the copied directory.

For example, make a copy of business and rename the copy business_v2.

2. In the following directories, repeat the copying and renaming process, using an original folder with the same name as step 1 as the source for the new directory.

● c8_location/ppserver/skins

● c8_location/webcontent/fragments/ppesAdmin/css/skins

Continuing the example, all three directories now have a new directory named business_v2. 3. In the new c8_location/webcontent/skins directory, modify the style sheets, graphics, or fonts

as required.

4. In IBM Cognos Administration, add a new style object and associate it with the style directory created in step 1.

Error When Clicking the Return Button After Drilling Through to a PowerPlay

Report

In PowerPlay Studio, if you drill through to a report that was created in PowerPlay Client and then attempt to use the Return button to go back to PowerPlay Studio, you may receive the following error in the drill-through source page:

ERROR: HTTP Error 403 - Forbidden

The error behavior is different depending on the PDF Rendering Viewer setting in PowerPlay administration.

To prevent this error if the report appears in IBM Cognos Viewer, do one of the following. ● Ensure that default action for the target report is set to Run the report or Open with PowerPlay

Studio. The error will occur if the default action is set to View the most recent report. ● Close the browser window of the target report instead of using the Return button. To prevent the error if the report appears in PowerPlay Studio Report Viewer, click the Home button on the target page to return to the default view in IBM Cognos Connection.

(20)

(21)

Index

A

administration limitations,6

settings may not work,7

auditing

not supported in admiinistration,6

B

bookmark conversion utility script,16

C

CM-REQ-4098,9

CM-REQ-4158,9

cube mapping errors

when using Asian characters in the migration target folder name,9

cubes

report cube mapping limitations,6

custom style creating,18

custom views

appear as broken links when migrated a second time,12

appear as broken links when migrated from personal NewsBoxes,11 D data sources limitations,6 DPR-ERR-2014,8 drill through

administration settings may not work,7

limitations,7

drill-through

error when returning to source,19

dynamic filtering

E

error

drill through,19

error message

Cannot parse CSX file,7

RSV-VAL-0003,8

F

failed to load csx file troubleshooting,10

fix list,5

H

HTTP Error 404

returning to drill-through source,19

I

IBM Cognos 8 distributed environments

migration error when server groups are used,8

IBM Cognos 8 Transformer

IBM Cognos Connection

empty folder named ubes created after migration,10

installation and configuration limitations,5

interface

customizing,18

J

Japanese characters

troubleshooting migration problems with cube or folder names,12

L

limitations,5

logging

not supported in admiinistration,6

M

MGD-msg-0413,12

(22)

MGD-msg-0422,14 MGD-msg-0424,14 MGD-msg-0440,12, 13 MGD-msg-0479,10 MGD-msg-0480,12 MGD-msg-0482,12 migration

Cannot parse CSX error,7

cube mapping errors when using Asian characters in the target folder name,9

custom views migrated a second time appear as broken links,12

custom views migrated from personal NewsBoxes appear as broken links,11

empty folder named ubescreated,10

errors when cube or folder names contain certain Japanese characters,12

errors when using server groups in IBM Cognos 8 distributed environment,8

error when migrating reports containing custom subsets with moveable calculations,9

error when migrating Upfront content from a Series 7 distributed environment,12

folders in Upfront personal NewsBox not migrated,8

known issues,7

limitations,6

memory address error appears in Migration Assistant on AIX,13

migrating cubes with non-ASCII characters on AIX,14

problems migrating reports with long names,13

ranks not migrated to Analysis Studio when applied to axis with custom subset and one or more cate-gories,9

reports created using Saved As command do not run,10

tasks scheduled to run at same time fail,13

unable to migrate reports on UNIX when path names contain certain European characters,15

unable to run report with a single measure in Report Studio,8

O

OP-ERR-0182,11

P

PowerPlay reports

running in Report Studio returns error,11

R

ranking

not migrated to Analysis Studio when applied to axis with custom subset and one or more cate-gories,9 readme updates,5 RSV-SRV-0040,9 S S7S-err-0646,13, 15 S7S-err-0813,13 samples limitations,6

Series 7 distributed environment

migration error when PPES services are stopped,12

Series 7 migration service error when starting,10

style

creating custom,18

T

troubleshooting

bookmark conversion utility script,16

custom views migrated a second time appear as broken links,12

custom views migrated from personal NewsBoxes appear as broken links,11

empty folder named ubescreated after migration,10

error when migrating Upfront content from a Series 7 distributed environment,12

error when starting Series 7 migration service,10

memory address error appears in Migration Assistant on AIX,13

migrating cubes with non-ASCIII characters on AIX,14

migrating reports containing custom subsets with moveable calculations,9

(23)

running PowerPlay report opened in Report Studio returns error,11

scheduled migration tasks fail,13

unable to migrate reports on UNIX when path names contain certain European characters,15

U

Upfront

folders in personal NewsBox not migrated,8

Upfront reports

created using Save As command fail to run after migration,10

Readme 23 Index

Version Readme

IBM Cognos 8 Business Intelligence

PowerPlay

Table of Contents

Chapter 1: IBM Cognos 8 Business Intelligence

PowerPlay Server Readme

Review the Readme Updates

Review the Fix List

Limitations

Installation and Configuration Limitations

PowerPlay Limitations

Migration Limitations

Drill Through Limitations

Installation and Configuration Known Issues

Error After Installing PowerPlay Administration With Existing PowerPlay Server

Installation

Migration Known Issues

Migration Task Shows Error when Upfront not Installed

Migrating a Report with a Single Measure on X or Y Axis Does not Run in Report

Studio

Folders in Upfront Personal NewsBox not Migrated

Migration Error when Using Server Groups in an IBM Cognos 8 Distributed

Environment

Ranking Applied to an Axis having a Custom Subset and One or More Categories

not Migrated to Analysis Studio

Cube Mapping Error when Using Asian characters in the Migration Target Folder

Error Migrating a PowerPlay Report Containing a Custom Subset with a Moveable

Calculation

Upfront Report Created Using the Save As Command in PowerPlay Web Fails to

Run After Migration

Empty Folder Named "cubes" Created After Migrating from IBM Cognos

Connec-tion

Starting the Series 7 Migration Service Returns an Error

Unable to Run PowerPlay Studio Report Opened in Report Studio

Custom Views and Shortcuts Migrated from Personal NewsBox Appear as Broken

Links

Custom View Migrated a Second Time Appears as a Broken Link

Migration Errors when Cube or Folder Name Contains Certain Japanese Characters

Error Message not Clear when Migrating Upfront Content from a Series 7

Dis-tributed Installation Environment

"Bad Address" Error Appears in Migration Assistant on AIX

Scheduled Migration Tasks Fail with Communication Error

Problems Migrating Reports with Internal Path Names Exceeding 255 Characters

Problems Migrating Cubes with non-ASCII Characters on UNIX

Unable to Migrate Reports on UNIX when Path Names Contain Certain European

Characters

Missing Brackets in Bookmark Conversion Utility Script Function

PowerPlay Known Issues

Report Viewed from Output Versions List Always Opens in Cognos Viewer

Continuous Prompting for Data Source Selection When Running a PowerPlay

Report

Error When an Agent Runs a PowerPlay Report

Report Output Versions are not Accessible from View Run History for PowerPlay

Reports

PowerPlay Administration Activities Do Not Appear in the PowerPlay Audit Logs

Error When Running a PowerPlay Report View with Options

Filters Are Not Applied When You Drill Through to a Report Based on a Different

Secured Cube

Connection Error When PowerCube File Name Includes Simplified Chinese

Characters

Audit Database Scripts for IBM Series 7 Style Logging

Cognos Application Firewall Error When Saving a PowerPlay Studio Report

Customize the Appearance of IBM Cognos BI

Error When Clicking the Return Button After Drilling Through to a PowerPlay

Report

Index