For troubleshooting information and support, consult the Knowledge Base. If you require additional information not found in the Knowledge Base or listed below in these release notes, contact Technical Support.

Known issues

Refer to the troubleshooting sections below for troubleshooting steps available for some of the known issues in this MicroStrategy release.

Oracle

Symptom: Manipulations in MicroStrategy such as starting MicroStrategy Intelligence Server, logging in to a project, executing a report, working with MicroStrategy objects, and importing a large MDX cube into MicroStrategy cause the Oracle database error ORA-01000.
Cause: The MicroStrategy metadata is stored in an Oracle database and the Oracle parameter OPEN_CURSORS is set to too low a value.
Solution: Increase the OPEN_CURSORS parameter to 1500. For additional information on this issue, refer to the MicroStrategy Tech Note TN 32324.

DB2

Symptom: Manipulations in MicroStrategy such as starting MicroStrategy Intelligence Server, logging in to a project, executing a report, working with MicroStrategy objects, and importing a large MDX cube into MicroStrategy cause DB2 to return the following database error message:
Database error <>: OdbcPreparedStatement::GetParameterDataTypes() failed. Error type: Odbc error. Odbc operation attempted: SQLDescribeParam. [HY000:8292: on SQLHANDLE] [MicroStrategy][ODBC DB2 Wire Protocol driver] No more available statements. Please recreate your package with a larger dynamicSections value. For more information, please consult DB2 document for error code SQL08292.
Cause: The MicroStrategy metadata is stored in a DB2 database and the DB2 parameter DynamicSections is set to too low a value.
Solution: Increase the DynamicSections parameter to 999. For additional information on this issue, refer to the MicroStrategy Tech Note TN 32324.

Case sensitivity

Symptom: When you include database tables and columns into a MicroStrategy project, case sensitivity is not enforced. This means that if two or more database tables or two or more database columns share the same name and use case sensitivity in the database to distinguish them as unique, MicroStrategy does not recognize them as different database tables and database columns. This can cause MicroStrategy to access the wrong database table or database column in certain scenarios.
Workaround: To ensure that database tables and database columns can be distinguished as unique in MicroStrategy, use names that are different in more than just case when defining the database tables and columns in the database. For example, instead of naming two tables as Test_Table and TEST_TABLE in your database, you can name these two tables Test_Table and Test_Table2.

Online Help

Issues that have a prefix of S (S#####) are customer cases that can be tracked through MicroStrategy Technical Support. Those that are prefixed with T (T#####) are MicroStrategy internal issues. Internal issue numbers do not correlate to customer case numbers.

Google Chrome support

A Google Chrome security update prevents WebHelp systems that are in locally stored file systems from being displayed properly. This is a known issue with Google Chrome. This affects viewing the Online Help for MicroStrategy Command Manager, MicroStrategy Integrity Manager, MicroStrategy Health Center, and other MicroStrategy administrative tools. To view the online help documentation for these MicroStrategy products and tools, you can:

• Open Google Chrome using the command line option –allow-file-access-from-files. Be aware that this disables some of the security features of Google Chrome.
• Use one of the other web browsers supported for these MicroStrategy products and tools, such as Internet Explorer or Firefox.

Exporting to OpenOffice.org Calc

Various MicroStrategy products support OpenOffice.org Calc as an export application. Due to some limitations of OpenOffice.org Calc, some standard exporting features are not supported. The list below provides guidelines to support exporting features in OpenOffice.org Calc:

• Use the MicroStrategy export options to embed the images directly in the exported file. Linked images cannot be exported to OpenOffice.org Calc.
• Gradient colors for the background of cells are displayed as single, solid colors. Gradient colors for the background of cells are not supported when exporting to OpenOffice.org Calc.
• Borders are displayed as solid lines. Certain border styles such as dashed or dotted borders are not supported when exporting to OpenOffice.org Calc.
• OpenOffice.org Calc has a limit of 256 worksheets in a workbook. You can create additional workbooks in OpenOffice.org Calc.

Resolved issues

For a complete list of all the issues resolved in this MicroStrategy Analytics Enterprise release, consult the Knowledge Base technical note .