Known issues in 12.1.x

This section describes known issues found in IBM® Cognos® Analytics 12.1.x versions.

12.1.0

Swagger loads wrong index page for the User Profile service

When you access the Swagger UI for the User Profile service, you might see an incorrect or a non-existent page.

Workaround

To resolve the issue, follow these steps:

  1. Go to the Explore field in the Swagger UI.
  2. Replace the https://petstore.swagger.io/v2/swagger.json URL with swagger.json.
  3. Press Enter or click Explore to reload the page.
Issue with the Cognos Analytics 12.1.0 installer on high-resolution desktops

When you run the Cognos Analytics 12.1.0 installer on a high-resolution desktop, such as 3840 x 2400 DPI, the installation wizard may display information that is cut off and the Select a Folder window may be too small.

Workaround

To resolve the issue, instead of running the file analytics-installer-4.0.8-win.exe to launch the installer, run the file analytics-installer-4.0.8-win.bat. The .bat file first corrects the resolution issue by adding the environment variable setting __COMPAT_LAYER=DpiUnaware. Then it runs the installer.

Follow these steps:

  1. In a command window, navigate to the folder to which you downloaded the installer files.
  2. Run the file analytics-installer-4.0.12-win.bat as an administrator.

    The .bat file runs, then launches the installer, which runs without any resolution issue.

For more information, see Single server installation.

Issues with Dynamic Query Analyzer and Cube Designer splash screens on high-resolution desktops

Starting the Dynamic Query Analyzer or Cube Designer on high-resolution desktops, such as 3840 x 2400, might result in opening extra splash screens or in cutting off information from the original ones.

Workaround

To resolve the issue, follow these steps:

  1. Locate the application file.
    • For Dynamic Query Analyzer, navigate to the .\dqa\win32.win32.x86_64\eclipse\dqa.exe file
    • For Cube Designer, navigate to the .\bin64\fmDesignerApp\FmDesigner.exe file
  2. Right-click the file to open the Properties window.
  3. Go to the High DPI scaling override section.
  4. Select the Override high DPI scaling behavior option.
  5. Choose the Application option from the Scaling performed by drop-down list.
  6. Click OK to confirm the changes.

For more information, see Start Dynamic Query Analyzer or Testing the installation of IBM Cognos Cube Designer.

Some Learn panel features are not available

The following Learn panel features are not available in release 12.1.0:

  • the Recommended for you list of curated topics
  • a What's New link
  • context-sensitive topic results based on the location from which the Learn panel is launched
  • support for some of the 26 Cognos Analytics product locales. AssistMe supports only these languages:
    • German (de)
    • English (en)
    • Spanish (es)
    • French (fr)
    • Italian (it)
    • Japanese (ja)
    • Korean (ko)
    • Brazilian Portuguese (pt)
    • Russian (ru)
    • Swedish (sv)
    • Simplified Chinese (zh-Hans)
    • Traditional Chinese (zh-Hant)

For more information, see New technology supporting the Learn panel.

Some third-party JDBC drivers incur runtime failures
Apache Hive does not officially support Java 17 until Hive 4.1

Even though the compatibility tests were successful, the advanced features, such as Kerberos authentication, did not function properly in the Java 17 environment. You might not be able to use existing Hive drivers in release 12.1.0.

For more information, see Connections to Apache Hive using Kerberos throws java.lang.NoClassDefFoundError.
Cloudera Impala JDBC and Kerberos

Cloudera Impala does not work with Kerberos authentication if you use IBM JRE 17; however, it works with Oracle Java™ 17. Because of that defect, you might not be able to use the Impala drivers with Kerberos authentication in release 12.1.0.

For more information, see Connections to Cloudera Impala using Kerberos throws java.lang.NoClassDefFoundError.

Dremio JDBC failures due to Apache Arrow

Dremio JDBC driver does not work with Apache Arrow in Java 17 environment. Because of that defect, you might not be able to use this driver in release 12.1.0.

For more information, see Dremio JDBC driver throws java.lang.IndexOutOfBoundsException.

