Forced traces generated continuously - 'AH_Idnr' with value 0 in module 'UCVAREXR'

book

Article ID: 221206

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

We are getting Forced Traces continuously on our system.

Our file system is running out of storage issue because of these traces.

The forced traces are generated in pairs, the first of the two contains the following error: 

20210728/185733.882 - UCVAREXR       RCV CHGLOGR frm <AGENT>                MQ1CP011 MsgID: 0454198642 c-acv: 00000000
20210728/185733.884 -  STRT UCUMIGR    OPC: 00002
20210728/185733.884 -  EXIT UCUMIGR    RET: 0000000000 TIME: 0000,00000 RETTEXT=' '
20210728/185733.884 - U00009909 TRACE: (BINDPAR: AH_Idnr      9001000a4bd2ce8 00004
                00000000 00000000               <....>
20210728/185733.884 -                     <0>
20210728/185733.884 - SELECT AH.*,ROWID FROM AH WHERE AH_Idnr = ? FOR UPDATE
20210728/185733.885 - UCUDB32 SLCU RET 0000 HSTMT: 0000000112bed030 VALUE: 0000000112bed030 ALL: 0.00160 DB: 0.00119 ODBC: 0.00017 UDB: 0.00025
20210728/185733.885 - UCUDB32 READ RET 0001 HSTMT: 0000000112bed030 VALUE: 0000000000000000 ALL: 0.00003 DB: 0.00003 ODBC: 0.00000 UDB: 0.00000
20210728/185733.886 - UCUDB32 CLST RET 0000 HSTMT: 0000000112bed030 VALUE: 0000000000000000 ALL: 0.00010 DB: 0.00000 ODBC: 0.00008 UDB: 0.00002
20210728/185733.886 - U00003620 Routine 'UCVAREXR' forces trace because of error.
20210728/185733.886 - U00005118 Program error: Database access via key 'AH_Idnr' with value 0 in module 'UCVAREXR'.

Cause

This is a bug

Environment

Release : 12.3.3 HF5

Component : AUTOMATION ENGINE

Resolution

Workaround:

Restarting the agent in the error message stops the Forced Traces.

 

Solution:

Issue has been qualified as a bug, a fix will be delivered in a future version.