|
Problem IT29781
|
Status: Closed |
SQLGETCONNECTATTR() FUNCTION CALL WITH SQL_ATTR_GET_LATEST_MEMBER_NAME TAKING TIME DUE TO GETADDRINFO TAKING MORE TIME
|
| product: |
DB2 CONNECT / DB2CONNCT / B10 - DB2 |
| Problem 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 |
| 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 *
**************************************************************** |
| Local Fix: |
Use the IP address or put the hostname to ip resolution in
/etc/hosts |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner :
follow-up : IT33421 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.07.2019
23.02.2020
23.02.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
