Error: ERRORCODE=-4461 when using SQL Agent with DB2 TLS connections.

Products

• CA Automic Workload Automation - Automation Engine
• Automic SaaS

Issue/Introduction

When configuring an IBM DB2 connection for TLS in the SQL Agent, jobs fail with a syntax error. 

Symptoms: Job logs show the following error: 

[jcc][10165][10036][4.27.25] Invalid database URL syntax: jdbc:db2://server:1234/dbname;sslConnection=true. ERRORCODE=-4461, SQLSTATE=42815

Environment

• SQL Agent 24.4.4
• IBM DB2
• TLS/SSL Connection enabled via Advanced Options

Cause

This is caused by a defect in the SQL Agent string assembly logic. The agent incorrectly uses a semicolon (;) as the initial boundary between the database name and the connection properties (e.g., ssiConnection=TRUE). Per IBM DB2 Type 4 JDBC specifications, a colon (:) is required as the separator for the first parameter.

Resolution

This issue is a known defect (DE208680).

Fix Status: 

Targeted to be fixed in Automation.Engine 24.4.6 - TBA and 26.1.0 -TBA

Workaround: To resolve this immediately, bypass the "Advanced Options" tab and manually format the connection string:

1. Open the DB2 Connection Object.
2. Remove all parameters from the Advanced Options tab.
3. In the Database Name field, append the required parameters directly to the name, starting with a colon (:).
   • Format: ####:sslConnection=true;
   • Example: MYDBNAME:sslConnection=true;
4. Save the object and re-execute the job.

Subscribe to this article to be updated on the fix status. For more information, see How to subscribe to a Knowledge Article.

Additional Information

For official IBM URL format specifications, refer to the IBM Documentation.