Snowflake JDBC failures due to Apache Arrow

Snowflake JDBC driver does not work with Apache Arrow in Java 17 environment. Because of that defect, you might not be able to use this driver in release 12.1.0.

For more information, see Snowflake JDBC driver throws java.lang.IndexOutOfBoundsException.

Databricks JDBC driver failures due to Apache Arrow

Darabricks JDBC driver does not work with Apache Arrow in Java 17 environment. Because of that defect, you might not be able to use this driver in release 12.1.0.

For more information, see Databricks JDBC throws com.databricks.client.jdbc42.internal.apache.arrow.vector.VarCharVector.get on AIX® and z-Linux®.

The following Informix® issues are not specific to using a Java 17 runtime environment.

Early versions of the Informix 15.0.x JDBC driver have issues that cause queries to fail

Because of that defect, you might not be able to use early versions of the Informix 15.0.x JDBC driver in release 12.1.0.

For more information, see Queries to Informix do not delimit identifiers when the Informix 15.0 JDBC driver is used.

Informix 4.5.x JDBC drivers fail to connect to Informix 15 servers

Because of that defect, you might not be able to use the Informix 4.5.x. JDBC drivers in release 12.1.0.

For more information, see Connections to Informix server version 14.x or 15.x do not work when the Informix JDBC driver 15.0.0 is used.

The JMX local connector is broken due to the Java 17 upgrade

The Liberty profile JMX local-connector feature does not work with Java 17 JRE. This is because some of the classes are moved from JRE to JDK.

The following error message appears:
Exception = java.lang.ClassNotFoundException
Source = com.ibm.ws.jmx.connector.local.LocalConnectorActivator$LocalConnectorHelper$1
probeid = 146
Stack Dump = java.lang.ClassNotFoundException: jdk.internal.agent.Agent

Workaround

To resolve the issue, you can replace the JMX modules with JDK modules and export them via JVM options.

Option 1
  1. Start Cognos Configuration.
  2. Enable a Cognos Analytics JMX remote connection.
  3. Specify the following URL:

    service:jmx:rmi://<ip>/jndi/rmi://<ip>:<port>/proxyserver

Option 2

Connect JMX using the Attach API.

Large deployment fails to import when using IBM Java 17

If your installation uses IBM Java 17, which is available in release 12.1.0, and you try to import a large deployment archive, the following error message appears in the file cognosserver.log:

JAXP00010004: The accumulated size of entities is "50,000,001" that exceeded the "50,000,000" limit set by "FEATURE_SECURE_PROCESSING".

Workaround

To resolve the issue, you can increase the size of imported deployments when you are using IBM Java 17. Follow these steps:

  1. Open the file installation_location\bin64\bootstrap_wlp_operating_system.xml in a text editor.
  2. Find the line <param condName="${java_vendor}" condValue="Oracle">-XX:+DisableExplicitGC</param> and add the following line after it:
    <param condName="${java_vendor}" condValue="IBM">-Djdk.xml.totalEntitySizeLimit=999999999</param>
  3. Restart the Cognos Analytics service.

    The deployment can now be imported successfully.

For more information, see Importing a deployment archive.

Imported PowerPlay® reports may fail to run as PDF

If you import a deployment from an old version of Cognos Analytics that contains PowerPlay reports, then you try to run one of the PowerPlay reports as PDF, the run may fail. The following message appears:

PDS-RM-0002 The PowerPlay server is not available.ppserver/pprp/SecureReport.cpp(365)

The issue can occur when you run the report from a Content folder or during a background run from a schedule.

Note: This issue does not occur if you open one of these reports in PowerPlay Studio and run the report as PDF.

Workaround

Follow these steps for each report:

  1. Open the report in PowerPlay Web 12.1.0 or higher.
  2. Save the report.

The report can now be run as PDF without any error messages.

The sample Great Outdoors data module can produce unexpected results
When you use the sample Great Outdoors data module to create a table, in rare Bottom count filter cases, the table can produce blank results.