|
Problem IC91756
|
Status: Closed |
ADD RETRY WHEN DB2 RECEIVES WSAEACCESS WHEN BINDING TCP SERVICE PORT IN WINDOWS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The db2start might report SQL5043N, and db2diag.log indicates
the error is caused by WSAEACCESS (10013) on bind() call.
2012-10-12-23.15.30.047000+540 I70203F367 LEVEL: Error
PID : 1092 TID : 3548 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000
EDUID : 3548 EDUNAME: db2sysc 0
FUNCTION: DB2 UDB, common communication, sqlcctcpconnmgr,
probe:47
MESSAGE : DIA3202C The TCP/IP call "bind" returned an
errno="10013".
The following Microsoft page says DB2 can receive WSAEACCESS in
Windows Server 2003 or later. If the service port has been used
by some other process, and it specifies SO_EXCLUSIVEADDRUSE
socket option on the port.
Using SO_REUSEADDR and SO_EXCLUSIVEADDRUSE
http://msdn.microsoft.com/en-us/library/windows/desktop/ms740621
%28v=vs.85%29.aspx
Also, ephemeral port range is started with 49152 in Windows
Vista or later, and this change increases the chances to
conflict ephemeral port with default DB2 service port (50000).
DB2 already has a retry logic when bind fail with WSAEADDRINUSE,
and this APAR will treat WSAEACCESS as same as WSAEADDRINUSE
when binding service port. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who use DB2 database server on Windows. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to FixPack 3 or later. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
This problem was first fixed in DB2 V10.1 FixPack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 22.04.2013
08.10.2013
08.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
