Hi All -
Running DB2 10.5 FP 8 on AIX 7.1.
I'm getting this error every few minutes
2017-12-21-05.59.50.374425-360 E154360A429 LEVEL: Error
PID : 51839300 TID : 2314 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000
HOSTNAME: p1proddb.vanhoof.com
EDUID : 2314 EDUNAME: db2tcpcm 0
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:2819 MESSAGE : DIA3202C The TCP/IP call "setsockopt(TCP_KEEPCNT)" returned an
errno="22".
Nothing has changed on the DB-side but I am told by one of the network guys that a windows NFS server 'moved' to a new location or was replaced by another server and then this started happening.
The IBM documentation sez it isn't a DB2 issue per-se but the error msgs are becoming tiresome and annoying.
Any ideas here? Anybody see this before?
-Bruce
On 12/21/2017 8:13 AM, bwmiller16@gmail.com wrote:
Hi All -
Running DB2 10.5 FP 8 on AIX 7.1.
I'm getting this error every few minutes
2017-12-21-05.59.50.374425-360 E154360A429 LEVEL: Error
PID : 51839300 TID : 2314 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000
HOSTNAME: p1proddb.vanhoof.com
EDUID : 2314 EDUNAME: db2tcpcm 0
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:2819 MESSAGE : DIA3202C The TCP/IP call "setsockopt(TCP_KEEPCNT)" returned an
errno="22".
Nothing has changed on the DB-side but I am told by one of the network guys that a windows NFS server 'moved' to a new location or was replaced by another server and then this started happening.
The IBM documentation sez it isn't a DB2 issue per-se but the error msgs are becoming tiresome and annoying.
Any ideas here? Anybody see this before?
-Bruce
As the IBM documentation states:
"Network and System Admins should investigate their networks and systems
to determine underlying root cause for the TCP troubles."
This is not a DB2 problem.
--
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
=============
On Thursday, December 21, 2017 at 9:40:03 AM UTC-5, Jerry Stuckle wrote:
On 12/21/2017 8:13 AM, bwmiller16@gmail.com wrote:
Hi All -
Running DB2 10.5 FP 8 on AIX 7.1.
I'm getting this error every few minutes
2017-12-21-05.59.50.374425-360 E154360A429 LEVEL: Error
PID : 51839300 TID : 2314 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
HOSTNAME: p1proddb.vanhoof.com
EDUID : 2314 EDUNAME: db2tcpcm 0
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:2819 >>> MESSAGE : DIA3202C The TCP/IP call "setsockopt(TCP_KEEPCNT)" returned an >>> errno="22".
Nothing has changed on the DB-side but I am told by one of the network guys that a windows NFS server 'moved' to a new location or was replaced by another server and then this started happening.
The IBM documentation sez it isn't a DB2 issue per-se but the error msgs are becoming tiresome and annoying.
Any ideas here? Anybody see this before?
-Bruce
As the IBM documentation states:
"Network and System Admins should investigate their networks and systems
to determine underlying root cause for the TCP troubles."
This is not a DB2 problem.
--
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex@attglobal.net
=============
Yes I understand that this isn't necessarily a DB2 Issue but the fact remains we're getting 100s of these a day and the volume of these is such its potentially masking out other issues.
So, it may not be DB2 caused but it affects DB2 and there doesn't seem to be a good reason or fix.
On Thursday, December 21, 2017 at 9:40:03 AM UTC-5, Jerry Stuckle wrote:^^^^^^^^
On 12/21/2017 8:13 AM, bwmiller16@gmail.com wrote:
Hi All -
Running DB2 10.5 FP 8 on AIX 7.1.
I'm getting this error every few minutes
2017-12-21-05.59.50.374425-360 E154360A429 LEVEL: Error
PID : 51839300 TID : 2314 PROC : db2sysc 0
INSTANCE: db2inst1 NODE : 000
HOSTNAME: p1proddb.vanhoof.com
EDUID : 2314 EDUNAME: db2tcpcm 0
[..]FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr_child, probe:2819 >> > MESSAGE : DIA3202C The TCP/IP call "setsockopt(TCP_KEEPCNT)" returned an >> > errno="22".
Yes I understand that this isn't necessarily a DB2 Issue but the fact
remains we're getting 100s of these a day and the volume of these is
such its potentially masking out other issues.
So, it may not be DB2 caused but it affects DB2 and there doesn't seem
to be a good reason or fix.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 128:19:41 |
Calls: | 6,734 |
Files: | 12,256 |
Messages: | 5,362,538 |