Known issues and limitations in Cognos Analytics

The following known issues and limitations apply to Cognos Analytics.

Cannot start service instance after you backup and restore content in Db2 OLTP cartridge

Applies to: 5.1.0 and later

You cannot start a Cognos Analytics service instance after you restore the instance that has the content store in the db2oltp cartridge. The cause of this issue is that the port number of the Db2 service instance changes after the restore.

Workaround

For the database connection, use the host name and port number of the Db2 instance in Kubernetes that do not change.

For more information, see Connecting to Db2 ports and services.

Cannot work with reports and receive XQE-MD-0107 Unable to establish a metadata connection to data source error message

Applies to: 5.1.2

You cannot work with a report that stops responding and the following error message is displayed:

XQE-MD-0107 Unable to establish a metadata connection to data source ...

This issue might occur when you provision a new Cognos Analytics service instance with the content store database that was created with an earlier instance provision.

Workaround

Before you re-provision your new instance, back up all your content objects using the Administration console and download this deployment using one of the following methods:

IBM Db2 database server cannot use Db2 encryption when creating the content store

Applies to: 5.1.1 and 5.1.2

You cannot create a Cognos Analytics service instance that uses a Db2 database as the content store when Db2 encryption is enabled. The service instance might provision but various issues might occur when you open dashboards, explorations, or reports.

Workaround

You must select the Disable Db2 encryption option when you create the content store.

Cannot create a service instance that uses a Db2 database with a connection that uses vault stored credentials

Applies to: 5.1.0 and later

You cannot create a Cognos Analytics service instance that uses a Db2 database as the content store with a connection where the credentials are stored in a vault. The service instance creation fails.

Workaround

You must use a connection with manually entered credentials to create a service instance that uses a Db2 database to store content.

Cannot save your configuration in Cognos Framework Manager or Transformer

Applies to: 5.1.0 and later

You cannot save your configuration in the Framework Manager and Transformer when you use these applications with IBM® Software Hub.

Workaround

To solve this problem, you must download from Fix Central (FC) and install Cognos Analytics Interim Fix (IF) 1. This Fix restores a feature that enables communication between the Framework Manager or Transformer and IBM Software Hub.

Cannot use the Manage menu to back up the content store

Applies to: 5.1.0 and later

You cannot use the Manage > Content > Backup menu item to back up the content store in Cognos Analytics on IBM Software Hub.

Workaround

To back up the content store, you must use the Administration console. For more information, see Backing up and restoring content in the Cognos Analytics documentation.

Specify the Cognos Analytics URL in Microsoft Teams

Applies to: 5.1.0 and later

If you are using Cognos Analytics with Microsoft Teams, you must ensure that the Cognos Analytics URL ends with bi/ when adding the URL to Microsoft Teams. For example,
https://cpd-ca.example.com/cognosanalytics/cat3/bi/

In this example, cat3 is the namespace to which Cognos Analytics is provisioned.

IBM Db2 database server cannot use Oracle compatibility mode when creating the content store

Applies to: 5.1.0 and later

If you configured the IBM Db2 database server to use Oracle compatibility mode, you must temporarily disable the Oracle compatibility mode before creating the content store. After creating the content store, configure the IBM Db2 database server to use Oracle compatibility mode again. For more information, see https://www.ibm.com/support/pages/node/515565.