Jitterbit · Database connector (PostgreSQL ODBC)
PostgreSQL: client encoding mismatch
Short answer
This Jitterbit PostgreSQL error means the encoding the server uses differs from the default encoding the PostgreSQL ODBC driver assumes. In the Database connection settings, add ConnSettings=SET CLIENT_ENCODING to 'LATIN1' to Additional Connection String Parameters, substituting the server's encoding.
VerifiedLast verified
01Error text
client encoding mismatch02Likely causes
- The encoding the PostgreSQL server uses differs from the default encoding the PostgreSQL ODBC driver assumes.
03How to fix it
- In the Database connection settings, add
ConnSettings=SET CLIENT_ENCODING to 'LATIN1'to Additional Connection String Parameters, substituting the server's encoding. - On Windows, if the server uses a Cyrillic encoding such as WIN1251, also set the client encoding to WIN1251 in the ODBC driver settings.
04Official documentation
→Related errors
- Base64 decoding failedThis Jitterbit error in DBLookup or DBExecute means an agent earlier than 12.9 tried to Base64-decode a JDBC result that only looks like Base64, such as a JWT. For private agents, upgrade to version 12.9 or later.
- Database connection could not be established due to a security policy violationThis Jitterbit error means agent 12.10 or later blocked a database connection to a loopback address or one that uses a restricted connection string parameter. On the private agent, configure the [JdbcSecurity] section of jitterbit.conf to allow the specific connection or parameter.
- Field value too long / values were truncatedThis Jitterbit database error means a mapped source value is longer than the target column, and by default the value is rejected. In the activity configuration, enable Allow truncation of character fields.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for Jitterbit work:Open Jitterbit jobsJitterbit rates and salaries