U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR', 'HY000', 'The connection is busy with results of another command'
search cancel

U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR', 'HY000', 'The connection is busy with results of another command'

book

Article ID: 254982

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

Installation on Windows&MSSQL
Upon start-up WP initializes and connects normally - No issues observed - MQSRV table has the WP listed
Upon start-up of JCP the WPs start generating continuous trace files - Although no errors observed in the JCP logs.
Note: Both WP and JCP process does not terminate unless manually killed.

Expected Behavior: Forced Traces should not be generated upon starting JCP
Actual Behavior: Traces are being generated and the trace files continously increment untill the process is terminated manually

Below error is observed in the WP logs and forced traces.

[DE]U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR ', 'HY000', 'Die Verbindung ist mit Ergebnissen eines anderen Befehls beschäftigt'

[EN]U00003590 UCUDB - DB error: 'SQLExecDirect', 'ERROR', 'HY000', 'The connection is busy with results of another command'

 

Environment

Release : 21.0.4

Component: Automation Engine 

Cause

This happens if your using MSSQL database and the ODBC connection string uses 1. Position = N - Do not use server cursor. (example below)

sqlDriverConnect=ODBCVAR=NNNNNNRN,DSN=???;UID=???;PWD=???

The issue has been confirmed to be a bug by our Dev team.

Resolution

Workaround:

Change the connection string to use 1. Position = S - Use server cursor (MS SQL Server 2000) instead of 1. Position = N - Do not use server cursor (example below)

1) sqlDriverConnect=ODBCVAR=SNNNNNRN,DSN=???;UID=???;PWD=???

or 

2) sqlDriverConnect=ODBCVAR=NNNNNNRN,DSN=???;UID=???;PWD=???;Mars_Connection=Yes

 

Solution:

The issue has been fixed with the Automation Engine component release 21.0.5