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
  3. Topics

KB46780: History list message is garbled when "UTF-8" is set for the "Character set encoding for Windows drivers" for the database connection against Oracle 11g when using "AL32UTF8" including Japanese Character.

Community Admin

• Strategy

This article explains that when Oracle 11g is using "AL32UTF8" for the Character set with Japanese Character in Windows, the History list messages could appear garbled.

SYMPTOM:
When Oracle 11g is using "AL32UTF8" for the Character set with Japanese Character in Windows, the History list messages are garbled as below:
 

ka04W000000OejAQAS_0EM440000002HIG.png

CAUSE:
This issue happens when "UTF-8" is set for the "Character set encoding for Windows drivers" in the database connections of Strategy.
ACTION:
The setting is the DB Connection property for the Driver Character Set, it is not database side. Intelligence Server is on Windows so by default on Windows most ODBC drivers use UCS-2 code page for Unicode data. In this situation, we generally set this to "Non UTF-8".
Edit the Database Instance -> Modify the Database coonection -> Advanced tab -> configure the setting as below:

ka04W000000OejAQAS_0EM440000002HII.png

 
46780

Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017