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

5 Troubleshooting Guidelines for Neoview Character Sets
Users
Table 5-1 identifies the Neoview Character Sets-related problems that you might need to
troubleshoot. For each problem type, the symptoms, probable causes, and recommended corrective
actions are provided. If you encounter problems that are not described here, contact your HP
support provider.
Table 5-1 Troubleshooting Symptoms, Causes, and Recommended Corrective Actions for Users
Recommended Corrective ActionsProbable CausesSymptomsProblem Type
Use Neoview ODBC and JDBC drivers
that are compatible with all the
Neoview platforms on your network.
Release 2.2 Neoview ODBC and
JDBC drivers can be connected
only to a Release 2.4 or Release 2.3
Neoview platform that uses the
ISO88591 configuration. If you
connect Release 2.2 Neoview
ODBC or JDBC drivers to a
Release 2.4 or Release 2.3
Neoview platform that uses the
SJIS or Unicode configuration, a
connection error is generated. For
more information, see
“Compatibility Between Neoview
ODBC and JDBC Drivers and
Neoview Platforms” (page 19).
The connection is
rejected and a
connection error is
generated.
Connection
error generated
when using a
downrev
Neoview ODBC
driver or
Neoview JDBC
driver
Correct the character mismatch. For
example:
• Locate the string literal that
contains the mismatched character.
• Issue an UPDATE statement with
the updated literal value.
• Pass the corrected value as a
parameter.
To prevent SQL-side SJIS character
mismatches from occurring, always
send the SJIS character data in
parameters when using an ODBC
connection. Do not enclose them in
SQL statement character string literals.
This type of character mismatch
can occur when SJIS character
data is inserted and queried using
either one of these two methods :
• The data was inserted as a
literal in an SQL statement but
queried using a parameter.
• The character value was
inserted as a parameter but
queried using a literal in an
SQL statement.
For more information, see “SJIS
Character Mismatches” (page 42)
The Neoview database
cannot successfully
query or compare SJIS
characters.
SQL-side SJIS
character
mismatch error
• Do not use 4-byte GB18030
characters in SQL identifiers or in
string literals inside SQL
statements. If you must use 4-byte
GB18030 characters in the data,
always use parameters to pass them
to the Neoview database.
• Do not use the two 4-byte GB18030
characters that map to the UCS2
values, 0xFFFE and 0xFFFF.
• You are using 4-byte GB18030
characters in SQL identifiers
or in character string literals
within SQL statements. The
SQL compiler does not support
the use of 4-byte GB18030
characters for these purposes.
• You are using one or both of
the two 4-byte GB18030
characters that map to 0xFFFE
and 0xFFFF for Unicode or
UCS2 characters. The SQL
compiler might not support
these two characters, even
when they are passed as
parameters.
A syntax or translation
error is displayed at a
client workstation.
Using 4-byte
GB18030
characters in
SQL statements
39