IBM Support

IT27223: SLOWNESS WHEN USING THE DB2DSDRIVER.CFG FROM NFS LOCATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error 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
    

Local fix

  • Don't use the DB2DSDRIVER_CFG_PATH to specify the
    db2dsdriver.cfg file,
    	                instead put in the <clidriver_location>/cfg/
    

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                          *
    * <clidriver_location>/cfg/                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to v111m4fp5/Vnext                                   *
    ****************************************************************
    

Problem conclusion

  • Slowness when using the db2dsdriver.cfg from NFS location
    
    The fix will be delivered in v111m4fp5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT27223

  • 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

    2018-12-06

  • Closed date

    2019-06-04

  • Last modified date

    2019-06-04

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

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

Fix information

  • Fixed component name

    DB2 CONNECT

  • Fixed component ID

    DB2CONNCT

Applicable component levels

  • RB10 PSN

       UP

  • RB10 PSY

       UP

[{"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:
14 December 2020