IMC06 error causes RWP loop on MS SQL database connection loss

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Introduction

On Automic Automation Engine systems using MS SQL Server, the Resource Work Process (RWP) may enter a rapid, tight loop following a database connectivity failure. Instead of exiting or attempting a standard 10-second reconnect, the process repeatedly attempts database calls, causing job reporting to stop and preventing successor jobs from starting.

Symptoms

• The RWP process shows high CPU usage or logs messages multiple times per second.
• Job reports are not processed, and system activity halts.
• The Work Process log contains the following error: 
U00003592 UCUDB - Status: 'IMC06' Msg: 'The connection is broken and recovery is not possible.'

Environment

• Automic Automation Engine 24.x
• Database: Microsoft SQL Server
• ODBC Connection strings using ConnectRetryCount or ConnectRetryInterval settings.

Cause

This issue has been investigated under DE184853:

The Automation Engine (specifically the ucudb32 module) evaluates database error codes to determine if a connection is lost. For MS SQL Server, IMC* class errors can return an error code of 0. Because the system interprets code 0 as success or a non-fatal deadlock, it enters an immediate retry loop rather than triggering the standard 10-second reconnection logic.

Resolution

Short-term Workaround

1. Identify the Work Process (WP) currently holding the R (Resource) role in the Administration perspective.
2. Terminate (kill) the specific looping WP process.
3. Another available WP will automatically assume the R role and resume processing.

Long-term Workaround

Remove the following reconnection parameters from the ODBC connection string in the ucsrv.ini file:

• ConnectRetryCount
• ConnectRetryInterval

Allowing the Automation Engine to handle reconnections natively (defaulting to 10-second intervals) prevents the rapid loop behavior.

Fixed Version

This issue is targeted to be fixed in a future release via defect DE184853.

Subscribe to this article to be updated on the fix status. For more information, see How to register for Product updates.

If further assistance is required, please Contact Broadcom Support.