Neoview Character Sets Administrator's Guide (R2.4, R2.5)

Table 5-1 Troubleshooting Symptoms, Causes, and Recommended Corrective Actions for Users
(continued)
Recommended Corrective ActionsProbable CausesSymptomsProblem Type
When the ISO88591 configuration is
selected, use only characters that are
supported (compatible) across all the
client workstations. To ensure
compatibility, use only 7-bit ASCII
characters or compatible 8-bit
ISO8859-n characters in SQL identifiers
and user data.
Causes can include:
• You inserted characters from
one client workstation into an
SQL table column and
attempted to retrieve
incompatible characters from
another workstation.
• You inserted characters from
two client workstations into
the same SQL table column
and attempted to retrieve
incompatible characters from
the second workstation.
These symptoms occur
when a client
workstation attempts
to query the Neoview
database:
• An error is
generated stating
that you inserted
characters from
another client
workstation that are
not supported on
the retrieving
workstation.
• Replacement
characters or
garbage data are
displayed from the
retrieving client
workstation.
• Neoview DB Admin
displays no data but
returns a CORBA
error.
• WMS cannot
display the
character data.
• Generated EMS
event messages
contain garbage
data.
Incompatible
client locale
errors in the
ISO88591
configuration
To avoid these replacement characters,
use only MS932-compatible SJIS
characters across all the client locales.
Do not use EUC-JP or other characters
that are incompatible with MS932.
A client locale that does not use
MS932-compatible encoding
attempted to retrieve
incompatible characters.
When the client locale
attempts to perform a
query in the SJIS
configuration, these
symptoms occur:
• A translation error
is generated stating
you inserted invalid
characters.
• Replacement
characters are
displayed from the
query application.
In the SJIS
configuration, a
client locale
with encoding
other than
MS932
generates
replacement
SJIS characters
41