> I've add lc_ctype parameter in connection parameter at
> poolman.props file like this : lc_ctype=UNICODE_FSS

You have to check character set of your database or column. If you do
not specify it, it is "NONE" by default and will cause you problems
when working with unicode characters. There is no rule to translate
characters >0x80 between NONE and any other character set except
OCTETS.

So you have following choices:

- modify your database schema to use UNICODE_FSS as default database
encoding or modify your column definitions to use UNICODE_FSS.

- use NONE character set both in database and client and use prepared
statements to execute your queries.

- use casting to OCTETS to convert NONE character set of the database
into UNICODE_FSS (should be used only if first choice is not
available).

Best regards,
Roman Rokytskyy