Using data integrator for ETL's pulling data from DB2 to SQL Server, after some time, will get these odbc errors:
Communication link failure. comm
rc=10055 – CWBCO1003 – Sockets error,
function returned 10055
Can't do anything with ODBC after that, have to reboot the box, and currently we just reboot the box every night at midnight to try to avoid the issue from happening.
Tried this, http://support.microsoft.com/kb/196271 but it didn't work, almost made it worse.
There doesn't seem to be a solution in sight. No other boxes that use ODBC get this issue that we use. Can't reformat the box at this time, legacy stuff on it.
Has anyone seen this issue, come across it, fixed it, mitigated it?
Best Answer
Certainly a low-memory condition, possibly caused by the extremely common mistake of not closing DB connections. My recommendations are:
If you do see the DB servers reporting a high number of idle connections in #3 you may be able to mitigate the problem by writing scripts to actively shutdown unused connections from the server side of the socket.