IBM Support

IT34883: INTERMITTENT GSKIT ERROR 17 OR GSKIT ERROR 106 FROM DB2 CLIENTS WHEN USING SSL

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

  • When SSL connections are being made from a Db2 client, the
    connection may intermittently fail with a "GSKit Error: 17" or a
    "GSKit Error: 106".
    
    The error message returned to the command line will look similar
    to the following:
    
    [IBM][CLI Driver] SQL10013N  The specified library "GSKit Error:
    17" could not be loaded.  SQLSTATE=42724
    
    
    The db2diag.log may also contain messages similar to the
    following:
    
    2020-11-06-11.48.02.142805-300 I474735138E413        LEVEL:
    Error
    PID     : 10207                TID : 140551623571328 PROC :
    db2cli
    INSTANCE: regress1             NODE : 000
    HOSTNAME:
    FUNCTION: DB2 UDB, common communication,
    sqlccMapSSLErrorToDB2Error, probe:261
    MESSAGE : DIA3604E The SSL function "GSKKM_OpenKeyDbData" failed
    with the
              return code "17" in "sqlccCreateDefaultKeyDB".
    
    
    2020-11-06-11.48.02.196035-300 I474745064E413        LEVEL:
    Error
    PID     : 10207                TID : 140551623571328 PROC :
    db2cli
    INSTANCE: regress1             NODE : 000
    HOSTNAME:
    FUNCTION: DB2 UDB, common communication,
    sqlccMapSSLErrorToDB2Error, probe:530
    MESSAGE : DIA3604E The SSL function "gsk_environment_init"
    failed with the
              return code "106" in "sqlccEnvironmentInitCommon".
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All DB2 clients on all Linux, Unix and Windows platforms at  *
    * service levels Version 11.1 GA through to Version 11.1.4 Fix *
    * Pack 5                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 11.1.4 Fix Pack 6 or higher.          *
    ****************************************************************
    

Problem conclusion

  • The complete fix for this problem first appears in DB2 Version
    11.1.4 Fix Pack 6 and all subsequent Fix Packs.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34883

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-11

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

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

    IT34882

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
01 April 2021