Invalid object name MQ1CP001_u on FINALIZE_UPGRADE ZDU with MS SQL Alternative schema

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

During the ZDU wizard from version 24.4.0x to version 24.4.0+hf.2 using as database MS SQL Server with Alternative MQ Schema, the step FINALIZE_UPGRADE fails with the following errors:

20250523/155007.093 - U00011896 Zero_Downtime_Upgrade mode 'FINALIZE_UPGRADE' initiated. Start of server-table (name, type, MQSet, host, port):
...
20250523/155007.097 - U00016014 Zero Downtime information: 'Check the CP# connection: AESYSTEM#CP00X, this CP# mqset: 1, terminate mqset: 1'
20250523/155007.107 - U00029108 UCUDB: SQL_ERROR    Database handles  DB-HENV: 660d7180  DB-HDBC: 660d7260
20250523/155007.107 - U00003591 UCUDB - DB error info: OPC: 'SQLExecDirect' Return code: 'ERROR'
20250523/155007.107 - U00003592 UCUDB - Status: '42S02' Native error: '208' Msg: 'Invalid object name 'MQ1CP001_u'.'
20250523/155007.107 - U00003594 UCUDB Ret: '3590' opcode: 'SUCO' SQL Stmnt: 'SELECT COUNT(*)    DIVDB_Int4 FROM                 MQ1CP001_u'
20250523/155007.107 - U00003620 Routine 'UCMAIN_R' forces trace because of error.
20250523/155007.107 - U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR   ', '42S02', 'Invalid object name 'MQ1CP001_u'.'

Please note that depending which MQSet is the active one, the message could be something like "Invalid object name 'MQ2CP001_u" instead.

Environment

Automation Engine 24.4.0 or 24.4.0HF1 being upgraded via ZDU to 24.4.0HF2 with MS SQL Alternative MQ Schema.

Cause

DE170950

Resolution

Solution:

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

Fix version:
Component(s): Automation Engine
Automation.Engine 24.4.0 HF3 - Available
Automation.Engine 24.4.1 - Planned release July 2025

After the DBload to 24.4.0HF3 or superior the value of the query used for GET_TABLE_NAME will be updated accordingly so no need to do any manual edition of the database value, ZDU can be done as normal if this is the version used or superior.

We recommend NOT to use the ZDU to 24.4.0HF2 or inferior if using an alternative MQ database, instead pleaase upgrade to 24.4.0HF3 or superior.

Additional Information

Public Description: An issue was resolved where, during the final step of the ZDU process, we now check for any pending tasks in the message queue (MQ) before shutting down old processes, specifically when the user is using an alternative MQ database.