|
Problem IT27223
|
Status: Closed |
SLOWNESS WHEN USING THE DB2DSDRIVER.CFG FROM NFS LOCATION
|
| product: |
DB2 CONNECT / DB2CONNCT / B10 - DB2 |
| Problem description: |
When ODBC and CLI application referring the db2dsdriver.cfg
located in the NFS file system and using the
DB2DSDRIVER_CFG_PATH to
specify the location, application is witnessing the
slowness the application.
This is witnessed when API SQLGetConnectAttrW when
called with "SQL_ATTR_GET_LATEST_MEMBER_NAME ".
This API call with SQL_ATTR_GET_LATEST_MEMBER_NAME
checks for the db2dsdriver.cfg exitance for its
each call.
In the system trace(strace) we will see trace like below:
lseek(11, 1608756, SEEK_SET) = 1608756
stat("/usr/sap/R50/SYS/global",
{st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
access("/usr/sap/R50/SYS/global/db2dsdriver.cfg",
F_OK) = 0
open("/usr/sap/R50/SYS/global/db2dsdriver.cfg",
O_RDONLY) = 23
close(23) = 0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ODBC AND CLI , DSDriver and Runtime clients *
****************************************************************
* PROBLEM DESCRIPTION: *
* Slowness when using the db2dsdriver.cfg from NFS location *
* *
* Description: When ODBC and CLI application referring the *
* db2dsdriver.cfg *
* located in the NFS file system and using the *
* DB2DSDRIVER_CFG_PATH to *
* specify the location, application is witnessing *
* the slowness the application. *
* This is witnessed when API SQLGetConnectAttrW *
* when called with "SQL_ATTR_GET_LATEST_MEMBER_NAME ". *
* This API call with *
* SQL_ATTR_GET_LATEST_MEMBER_NAME checks for the *
* db2dsdriver.cfg exitance for its *
* each call. *
* *
* In the system trace(strace) we will see trace like *
* below: *
* *
* lseek(11, 1608756, SEEK_SET) = 1608756 *
* stat("/usr/sap/R50/SYS/global", *
* {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 *
* access("/usr/sap/R50/SYS/global/db2dsdriver.cfg", *
* F_OK) = 0 *
* open("/usr/sap/R50/SYS/global/db2dsdriver.cfg", *
* O_RDONLY) = 23 *
* close(23) = 0 *
* *
* Workaround : Don't use the DB2DSDRIVER_CFG_PATH to specify *
* the db2dsdriver.cfg file, *
* instead put in the *
* /cfg/ *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v111m4fp5/Vnext *
**************************************************************** |
| Local Fix: |
Don't use the DB2DSDRIVER_CFG_PATH to specify the
db2dsdriver.cfg file,
instead put in the /cfg/ |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.12.2018
04.06.2019
04.06.2019 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
