IBM Support

IT24179: DURING DB2START, "SETTING NON-SHARD SQLLIB" MESSAGE IS STILL ADDED TO DB2DIAG.LOG IN THE DEFAULT DIAGPATH

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

  • Even after changing DIAGPATH from the default value, "Setting
    non-shard sqllib" message is still added to db2diag.log located
    in the default DIAGPATH where is different from the current
    DIAGPATH during db2start operation as below.
    
      This "Setting non-shard sqllib" message is just an information
    message and the newly created db2diag.log file in the default
    DIAGPATH can be safely ignored and deleted.
    
    2018-01-29-13.05.09.492043+540 I1579A303            LEVEL: Event
    PID     : 26607646             TID : 1              PROC :
    db2star2
    INSTANCE: db2inst3             NODE : 000
    HOSTNAME: hostname
    EDUID   : 1
    FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:3230
    MESSAGE : Setting non-shared sqllib
    

Local fix

  •   The "Setting non-shard sqllib" message and the newly created
    db2diag.log file in the default DIAGPATH can be safely ignored
    and deleted.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 11.1 Modification 4 FixPack 6 or      *
    * later                                                        *
    ****************************************************************
    

Problem conclusion

  • Fixed in DB2 Version 11.1 Modification 4 FixPack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT24179

  • 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

    2018-02-22

  • Closed date

    2021-03-12

  • Last modified date

    2021-03-12

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

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

    IT31679

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:
13 March 2021