Planning Release NotesVersion 10.1.0
Release Notes
Product Information This document applies to IBM Cognos Planning
Version 10.1.0 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. 1999, 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, ReportNet, 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. UNIX is a registered
trademark of The Open Group in the United States and other
countries.
Table of Contents
Chapter 1: Release Notes Updates By Date 5 Updated: October 18,
2010 5
Installation and Configuration 5 IBM Cognos Planning Analyst 5 IBM
Cognos Planning Contributor 5
Chapter 2: IBM Cognos Planning Release Notes 7 System requirements
7 Installing the product 7 Fix list 7 Open APARs 7 Known IBM Cognos
Planning problems 8
Installation and configuration 8 Known Administration Issues 10
Security 11 General 11 IBM Cognos Planning Analyst 12 IBM Cognos
Planning Contributor 13 IBM Cognos Planning data service 20
Internationalization 21
Known IBM Cognos Business Intelligence problems 21 General
documentation problems 21
Chapter 3: Deprecation notices 23 Supported environments 23 Product
features 23
Index 25
Licensed Materials – Property of IBM 3© Copyright IBM Corp. 1999,
2010.
4
Chapter 1: Release Notes Updates By Date
This section contains cross references to known issues and
documentation updates that were made
after October 17, 2010.
Updated: October 18, 2010 The following Release Notes updates were
made on October 18, 2010
Installation and Configuration Added - "Upgrading ContributorWeb
Client versions 8.4 or 8.4.1 to version 10.1 onWindows
7 operating system fails" (p. 8)
IBM Cognos Planning Analyst Added - "Japanese and Korean characters
in Planning Analyst group or role names not imported
correctly" (p. 12)
IBM Cognos Planning Contributor Added - "Documentation update
regarding the Export to Microsoft Excel Wizard" (p. 13)
Added - "Data fromMicrosoft Excel not imported into Planning
ContributorWeb Client when
using Local Links" (p. 14)
Added - "Framework Manager models with member-based hierarchies
fail validation with a
determinant error" (p. 14)
Added - "Links from FrameworkManager sources fail when using a DB2
database and a column
that contains textual data" (p. 15)
Added - "Items which are "no data" in access tables show in pages
list in grid" (p. 15)
Licensed Materials – Property of IBM 5© Copyright IBM Corp. 1999,
2010.
6
Chapter 1: Release Notes Updates By Date
Chapter 2: IBM Cognos Planning Release Notes
This document provides a list of known problems, useful topics, and
links for when you install
IBM® Cognos® Planning.
For the latest version of this document, see the Information Center
for this product at http://publib.
boulder.ibm.com/infocenter/cogic/v1r0m0/index.jsp.
guides at
http://publib.boulder.ibm.com/infocenter/cfpm/v10r1m0/
Installing the product For instructions on how to install the
product, see the installation and configuration guides at
http:
//publib.boulder.ibm.com/infocenter/cfpm/v10r1m0/
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 at
http://www-947.ibm.com/support/entry/portal/Troubleshooting/Software/
Information_Management/Cognos_Business_Intelligence_and_Financial_Performance_
Management
2. Enter your search parameters in the Search support box, and
click the blue arrow.
Depending on the product and version being accessed, fix lists
might be available under "fix list",
"product documentation", or "fix pack" links in the search
results.
Open APARs You can track problems that are discovered and reported
to IBM as a result of a product defect.
These APARs (Authorized Program Analysis Reports) remain open until
a fix is available.
A list of all open APARs is available from the following Web
site:
http://www-01.ibm.com/support/search.wss?rs=0&lang=&loc=en&r=10&cs=utf-
8&rankfile=0&cc=&coll=0&spc=&stc=&apar=only&q1=%2Bopen&sort=rk&tc=SWQ20&ibm-
search.x=19&ibm-search.y=10&ibm-search=Search&dc=DB550&dtm
Licensed Materials – Property of IBM 7© Copyright IBM Corp. 1999,
2010.
This section contains IBM® Cognos® Planning issues.
Installation and configuration This section contains known issues
about installation and configuration.
Creating and configuring a planning store
It is now mandatory to create and configure a planning store for
your IBM® Cognos® Planning
environment. You can connect to your planning store using IBM
Cognos Configuration.
When you use a DB2® database for your content store you must
configure, set, and test the content
store before setting up the planning store.
Upgrading ContributorWeb Client versions 8.4 or 8.4.1 to version
10.1 onWindows 7 operating system fails
If a computer running the Microsoft Windows 7 operating system has
Contributor Web Client
versions 8.4 or 8.4.1 installed, upgrading the Contributor Web
Client to version 10.1 fails.If a
computer is upgraded to Windows 7 after Contributor Web Client
version 10.1 has been installed,
Contributor Web Client will continue to work.
To upgrade to Contributor Web Client version 10.1 if you deploy
Contributor Web Client with
the push method using a script, change the script. Alter the script
to remove the version 8.4 or 8.4.1
Web Client and to install the version 10.1 Web Client. If planners
also need to access version 8.4
or 8.4.1 of Contributor Web Client, alter the script to re-install
the required version after installing
Contributor Web Client version 10.1.
To upgrade to Contributor Web Client version 10.1 if you use the
pull method, planners must first
manually uninstall the version 8.4 or 8.4.1 client, then pull the
version 10.1 client. If planners also
need to access version 8.4 or 8.4.1 of Contributor Web Client, they
must then reinstall the version
8.4 or 8.4.1 client.
Changes to IBM Cognos service in IBM Cognos Configuration
In earlier releases, you had two options in IBM® Cognos®
Configuration for configuring the maxi-
mum amount of memory for the IBMCognos service. You could adjust
the value for theMaximum
memory in MB property or you could delete the Cognos service and
then select a new service that
used a small, medium, or large configuration template. In IBM
Cognos Planning, Version 10.1.0,
you have the single option of adjusting the value for the Maximum
memory in MB property.
Updates for Microsoft SQL Server connection string
You need to update the epEAdminSQL7Resources.xml file to
accommodate the name of the native
client driver that is used in Microsoft® SQL Server 2008.
This update is required to start the planning service. Youmust
update the epEAdminSQL7Resources.
xml file on each computer that has the IBM® Cognos® Planning server
installed.
8
You can update the epEAdminSQL7Resources.xml file immediately after
installing the planning
server, prior to opening IBM Cognos Configuration.
Please change from this original Resource ID value:
<Resource ID="DefaultProviderDriverString"
Context="Customization" Hint="The default string used in the ADO
connection string that is generated for a new Application.">
<![CDATA[SQLOLEDB or SQLNCLI] ]>
</Resource>
To this new Resource ID value:
<Resource ID="DefaultProviderDriverString"
Context="Customization" Hint="The default string used in the ADO
connection string that is generated for a new Application.">
<![CDATA[SQLNCLI10] ]>
</Resource>
Additional changes required
In addition to the client tools, you need to install the Microsoft®
SQL Server 2005 Backward
Compatibility Components.
Tip: On the Microsoft download Web site, search for SQL Server
Feature Pack, and then sort by
Release Date to find the latest version.
You need to install the followingMicrosoft SQL Server 2005 Backward
Compatibility Component:
SQL Distributed Management Objects (SQL-DMO)
Planning Start menu shortcuts do not work
If you install IBM®Cognos® Planning, and then install the c8BIModel
package in a different location
on your computer, the Microsoft® Start menu shortcuts to the
Planning applications do not work.
To prevent this problem, do one of the following:
Install all IBM Cognos packages in the same location
Specify a different Start menu folder for each IBM Cognos package
that uses a different install
location.
Cannot create network installation point
You cannot create a network installation point from a computer that
already has IBM® Cognos®
Planning installed on it.
To create the network installation point, run the installation from
another computer and specify
the IBM Cognos Planning Analyst UNC Install Location.
Cannot edit macros after upgrade
During an upgrade, if you remove applications from the old Planning
Administration Domain
before you upgrade their corresponding macros, you will not be able
to edit the macros after you
finish the upgrade.
To avoid this problem, do not remove applications from the old
Planning Administration Domain
until you have upgraded the complete Planning Administration
Domain.
Release Notes 9
Chapter 2: IBM Cognos Planning Release Notes
Planning Contributor Users Role with language installs can cause
problems with access to applications
You may experience problems accessing applications if you use a
language install and select the
default user role, Planning Contributor Users. This is because
IBM®Cognos® Planning Administrator
is not available in localized languages.
To solve this problem, create a new role under the Cognos group and
add users to it. In the appli-
cation, assign the right to this new role. The user can then open
the application.
IBM Cognos Connection User Guide appears in English in all language
versions of the product
When the product language in IBM® Cognos® products is set to a
language other than English, the
portal user interface appears correctly in the selected language,
but the IBM Cognos Connection
User Guide appears in English. This is because the translated
version of this document is not included
in the IBM Cognos Planning package.
To solve this problem, install IBM Cognos Supplementary Languages
Documentation Package
version 10.1 to the same location as IBM Cognos Planning. You can
download the installation
package from the IBM Cognos Resource Center Web site
http://www.ibm.com/software/data/support/cognos_crc.html
The IBM Cognos Connection User Guide should now appear in the same
language as the IBM
Cognos product user interface.
Copying Contributor documentation to the UNIX gateway
When you configure an gateway on a computer running a UNIX®
operating system for IBM®
Cognos® Planning, you are no longer required to copy zip files
whose names begin with docplancli-
entinstall.
When you copy the IBM Cognos Planning Contributor documentation to
the UNIX gateway
computer, you only need to copy zip files whose names begin with
doccontribweb and docplan-
ningrdm.
Planning supports 32-Bit IBM Cognos Business Intelligence
installation
IBM®Cognos® Business Intelligence products are now available with
support for 64-bit application
servers. IBM Cognos Planning only supports a 32-bit BI application
server.
You cannot install Planning on the same computer as an existing BI
64-bit installation but you can
have other 64-bit BI computers as part of the environment. For
example, you can use a 64-bit
Content Store.
Known Administration Issues This section contains known issues
about IBM® Cognos® Planning Contributor administration.
Upgrading Microsoft SQL Server client tools for job-server
clusters
Upgrading your planning environment to use Microsoft® SQL Server
2008 client tools involves
setup considerations in order for the job-server clusters in your
IBM®Cognos® Planning environment
to work properly.
can choose one of the following options:
Use the same version of Microsoft SQL Server client tools for each
job-server within a cluster.
Multiple clusters can use different versions. For example, SQL
Server 2005 Cluster A, SQL
Server 2005 Cluster B, and SQL Server 2008 Cluster C. However, as
each job server is upgraded
it must be moved from a SQL Server 2005 job cluster to a SQL Server
2008 job cluster.
Install and use Microsoft SQL Server 2005 and Microsoft SQL Server
2008 client tools for the
entire environment.
Each job-server within a cluster must be able to handle the same
connection type. When you setup
your job-server cluster to monitor applications, publish
containers, or content store, ensure that
the job server can use the connection string. The following table
provides the connection string that
corresponds to the version of SQL Server client tools that are
installed on the job server.
SQL Server Client Tool VersionConnection String
2008SQLNCLI10
2005SQLNCLI
For example, if your application uses the SQLNCLI10 connection
string, then you can assign this
application to a cluster that has SQL Server 2008 client tools
installed on the job server.
Always stage and test your job-server clusters and planning
environment before upgrading to a new
Microsoft SQL Server 2008 production environment.
Note: You should also partition your Web-server clusters in a
similar way, using IBM Cognos
Connection.
CA Siteminder security timeout causes error in Planning
Administrator
In CA Siteminder, you set the maximum timeout and the idle timeout
time durations for a session.
In IBM®Cognos®Connection you set the session timeout to a longer
time.When using IBMCognos
Planning Administrator, after the CA Siteminder timeouts have
occurred, you click an object in the
tree view. An error message is displayed in Planning
Administrator:
"Unable to perform action. Failed to process server response.
Failed to send the SOAP message."
Additionally, Planning Administrator may close unexpectedly.
To work around this problem, ensure that the timeout values that
you set in CA Siteminder are the
same as or greater than those you set in IBM Cognos
Connection.
General This section contains general known issues.
Release Notes 11
There are no general items for this release.
IBM Cognos Planning Analyst This section contains known issues
about IBM® Cognos® Planning Analyst.
Japanese and Korean characters in Planning Analyst group or role
names not imported correctly
If you have Japanese or Korean characters in group or role names,
they will not import correctly
in IBM® Cognos® Planning Analyst when using the Maintain libraries
and users feature.
This problem only occurs for groups and roles. It does not occur if
Japanese or Korean characters
exist in user names. To work around this problem, secure Planning
Analyst using user names instead.
Additional information added to the task "Create a DSN for the
Database Server"
The topic "Create a DSN for the Database Server" is updated as
follows.
Create a DSN for the Database Server
Step 5 contains additional information.
Steps for Oracle
1. In the Microsoft® Windows® Control Panel click Administrative
Tools,Data Sources (ODBC).
2. Click the System DSN tab.
3. Click Add and double-click Oracle native DBMS driver.
4. In Oracle ODBC Driver Configuration screen, provide the
requested information, and leave
the default check box selections.
5. Click Test Connection to check whether the ODBC environment is
configured properly.
It connects to the database specified by the Data Source Name
definition, and you are prompted
for your username and password.
To reduce the risk of spreading malicious content, it is
recommended that you restrict users
who connect to ODBC sources to attaching only the most essential
file types to cubes.
For enhanced security, it is also recommended that users who
connect to ODBC sources do
not have delete privileges.
Sort order is an option on the Import Link tab
You can now choose Sort Order as an option under Location/Sort
Order on the Import Link tab
of d.List options. This option preserves the items in the same
order as they are in the source file.
Object level access rights
If you define object level access rights in IBM® Cognos® Planning
Analyst and then delete users,
groups, or roles that have been granted those rights, the rights
are inherited by the next available
user, group, or role.
Chapter 2: IBM Cognos Planning Release Notes
If you do not want these access rights inherited by the next
available user, group, or role, you must
manually update them.
Publish performance decreases when the Annotation option is
selected
The performance of a publish in IBM® Cognos® Planning Analyst
decreases when the annotation
option is selected, even when there is no actual annotation data to
publish. This applies to both the
Table-only layout and View publish layout options. To improve
performance, clear the Annotation
option.
Table-Only Layout in Publish macro allows no dimension for
publish
When using the "Table-Only Layout" in the Publish macro in IBM®
Cognos® Planning Analyst, if
you do not choose a dimension for publish, then an empty database
(system tables only) is created.
In the case of "View Publish Layout" the publish tables are created
as expected.
Scheduled jobs and macros credentials
Window Integrated Authentication is used to secure scheduled jobs
and macros in IBM® Cognos®
Planning Analyst.
It is possible to run other authentication methods, although you
are prompted for credentials.
Generate Transformer model
IBM® Cognos® Transformer Series 8 must be installed on the
application server in order to create
PowerCubes. The Transformer model can still be created without
Transformer. When publishing
multiple cubes at once, one package is created for each cube.
IBM Cognos Planning Analyst must be secured against a Series 7
namespace because of integration
with Transformer Series 8. The namespace entry in IBM® Cognos®
Configuration must be the same
as the Series 7 namespace name.
Documentation incorrectly identifies that Analyst users must be
part of the Planning Contributor Users Role
A user in IBM® Cognos® Planning Analyst does not have to be a
member of the "Planning Contrib-
utor Users" role in IBM Cognos Connection. Analyst users must be
part of any role that has been
granted rights to be able to login to Analyst.
IBM Cognos Planning Contributor This section contains known issues
about IBM® Cognos® Planning Contributor.
Documentation update regarding the Export to Microsoft Excel
Wizard
The documentation regarding the Export toMicrosoft ExcelWizard
available in the IBM®Cognos®
Planning Contributor Web Client User Guide is updated as follows.
Changes have been made to
the section called "Saved Selections."
Release Notes 13
Saved Selections
Selections are sets of data from an application grouped together to
create specific reports. These
selections can be made up of data from one or more tabs within your
application.
Once selections are created and saved, they are called Saved
Selections and are stored on the server.
From the File menu, click Export to Excel. Choose which selection
option you want to use:
New Selection - creates a new selection of data. You can choose to
Include Annotations,Merge
Cells to merge adjacent cells with the same value into a single
cell, or Run when Finished to run the saved selection immediately
when the export wizard is complete.
To reduce the number of pages in your report, use theMerge Cells
option to stack two or more dimensions into one axis (row or
column). You can stack dimensions to reduce the number of
pages in your report by moving page dimensions to either rows or
columns.
To save a selection for use in another e.List item either by
yourself or others, select Include All for the e.List dimension.
For each dimension that is subject to "no data" access tables so
that
their members vary from elist item to elist item, select Include
All.
Import Selection - imports an existing selection of data. If the
same selection is imported multiple
times, it will not be given a new name by default. When editing an
imported selection, a new
name may be selected.
Edit Selection - changes the structure of an existing selection. If
the saved selection was created
for a different e.List selection and used the Include All option
for the e.List dimension, you may need to edit the selection to
show the required e.List items.
Run Selection - uses a previously saved selection without changing
the structure. If the structure
of a previously saved selection has changed significantly (because
of a model change), that
selection may not be compatible and would need to be
recreated.
Data from Microsoft Excel not imported into Planning Contributor
Web Client when using Local Links
When importing data fromMicrosoft® Excel into IBM® Cognos® Planning
Contributor Web Client
using Local Links, numeric data is not imported if it is formatted
in Excel as Currency or
Accounting.
When importing data from Excel into Planning Contributor Web Client
using Local Links, you
must format data in Excel as General or Numeric.
Framework Manager models with member-based hierarchies fail
validation with a determinant error
After generating an IBM® Cognos® Framework Manager model in IBM
Cognos Planning Contrib-
utor 10.1 and selecting member based hierarchies, the Verify Model
tool in Framework Manager
returns the following error:
BMT-MD-2041 One or more query items are not referenced by a
determinant.
This error is present for each dimension in the Derived Hierarchy
list.This message appears either
when republishing the package generated in FrameworkManager or
verifying the model manually.
The error message does not affect data quality. The data presented
when using the affected query
items is accurate.
Chapter 2: IBM Cognos Planning Release Notes
To not receive the error message, manually modify the determinants
for each query subject affected.
Steps
1. In Framework Manager, open the Query Subject Definition for the
Derived Hierarchy query
item.
2. Select the Determinants tab.
3. Navigate to the lowest level items in the Determinants
section.
4. Select the Uniquely Identified box.
5. Clear the Group by box.
6. Save your changes.
7. Repeat the previous for each affected Derived Hierarchy query
item.
8. Verify the model again.
The errors have been eliminated.
Links from Framework Manager sources fail when using a DB2 database
and a column that contains textual data
If you use an IBM® DB2® database, both admin links and d-links from
IBM Cognos® Framework
Manager sources that contain textual data will fail. Framework
Manager sources with numeric
data only are not affected
To work around this problem, use ODBC or ASCII data sources
instead.
Items which are "no data" in access tables show in pages list in
grid
In Contributor Web Client, in certain circumstances, where access
tables have been used to provide
"no data" security settings for an item, that item will show in the
Pages list in the grid.
This problem occurs if the dimension is in use in full in another
cube, typically an Assumption cube.
This problem will not cause problems with data entry. While the
item appears in the Pages list, you cannot select the item. It will
not appear in rows or columns in the grid.
Microsoft Excel 2007 appears to freeze when using JAWS screen
reader and Planning Contributor Add- in for Microsoft Excel
Microsoft® Excel 2007 may appear to freeze when using it with the
JAWS screen reader and the
IBM® Cognos® Planning Contributor Add-in for Microsoft Excel. When
you enter a userid and
password in the add-in, select an application, and then select a
node, the Excel status bar shows
that annotations are loading but appears to freeze.
To work around this problem, press any key on the keyboard. The
grid will immediately load.
Clarifying expected behavior when the "Validate source data on
import and log errors to file" checkbox is selected or not
selected
If you select the Validate source data on import and log errors to
file checkbox:
Release Notes 15
Chapter 2: IBM Cognos Planning Release Notes
Data is validated as it is imported.
Invalid records are automatically logged to a file
<temp-dir>\rejects<timeStamp>.txt
Because there is no other notification, we recommend that you check
the log file each time to
see if any records were not imported.
The import will continue to import as much as possible even when
errors are logged and will
state 'success' when finished.
The validation of large sets of data can impact on performance of
the import.
If you do not select the Validate source data on import and log
errors to file checkbox:
No validation occurs.
If any invalid records are found during the import, the process
will fail and the user is informed.
No errors are logged.
Because there is no validation and this is the equivalent of a Bulk
Load, the performance of
this import can be faster than with the checkbox selected.
Documentation incorrectly identifies that access rights for an
application are inherited from the access rights set at the
datastore level
Applications do not inherit rights from the Datastore or
Application folder level. The rights still
need to be specified at the lowest level. You must set rights at
the PAD, datastore, Application
folder and application level to allow a user to go-to-production an
application.
In-place upgrade of version 8.2 or 8.3 publish container
fails
A table publish container (publishparameters) contains a new column
called cantrickleupdate in
IBM® Cognos® Planning Analyst versions 8.4 and later. If you do an
in-place upgrade of a version
8.2 or 8.3 application, the publish container is not updated,
therefore the publish can fail.
To solve this problem, add this column manually with the same
parameters as the cantricklerun
column.
Dimension is only available in List View and not in Hierarchical
View
Sometimes a dimension is only available in list view and not in
hierarchical view.
To appear in hierarchical view, a dimension must use a simple
hierarchy. If a dimension contains
Calculation options (Time Average, Weighted Average, Force to Zero)
or alternate roll-ups (where
a child has multiple parents) or is set as a Time dimension, it is
only available in list view, not in
hierarchical view.
Hide All Objects option not supported in Planning Contributor
Add-in for Microsoft Excel
When you select the Hide all objects option in Microsoft® Excel
spreadsheet software, then IBM®
Cognos® Planning Contributor Add-in for Microsoft Excel is unable
to access embedded OLE
objects on the worksheets of the active workbook. This may cause
some of the add-in’s features to
fail, such as enabling a workbook.
16
Chapter 2: IBM Cognos Planning Release Notes
To work around this issue, do not select the Hide all objects
option.
Corrupted characters in BMTReportNet.log file
The BMTReportNet.log file is produced when an error occurs in the
execution of the Generate
FrameworkManagerModel extension wizard. This file is encoded using
UTF-8. To avoid corrupted
characters, use a text editor which supports UTF-8.
Unable to access IBM Cognos Planning Contributor Add-in for
Microsoft Excel after uninstalling Planning Administrator
Users who have both IBM®Cognos® Planning Administrator and
IBMCognos Planning Contributor
Add-in for Microsoft® Excel installed on the same computer may
encounter an error with the add-
in after uninstalling only Planning Administrator. This is caused
by the removal of some components
required by both applications.
To work around this issue, reinstall the add-in.
After running Publish Generate Script, an error message about Out
of Script is displayed when trying to publish
To run the publish process, you must attach the publish container
manually after running Publish
Generate Script.
If you do not manually add the container, an "out of script" error
message is displayed if you
attempt to run publish.
1. Select the desired datastore.
2. Click Create New.
3. Attach the new container.
Error message about the current fetch buffer is displayed when
using Microsoft SQL Server 2005
When using IBMCognos Planning applications hosted onMicrosoft® SQL
Server 2005, the following
error message may be displayed:
There are no rows in the current fetch buffer.
You need to change your Microsoft SQL Server 2005 to Native Client.
You should install SQL
Native Client on each computer that will be processing IBM® Cognos®
Planning applications (job
servers, web servers, admin servers). The installation file,
"sqlncli.msi", is available from the SQL
Server 2005 installation media. For more information, see
http://msdn2.microsoft.com/en-us/library/
ms131321(SQL.90).aspx
When creating connections toMicrosoft SQL Server 2005 computers,
click theAdvanced button
and change the Provider Driver from SQLOLEDB to SQLNCLI.
Release Notes 17
Chapter 2: IBM Cognos Planning Release Notes
You can change the provider driver after creating the data store
server by selecting the datastore
in IBM Cognos Planning Administrator. The updated provider driver
can be cascaded to the
applications in that data store.
IBM Cognos Planning Administrator appears unresponsive
When a user who does not have rights to IBM® Cognos® Planning
Analyst attempts to add the
"Execute Analyst Macro" step to a macro that they are creating, IBM
Cognos Planning Adminis-
trator appears to be unresponsive. This occurs because Planning
Analyst does not allow the user
to view the libraries because the rights assigned to the
user.
Planning Administrator users that need to create macros that
contain the Execute Analyst Macro
step must have rights assigned for Planning Analyst to allow them
access to the libraries.
Administration Links and SAP BW detailed fact query subjects
This applies only to an Administration Link that is sourced from an
IBM® Cognos® package based
on an IBM Cognos Framework Manager model that is using the SAP BW
Detailed Fact Query
Subject. If the Link is configured in such a way that a Query Item
from this Package is left unmapped
and the 'Include All' flag is selected (no explicit members are
selected), then the Link will fail.
The workaround is to leave the Query Subject out of the Link. The
data is still aggregated to the
top level of the hierarchy.
Query fails with error message DM-DBM-0402 because of too little
disk space in Temp directory
When executing administration links that use the Detailed Fact
Query Subject, one of the internal
IBM® Cognos® components builds temporary files in the Temp folder
under the IBM Cognos
installation directory. The temporary files are deleted after the
query completes, but these files can
be large, depending on how much data is being retrieved. If the
drive that contains the Temp folder
does not have enough space to contain the temporary files, the
query will fail and you will receive
the following error in the PlanningErrorLog.csv file:
Error Message: DM-DBM-0402 COGQF driver reported the
following:~~~~COGQF failed to
execute query - check logon / credential path~~~~DM-DBM-0402 COGQF
driver reported the
following:~~~~RQP-DEF-0177 An error occurred while performing
operation '
sqlOpenResult'
status='-28'.~~UDA-SQL-0114 The cursor
supplied to the operation "sqlOpenResult" is
inactive.~~UDA-SOR-0005
Unable to write the file.~~~~~~DM-DBM-0402 COGQF driver reported
the following:~~~~
Workaround: Make at least 2 GB of disk space available on the
installation location's drive. If you
still receive the error, then make more space available.
Administration Links using a PowerCube as the data source
You can create an Administration Link to import data from a package
that was created in IBM®
Cognos® Connection when the data source is a PowerCube. If you
select a package that was not
created from a PowerCube or was not published from IBM Cognos
Framework Manager you will
get an error message stating that the package you have selected
cannot be used as a source for an
Administration Link because it was not published from Framework
Manager.
18
UNIX gateway configuration
If you are using a UNIX® gateway with Planning, you will require
the addition of a separate library
for use with Contributor Web Client.
Missing Launch Options in IBM Cognos Connection
If you are using a UNIX® gateway with Planning, only Drill-though
Definitions is available through
launch options in IBM® Cognos® Connection.
IBM Cognos Connection does not keep a record of scheduled Planning
macros
When scheduled Planning macros run through IBM® Cognos® Connection
a record is not kept in
the Current/Past Activities in IBM Cognos Connection.
You can use the Monitoring Console to verify the state of scheduled
macros.
Workflow page URL in the Contributor Help Text causes an error on
the page
When you enter a URL for the Workflow page into the Contributor
Help Text in IBM® Cognos®
Planning Administrator, the URL typically opens within the Workflow
Page, rather than opening
in a new window. This is expected behavior. However, if the user
clicks on a Workflow page URL
and opens the web page inside the Workflow page, then the
information arrows next to State,
Ownership, Reviewer, and Last Data Change will result in an error
on the page when they are
clicked.
To avoid this, either inform users not to click on the URL before
the information arrows, or add
content to the URL tag in the Administration Console to open the
URL in a new window. You can
create the URL to open the page in a new window like this: <a
href="http://www.ibm.com"
TARGET="_blank">IBM Website</a>. "_blank".
Cannot secure the update mechanism for Contributor Web Client
Use of the update mechanism in Contributor Web Client is optional.
For this version, if customers
would like to use this capability, the update site itself cannot be
secured through your web server.
This does not affect the rest of the C8 folder content. With some
security products, such as
Siteminder, it is not possible to have a mixture of security
settings beneath a parent folder. So, it is
possible to change the location of the update site from the
default, which is beneath the C8 folder,
to a new location. It can then be left unsecured and have no impact
on the rest of the IBM Cognos
8 content. The location of the update site is stored in
<installation folder>\\cognos\\c8\\webcontent\
\contributor\\epRemoteCaller.js and you can change it to point to a
new location. More instructions
can be found in the file itself.
Instead of securing the C8 folder, secure the individual folders
under C8 like cgi-bin. The webcontent
folder contains static html documents and documentation, none of
which need to security.
Different D-Link behavior in Single e.List and multiple e.List
views
You have two cubes with a link running in Fill mode between them.
One of the dimensions on the
source and target cubes is matched on description. These dimensions
being matched on are not
identical. The Access Table on this dimension is set up to make the
source cube No Data for some
nodes but not others. If you open a single node where the source
cube is set to No Data, then the
link does not execute and the target is left untouched, as if the
link did not exist. If you open a
Release Notes 19
Chapter 2: IBM Cognos Planning Release Notes
multinode view which has a mixture of nodes that have the source
cube set to No Data as well as
'with data' then the target cube for all nodes is zeroed out and
then populated with data from the
source cube. For the nodes where the source cube is available, this
is normal behavior. For the nodes
where the source cube is not available, the behavior is different.
In this case, when a single node is
opened, the data is zeroed out rather than left untouched.
Use Substitute link mode rather than Fill mode.
IBM Cognos Planning data service This section contains known issues
about the Planning data service.
Parent category displays zeros
In cases where the source data categories do not roll up to a
parent category, IBM® Cognos® Report
Studio and IBM Cognos Analysis Studio display a temporary parent
category with a data value of
zero (0).
Unexpected summary data in Report Studio
If you add an additional summary row to an existing report in IBM®
Cognos® Report Studio, and
change the roll up property of this row, the original IBM Cognos
Planning Contributor parent row
may be impacted by the new roll up setting.
Packages containing an IBMCognos Planning data source are
unsupported in IBMCognos DataManager or IBM Cognos Metrics
Designer
Packages containing a IBM® Cognos® Planning data source are
unsupported in IBM Cognos Data
Manager or IBM Cognos Metrics Designer.
For Data Manager, access the published plan as a relational data
source. For Metrics Designer,
generate a Framework Manager model against the published plan with
the Generate Framework
Manager Model extension. For more information about publishing plan
data or generating a
Framework Manager model, see the IBM Cognos Planning Contributor
Administration Guide.
Generate Framework Manager Model support
The following section contains information that pertains to
Generate Framework Manager Model
support.
Cognos ReportNet 1.1 and IBM Cognos Planning generated model file
incompatibility
Files generated with the Generate Framework Manager Model wizard in
IBM® Cognos® Planning
Analyst or the Generate Framework Manager Model admin extension in
IBM Cognos Planning
Administrator are not compatible between Cognos ReportNet® version
1.1 and IBM® Cognos®
Planning. In IBMCognos Planning, the update option is not supported
for ReportNet 1.1 generated
models. Attempting to update a Cognos ReportNet version 1.1 model
can cause the wizard or
extension to fail with the following message:
An error occurred while creating the model.
To solve this problem, create new IBMCognos Planningmodels and
packages. If necessary, customize
these in IBM Cognos Framework Manager.
20
Internationalization This section contains known issues when using
IBM® Cognos® Planning with international data.
Sorting in IBM Cognos Planning Analyst
Sorting in IBM® Cognos® Planning Analyst, such as inserting new
items in a D-List alphabetically,
may not support the collation sequence as specified by regional
settings for the operating system.
Sorting issues are most prevalent for Korean and Thai
locales.
Known IBM Cognos Business Intelligence problems This section
contains IBM® Cognos® Business Intelligence issues.
There are no known issues in IBM Cognos BI that affect IBM Cognos
Planning at the time of pub-
lication.
General documentation problems This section contains general
documentation issues.
There are no known general documentation items at the time of
publication.
Release Notes 21
22
Chapter 3: Deprecation notices
This section contains information about IBM Cognos Planning
deprecation notices.
Supported environments This section contains information about IBM
Cognos Planning deprecation notices for supported
environments.
There are no deprecation notices for supported environments at the
time of publication.
Product features This section contains information about IBM Cognos
Planning deprecation notices for product
features.
There are no deprecation notices for product features at the time
of publication.
Licensed Materials – Property of IBM 23© Copyright IBM Corp. 1999,
2010.
24
64-bit computer support, 10
admin links
DB2, 15
sorting, 21
B BI, See IBM Cognos Business Intelligence
BMTReportNet.log file
configuring
known problems, 13
Contributor Help Text
DB2
deprecation notices, 23
d-links
DSN for database server
documentation update, 13
Licensed Materials – Property of IBM 25© Copyright IBM Corp. 1999,
2010.
F features
deprecated, 23
known problems, 20
Planning Contributor Add-in forMicrosoft Excel, 16
I IBM Cognos Business Intelligence
known problems, 21
IBM Cognos Connection
languages, 10
IBM Cognos Metrics Designer
IBM Cognos Planning
IBM Cognos Report Studio
JAWS screen reader
Contributor Add-in for Microsoft Excel, 15
jobs
upgrading, 10
Generate Framework Manager Model, 20
IBM Cognos Business Intelligence, 21
IBM Cognos Planning, 8
installation and configuration, 8
L Launch Options
layouts
M macros
editing, 9
26
Index
tributor Add-in for Microsoft Excel, 15
Microsoft SQL Server
connection string, 8
N network installation point
performance
Execute Analyst Macro step, 18
Planning Analyst, See Analyst
Planning Contributor, See Contributor
Hide All Objects option, 16
using with Microsoft Excel 2007 and JAWS screen
reader, 15
update mechanism
publish containers, 16
V Validate source data on import and log errors to file
checkbox, 15
Updated: October 18, 2010
System requirements
Installation and configuration
Known Administration Issues
Internationalization
General documentation problems
