SQL JOB fails with IO Error: Socket read timed out
search cancel

SQL JOB fails with IO Error: Socket read timed out


Article ID: 241111


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic One Automation


A SQL job object that runs a query on a database using a SQL connection object occasionally fails with this "socket read time out" error message:

2022-04-15 15:30:09 - U02012031 The database driver returned the following error message:
2022-04-15 15:30:09 IO Error: Socket read timed out
2022-04-15 15:30:09 - U02004025 Job-script execution was aborted.

4/15/2022 03:30:09 PM
U00011003 Job 'SQL.JOB.NAME' (RunID '0017814985') on Host 'SQL_AGENT_NAME' aborted (return code='0102'). Remote status=Waiting for Database

Execution history of when this job fails fails with a timeout always after the same amount of time such as a minute.


Release : 12.3

Component : Database agent


This is due to settings on the database.  There is either a timeout set or something else that is blocking connections to the database from remote servers.  

In one case, there was a month end processes that caused a heavy load on the db and so the db was set up to no longer allow new connections that would add to stress, so it timed them all out.