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
Make sure you always provide prefixes
to character string literals as instructed
in “Rules for Encoding SQL Language
Elements” (page 23).
If you cannot generate prefixes with
your character string literals, contact
your HP support provider and ask
them to resolve the problem.
This error is displayed when a
user fails to explicitly specify the
correct prefix for a character string
literal (for example, _ISO88591
or _UCS2) for a character column
that is not the default character
set. For example, in the ISO88591
configuration, all newly-created
columns default to ISO88591
columns unless the column's
character set definition explicitly
specifies CHARACTER SET UCS2.
If it does, the user must also
specify the UCS2 prefix (_UCS2)
for every character string literal
in the SQL statement that is
associated with a UCS2 column.
If literal prefixes are not specified
for columns that are not the
default column for the
configuration, the SQL statement
will fail and return an error.
• An incompatible
character set error
(4039) is displayed
at a client
workstation.
• The DDL or DML
statement fails.
Correct
character string
literal prefixes
not provided in
an SQL
statement
All SQL metadata must be stored in
ISO88591 columns, regardless of the
Neoview character set configuration.
An attempt was made to store
character data in a metadata table
column using a UCS2 column.
An error reporting an
incorrectly-prefixed
literal is received.
Using UCS2
columns to
query SQL
metadata
In the Unicode configuration, SQL
identifiers are stored in UTF8
characters, where multibyte characters
can quickly consume limited space.
Reduce the number of characters in the
SQL identifier or use 7-bit ASCII
characters instead of multibyte
characters.
an SQL identifier exceeded the
128-byte limit.
An error reporting that
an SQL identifier is too
long is received.
SQL identifier
too long
40 Troubleshooting Guidelines for Neoview Character Sets Users