SYMPTOM:
When a user attempts to retrieve German characters with Umlaut (for example, ÖÖÖ) using the Strategy ODBC Driver for Sybase ASE Wire Protocol on Solaris, the characters are incorrectly displayed (through Strategy DB Query Tool on Solaris) as shown in the image below:

The database is Sybase Adaptive Server, which is setup for codepage ISO-8859-1 (commonly known as ISO8859-1 or Latin-1). This codepage does support umlaut characters. Also, the ISO8859-1 codepage is installed on the Solaris machine.
The issue does not happen with the equivalent Windows driver - Strategy ODBC Driver for Sybase ASE Wire Protocol Version on Windows. The umlaut are displayed correctly (through Strategy DB Query Tool on Windows) as shown in the image below:

As a related symptom, the umlaut characters (ÖÖÖ) can be seemingly successfully retrieved through Strategy DB Query Tool on Solaris if the characters were inserted through Strategy DB Query Tool on Solaris in the first place. However, the same characters (that were inserted from Solaris) now display incorrectly through Strategy DB Query Tool on Windows, as shown in the image below:

CAUSE:
The IANAAppCodePage value is not appropriately set for the Strategy ODBC Driver for Sybase ASE Wire Protocol. This value is used by the Strategy ODBC Administrator (essentially the DataDirect ODBC Driver Manager on Solaris) to perform any transliteration necessary for International characters.
The value of IANAAppCodePage is set in the odbc.ini file. Refer to the following Strategy Knowledge Base technical note for details regarding this setting:
KB10136 (KB5300-752-0498) - How to configure ODBC Data Source Names for international environments in Strategy Intelligence Server Universal
ACTION:
Since the codepage used on the database and the operating system is ISO8859-1, use an IANAAppCodePage value of 4, which is the appropriate value for this codepage. By default, the IANAAppCodePage value is set to 106 when a DSN is created - 106 is the value for UTF-8. This may be changed to 4 by following the steps below:
After this value changes to 4, the umlaut will display correctly (through Strategy DB Query Tool on Solaris) as shown in the image below:
