IBM Support

IT29781: SQLGETCONNECTATTR() FUNCTION CALL WITH SQL_ATTR_GET_LATEST_MEMBER_NAME TAKING TIME DUE TO GETADDRINFO TAKING MORE TIME

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • SQLGetConnectAttrW api  with SQL_ATTR_GET_LATEST_MEMBER_NAME
    option takes upto 6ms while it takes .4 ms or even lesser in
    good case.
    
    [1561643972.281175 - 06/27/2019 13:59:32.281175]
    49715	SQLGetConnectAttrW( hDbc=0:1,
    fOption=SQL_ATTR_GET_LATEST_MEMBER_NAME,
    pvParam=&0fffffffffff5910, cbParamMax=64,
    pcbParam=&0fffffffffff5840 )
    
    [1561643972.287257 - 06/27/2019 13:59:32.287257]
    SQLGetConnectAttrW( pvParam="MLT3", pcbParam=8 )
    49826    <--- SQL_SUCCESS   Time elapsed - +6.091000E-003 secon
    
    The delay is due to using the hostname in the affinitylist in
    the db2dsdriver.cfg file.
    CLI driver call sthe getaddrinfo() api to convert the host name
    to IP address and comapre with the
    current connected member ip. getaddrinfo() is taking more time.
    

Local fix

  • Use the IP address or put the hostname to ip resolution in
    /etc/hosts
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DB2 CLI users calling the SQL_ATTR_GET_LATEST_MEMBE          *
    * attribute.                                                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * The issue will be delivered in v11.m4fp5                     *
    ****************************************************************
    

Problem conclusion

  • DB2 v11.1m4fp5 will contain the fix, which avoids calling the
    getaddrinfo().
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT29781

  • Reported component name

    DB2 CONNECT

  • Reported component ID

    DB2CONNCT

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-07-19

  • Closed date

    2020-02-23

  • Last modified date

    2020-02-23

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

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

    IT33421

Fix information

  • Fixed component name

    DB2 CONNECT

  • Fixed component ID

    DB2CONNCT

Applicable component levels

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"11.1","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
04 July 2020