ucybdbld v21 with Postgresql fails with invalid byte sequence for encoding "UTF8"
search cancel

ucybdbld v21 with Postgresql fails with invalid byte sequence for encoding "UTF8"

book

Article ID: 407902

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

We are installing Automic Automation 21.0.14 on Linux using as database a Postgresql 16.x database also running on Linux.

After configuring the ucybdbld.ini with the connection string as follows:

sqlDriverConnect=ODBCVAR=NNJNIORP,host=localhost port=5432 dbname=automicdb user=username password=xxx connect_timeout=10 client_encoding=UTF-8

When launching it to perform a dbload of the database with a command:

./ucybdbld -B -X/opt/automic/Utility/db/general/21.0/UC_UPD.TXT

It fails with the errors below:

20250819/153616.589 - U00003590 UCUDB - DB error: 'ERROR:  invalid byte sequence for encoding "UTF8": 0x80 CONTEXT:  unnamed portal parameter $2', '', '', ''
20250819/153616.589 - U00003592 UCUDB - Status: '22021' Native error: '3452617' Msg: 'invalid byte sequence for encoding "UTF8": 0x80'
20250819/153616.589 - U00000006 DEADLOCK or Connection to database lost - Rollback handling initiated. See previous messages.
20250819/153616.589 - U00003531 UCUDB: Error while checking data source (e.g. code conversion or driver problem, see log file).

Environment

Automic Automation 21.x on Linux with Postgresql 16.x as database.

Cause

Wrong client_encoding defined in ucybdbld.ini (client_encoding=UTF-8 instead of client_encoding=LATIN9)

Resolution

Modify the connection string in all the utilities and AE configuration files to client_encoding=LATIN9 for 21.x components.

See the examples from the ini and documentation below:

For v21:

  • SQLDRIVERCONNECT=ODBCVAR=NNJNIORP,host=host01 port=5432 dbname=aedb user=automic password=1 connect_timeout=10 client_encoding=LATIN9

For v24:

  • SQLDRIVERCONNECT=ODBCVAR=NNJNIORP,host=host01 port=5432 dbname=aedb user=automic password=1 connect_timeout=10 client_encoding=UTF8

Additional Information

Please review the documentation where an example is shown.

For versions 21.x(and inferior) the client_encoding should be LATIN9, whereas for v24+ the client_encoding should be set UTF8.