Question & Answer
Question
How do I resolve NPS and MicroStrategy® connectivity problems when Unicode translation options differ?
Answer
When MicroStrategy is unable to connect to NPS, you should analyze the settings for the MicroStrategy locale and compare those against the settings for NPS.
If there is a mismatch in the Unicode Translation Options between the two systems, the settings on one of the systems should be changed to match the other. Choosing the system for amendment depends on what other systems are currently or potentially likely to connect to NPS. If all other systems connecting to NPS are set for UTF8, then it makes sense to amend the setting on the NPS side. Otherwise, it would make sense to make amendments on the client side.
The following example shows how to change UnicodeTranslationOption from utf16 to utf8 to match that of MicroStrategy:
/usr/local/ms
FileName: set_microstrategy_locale; This example file displays current MicroStrategy environment settings
LC_COLLATE=en_US.UTF-8
export LC_COLLATE
LC_CTYPE=en_US.UTF-8
export LC_CTYPE
LC_MESSAGES=C
export LC_MESSAGES
LC_MONETARY=en_US.UTF-8
export LC_MONETARY
LC_NUMERIC=en_US.UTF-8
export LC_NUMERIC
LC_TIME=en_US.UTF-8
export LC_TIME
LANG=en_US.UTF-8
export LANG
A possible solution would be to change the NPS Unicode Translation Options settings to match those of MicroStrategy. The settings are located in the file, odbcinst.ini. The following is an example of that file:
/usr/local/ms/microstrategy/odbcinst.ini
bash-3.00$ more /usr/local/ms/microstrategy/odbcinst.ini
[ODBC Drivers]
NetezzaSQL = Installed
[ODBC Connection Pooling]
PerfMon = 0
Retry Wait =
[NetezzaSQL]
Driver = /usr/local/ms/netezza/lib/libnzodbc.so
Setup = /usr/local/ms/netezza/lib/libnzodbc.so
APILevel = 1
BoolsAsChar = true
ConnectFunctions = YYN
Description = Netezza ODBC driver
DriverODBCVer = 03.51
DebugLogging = true
LogPath = /usr/local/ms/microstrategy/log
UnicodeTranslationOption = utf8 ##<<Edit this setting from utf16 to utf8 to match that of MicroStrategy
CharacterTranslationOption = all
PreFetch = 256
Socket = 16384
[ODBC]
Debug=ON
Trace=ON
DebugFile=/usr/local/ms/microstrategy/log/odbcinit-debug.log
TraceFile=/usr/local/ms/microstrategy/log/odbcinit-trace.log
TraceAutoStop = 0
Note: Debug and Trace settings should be OFF unless you are debugging. If set to ON, performance is likely to decrease.
Historical Number
NZ717678
Was this topic helpful?
Document Information
Modified date:
17 October 2019
UID
swg21571140