EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB305255: MicroStrategy Intelligence Server 10.x running on UNIX/Linux operating system fails to initiate logging to the Statistics tables when the Statistics DB is hosted on a MySQL 5.x database


Community Admin

• Strategy


When MySQL 5.x is used as the Enterprise Manager Statistics Repository in MicroStrategy 10.x, MicroStrategy Intelligence Server running on a Linux operating system attempts to insert statistics data into the historical statistics tables (IS_XXX_STATS tables) instead of the Staging tables (STG_IS_XXX_STATS).

SYMPTOM
When MySQL 5.x is used as the Enterprise Manager Statistics Repository in Strategy 10.x, Strategy Intelligence Server running on a Linux operating system attempts to insert statistics data into the historical statistics tables (IS_XXX_STATS tables) instead of the Staging tables (STG_IS_XXX_STATS). It is verified that the DSN to the Statistics database is created using the supported ODBC driver for MySQL. Errors similar to the following are seen in the DSSErrors: 
 


2016-08-09 10:29:36.403-05:00 [HOST:Hostname][PID:18118][THR:4122457856][Database Classes][Error] Execute Query failed.Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [42S22:1054: on SQLHANDLE] [MySQL][ODBC 5.3(w) Driver][mysqld-5.6.10-enterprise-commercial-advanced]Unknown column 'SERVERNAME' in 'field list' Connection String: DSN=STATS_MySQL;UID=xxyyzz;. SQL Statement: insert into IS_DOCUMENT_STATS (JOBID,SESSI.....

 
From the DSSErrors log, it is also observed that the Statistics tables version is not correctly registered at the time of Strategy Intelligence Server startup. 

Statistics schema version from Database: 1

 
CAUSE
This issue is seen because of an incorrect encoding set on the Statistics database instance. This setting should be based on the encoding supported by the ODBC driver. 
 
ACTION

  1. Edit the Statistics Database Instance > Database Connection > Advanced > change the "Character set encoding drivers for Unix/Windows drivers" from UTF-8 to Non-UTF8. 
  2. Save the change and restart the Strategy Intelligence Server. 

 
The Strategy Internal reference number for the issue discussed in this document is DE37085. 


Comment

0 comments

Details

Knowledge Article

Published:

May 17, 2017

Last Updated:

May 17, 2017