- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
12-18-2025 01:57 AM
Hi all,
When trying to connect to DBeaver, the client gives the error: "the server's client_encoding parameter was changed to sql_ascii"
This happens to a set of servers only, and with the same client, direct connectivity is possible.
Has anyone encountered this and resolved?
Thanks in advance!
12-18-2025 12:53 PM
Did you check Session Diagnostics already?
Inside SIA interface
12-18-2025 05:28 PM
Hi @Maneesh Yatiwella
The error message suggets that client_encoding required to be UTF8 in DBeaver to work properly.
Can you please check with DBeaver team whether they can set allowEncodingChanges to True?
Hope it helps!
12-18-2025 07:27 PM
Hi @Malhar Vora ,
The issue is that when connecting directly to the DB with the client, there's no issues. However, when connecting to the same DB with the same client via SIA this happens.
12-18-2025 07:28 PM
Hi @Airton Amaral ,
Yes.
Compared a working one with the one in issue as well. No hints.
12-21-2025 04:38 PM
Hi @Maneesh Yatiwella
Can you please check whether TLS is enabled on the DBeaver ?
The connectivity might be failing due to TLS handshake from SIA to DB.
Hope it helps ‘
12-21-2025 07:11 PM
Hi @Malhar Vora ,
Yes, tried
It seems that changing anything in the DBeaver client makes no difference.
BR,
Maneesh
12-21-2025 07:14 PM
@Malhar Vora , @Airton Amaral Thanks for the input. I asked the customer to check on the PostgreSQL instances to change the settings instead of the DBeaver client. Seems it is working for the DBs we tried.
12-23-2025 02:35 AM
Hi @Maneesh Yatiwella ,
I’m glad to hear the issue is resolved!
If one of the replies helped you along the way, please mark it as ‘Best Answer’ to assist other community members with similar questions.
Thank you! Omri
01-06-2026 09:00 AM
Hi Omri,
The issue could be resolved by asking to change the settings at the PostGre SQL instance. It seems like there are some limitations with SIA for some clients even though the documentation specify only DB versions. Because all the DB that did not support were on a different version. However, as per the documentation, that version should support
BR,
Maneesh
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

