Troubleshooting
Problem
Messages in db2diag.log on connections being abort error - DIA3208E.
Symptom
Some workstations unable to connect to DB2.
Cause
Security / firewall policies prevent connections to remote host / port.
Environment
All environments.
Diagnosing The Problem
The following messages will appear in db2diag.log :
2016-10-06-13.20.23.494437+540 I28423822A454 LEVEL: Error
PID : 12124262 TID : 2571 PROC : db2sysc 0
INSTANCE: db2inst NODE : 000
HOSTNAME: hostname
EDUID : 2571 EDUNAME: db2tcpcm 0
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:105
MESSAGE : DIA3208E Error encountered in TCP/IP protocol support. TCP/IP
function "accept". Socket was "8". Errno was "72".
on AIX , errno 72 is "ECONNABORTED Software caused connection abort". DB2 engine get errno 72 during the system 'accept' call.
This happens during a TCP/IP "three-way handshake" when trying to establish a connection.
The following event should happen for a normal connection setup:
1 - client sends a SYN packet to initiate a connection
2 - server replies with ACK and SYN
3 - client sends a ACK to acknowledge the server SYN
4 - server calls the 'accept' system call to establish the file handle for communication
However, in this case, the client sends a RST packet to the server between step 3 and step 4. This would be interpreted as client aborting the connection.
This is not a DB2 defect. It is merely responding to network events from the client.
Most likely, you may have some security or monitoring tool that is killing the connection. You will need to engage your security team to examine the configuration and all the packets to pass through.
Resolving The Problem
Engage your system administrator to isolate and temporarily turn off security tools to verify, and reconfigure the security tool if necessary.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21992722