SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

Utility Messages (20000 through 23099)
HP NonStop SQL/MX Messages Manual—523730-004
17-60
SQL 20244
Where file is the name of the Unicode data file.
Cause. The byte order mark bytes specified are invalid.
Effect. The Unicode data import fails.
Recovery. Re-create the Unicode data file. Specify the standard byte order mark
sequence: 0xFF 0xFE, for the little- endian byte order, and 0xFE 0xFF, for the begin-
endian byte order.
SQL 20245
Where column-name is the name of the column that corresponds to the invalid
character set value.
Cause. You specified a literal, with a character set other than ISO8859, for column
column-name, which is part of the partition key.
Effect. The operation fails.
Recovery. Partition key columns must be defined with character set ISO88591.
SQL 20250
Cause. You tried to reuse the first partition, but the new key range that you specified
(in the WITH clause) overlaps the existing key range of the first partition.
Effect. The operation fails.
Recovery. None.
SQL 20251
Where operation is the type of MODIFY operation including ADD, MOVE, or DROP.
20244 The byte order mark in Unicode data file file is not
valid.
20245 An invalid character set was specified. Column column-
name is part of the partitioning key and must be defined with
the character set ISO88591.
20250 The first partition cannot be reused because the
specified new key range overlaps the existing key range of
the first partition.
20251 Request operation uses the same partition location as
another request in the command.