GAUSS-02601 -- GAUSS-02610

GAUSS-02601: "invalid source encoding ID: %d"

SQLSTATE: XX000

Description: Internal system error.

Solution: Contact technical support.

GAUSS-02602: "expected source encoding '%s', but got '%s'"

SQLSTATE: XX000

Description: Internal system error.

Solution: Contact technical support.

GAUSS-02603: "invalid destination encoding ID: %d"

SQLSTATE: XX000

Description: Internal system error.

Solution: Contact technical support.

GAUSS-02604: "expected destination encoding '%s', but got '%s'"

SQLSTATE: XX000

Description: Internal system error.

Solution: Contact technical support.

GAUSS-02605: "encoding conversion length must not be negative"

SQLSTATE: XX000

Description: Internal system error.

Solution: Contact technical support.

GAUSS-02606: "invalid byte sequence for encoding '%s': %s"

SQLSTATE: 22021

Description: The character sequence cannot be identified.

Solution: Ensure that the data contains no unrecognizable character encoding by following the instructions provided in Character Set Support in PostgreSQL Documentation.

GAUSS-02607: "character with byte sequence %s in encoding '%s' has no equivalent in encoding '%s'"

SQLSTATE: 22P05

Description: The related character code cannot be found.

Solution: Run the select * from pg_conversion command to view the conname column. Ensure that the two types of character encoders can be converted to each other.

GAUSS-02608: "encoding name too long"

SQLSTATE: 42622

Description: The character encoding name is too long.

Solution: Shorten the character encoding name.

GAUSS-02609: "invalid encoding number: %d"

SQLSTATE: 22023

Description: The character sequence cannot be identified.

Solution: Ensure that the local character set is supported.

GAUSS-02610: "conversion between %s and %s is not supported"

SQLSTATE: 0A000

Description: These two character encoding sets cannot be converted to each other.

Solution: Ensure that the source and target character sets are compatible.