DB Archive fails after upgrade to v24 with ORA-01406: fetched column value was truncated

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

After the upgrade from v21 to v24 an error occurs running the DB Archive Utility:

20250811/130712.775 - U00003525 UCUDB: ===> 'SELECT COUNT(*) DIVDB_INT4 FROM  Meld where Meld_ArchiveFlag = 0 and Meld_DeleteFlag = 0 and Meld_Client = ? and ((MELD_TimeStamp < ? AND MELD_Seen = 1) or (MELD_TimeStamp < ? AND MELD_Seen = 0))'
20250811/130713.432 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 1ebebd0  DB-HDBC: 1f395a0
20250811/130713.432 - U00003591 UCUDB - DB error info: OPC: 'OCIStmtFetch' Return code: 'ERROR'
20250811/130713.432 - U00003592 UCUDB - Status: '' Native error: '1406' Msg: 'ORA-01406: fetched column value was truncated'
20250811/130713.432 - U00003590 UCUDB - DB error: 'OCIStmtFetch', 'ERROR   ', '', 'ORA-01406: fetched column value was truncated'
20250811/130713.432 - U00033122 Error occurred in function <ProcessArchiveAH> 
MsgNr: <0> MsgInsert: <> Additional info: <>
20250811/130713.432 -  |

Cause

Oracle VARCHAR2 fields are defined by character count, not byte count. Before the UTF-8 encoding was introduced in v24, a VARCHAR2(32) column could store 32 characters represented as single bytes (e.g., 32 'ö' characters occupying 32 bytes). In UTF-8, some characters are represented by multiple bytes, leading to this issue.

Resolution

Solution:

Update to a fix version listed below or a newer version if available.

Fix version:

Component(s): Utilities

Automation.Engine 24.4.2 HF1 - Available
Automation.Engine 24.4.3 - planned release December 2025

Additional Information

The reference for this fix is DE174501