DB Archive fails after v21 to v24 upgrade
search cancel

DB Archive fails after v21 to v24 upgrade

book

Article ID: 405837

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

The DB Archive fails with this error on an ACT report:

20250602/092639.555 - U00009909 TRACE: (BINDPAR:  RT_AH_Idnr        )                                          0x7f3cfb7b1d44 000004
                              00000000  31AFF100                             >1...<
20250602/092639.555 -                                        >15839025<
20250602/092639.555 - U00009909 TRACE: (BINDPAR:  RT_Type           )                                          0x7f3cfb7b1d48 000003
                              00000000  414354                               >ACT<
20250602/092639.555 - Select RT_MsgNr, RT_MsgInsert, RT_TimeStamp, RT_Content from RT where RT_AH_Idnr = ? and RT_Type = ? order by RT_Lnr ASC
20250602/092639.558 - UCUDB32 SLCT RET 0000 HSTMT: 0x000000011ba9d0 VALUE: 0x00000000000032 ALL:  0.00316 DB:  0.00302 ODBC:  0.00000 UDB:  0.00014
20250602/092639.560 - U00003592 UCUDB - Status: '' Native error: '24345' Msg: 'ORA-24345: A Truncation or null fetch error occurred'
20250602/092639.560 - U00029134 UCUDB: Memory of length '1' has been assigned to clob or blob field 'RT_Content(2b86d40,7f3cfb758020,7f3cfb763d18)'.
<...>
                              000003B0  61766161 67656E74 2E6A6172 3C62723E  >avaagent.jar<br><
                              000003C0  32303235 30353331 2F303331 3133322E  >20250531/031132.<
                              000003D0  30303020 2D205530 30303230 34303820  >000 - U00020408 <
                              000003E0  50617261 6D657465 72732073 7472696E  >Parameters strin<
                        000003F0  673A2020 2D2D7275 6E496420 27323032  >g:  --runId '202<
20250602/092639.564 - U00009909 TRACE: (DB-DATEN: RT_TimeStamp      )                                          0x7f3cfb7b1d54 000016
                              00000000  E9070500 1F000300 11002100 00000000  >..........!.....<
20250602/092639.564 -                                        >2025.05.31 03:17:33.0<
20250602/092639.564 - U00009909 TRACE: (DB-DATEN: RT_Content        )                                          0x2b86d40 000000
20250602/092639.564 - UCUDB32 READ RET 0000 HSTMT: 0x000000011ba9d0 VALUE:            (nil) ALL:  0.00010 DB:  0.00000 ODBC:  0.00000 UDB:  0.00010
20250602/092639.564 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 107b9a0  DB-HDBC: 10f6e20
20250602/092639.564 - U00003591 UCUDB - DB error info: OPC: 'OCIStmtFetch' Return code: 'ERROR'
20250602/092639.564 - U00003592 UCUDB - Status: '' Native error: '24345' Msg: 'ORA-24345: A Truncation or null fetch error occurred'
20250602/092639.565 - UCUDB32 READ RET 3590 HSTMT: 0x000000011ba9d0 VALUE:            (nil) ALL:  0.00007 DB:  0.00000 ODBC:  0.00000 UDB:  0.00007
20250602/092639.565 - U00003590 UCUDB - DB error: 'OCIStmtFetch', 'ERROR   ', '', 'ORA-24345: A Truncation or null fetch error occurred'
20250602/092639.565 - DB-OPC: CLSTA    DB-RET: 0 HSTMT: 0x000000011ba9d0 VALUE:            (nil)
20250602/092639.565 - UCUDB32 CLAL RET 0000 HSTMT: 0x000000011ba9d0 VALUE:            (nil) ALL:  0.00004 DB:  0.00000 ODBC:  0.00002 UDB:  0.00003
20250602/092639.567 - UCUDB32 CMIT RET 0000 HSTMT:            (nil) VALUE:            (nil) ALL:  0.00222 DB:  0.00221 ODBC:  0.00000 UDB:  0.00002
20250602/092639.567 - U00033122 Error occurred in function <ProcessArchiveRH>
MsgNr: <0> MsgInsert: <> Additional info: <>
20250602/092639.567 -  |

The fetched data is displayed in the trace file and ends with the line above in bold; however, the actual RT content continues when querying the RunID and report type.

 

When trying to download the ACT report, AWI also displays a pop-up error:

Runtime error in object 'XREPORT_BLOCK(GET)', line '00150': DS-Return code: '0000003590': 'U00003590 UCUDB - DB-Error: OCIStmFetch', 'ERROR', ", 'ORA-01403: no data found", Error in UCDSFUN and Position: 'DS_DB2XML_REPORT5'. 

 

Environment

ucybdbar version '24.4.0+build.1741626183548

Cause

This is an issue related to the UTF-8 migration.

Resolution

Solution:

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


Fix version:

Component(s): DB Archive Utility (ucybdbar)

Automation.Engine 24.4.1 HF2 - Available
Automation.Engine 24.4.2 - Available

Additional Information

The references for this fix are DE171603 and DE171583.

Also see: https://broadcomcms-software.wolkenservicedesk.com/external/article?articleNumber=404189