IBM Support

IC88244: ADD RETRY WHEN DB2 RECEIVES WSAEACCESS WHEN BINDING TCP SERVICE PORT IN WINDOWS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users who use DB2 on Windows platforms.                      *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to V9.7 FixPack 8 or later.                   *
    ****************************************************************
    

Problem conclusion

  • This problem was first fixed in DB2 V9.7 FixPack 8.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC88244

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-14

  • Closed date

    2013-04-22

  • Last modified date

    2013-04-22

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IC91756

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
22 April 2013