DB Maintenance job Aborted
Article ID: 232337
Updated On:
Products
Issue/Introduction
UCYBDBAR fails with an error:
U00003590 UCUDB - DB error: 'ERROR: character with byte sequence 0xc2 0xa4 in encoding "UTF8" has no equivalent in encoding "LATIN9"', '', '', ''
Environment
Release : 12.3
Component : AUTOMATION ENGINE
Database: PostgreSQL
Cause
The character that is trying to be converted from UTF to LATIN9 is an undefined currency symbol, and actually has no translation in LATIN9.
The error message in the log file is:
U00003590 UCUDB - DB error: 'ERROR: character with byte sequence 0xc2 0xa4 in encoding "UTF8" has no equivalent in encoding "LATIN9"', '', '', ''
The only charset that can translate that is LATIN1, but this is not a valid encoding for Automic with PostgreSql.
Database is PostgreSql. Run the following in PostgreSql to verify the encoding:
SHOW SERVER_ENCODING;
SHOW CLIENT_ENCODING;
These should come back as UTF8. In this case these both came back as UNICODE.
The documentation states the UTF8 is required for PostgreSql
https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#Installation_Common/PreparationSteps/PrepareAEDB_PostgreSQL.htm?TocPath=Installing%2520and%2520Upgrading%257CManual%2520Installation%257CPreparing%2520for%2520the%2520Installation%257CPreparing%2520the%2520AE%2520Database%257C_____4
The fact that the character is written to the DB in the first place without providing a replacement character is a problem with the version of Postgres or its client (see solution 2).
Resolution
Solution 1
The database must be created using UTF8.
If the database does not have SERVER_ENCODING and CLIENT_ENCODING both at UTF8, then the following must be done.
1. Export the database dump.sql
2, Create a new database with UTF8 encoding
3. Restore the database dump to this new database
4. Stop AE
5. Update your ini files to use this new database
6. Restart AE
Solution 2
If you can upgrade your AE to v21.0.4 or higher you can upgrade the Postgres DB and Client to v13 or v14 which does not have this issue anymore because a replacement character is written to the DB.
Feedback
