|
Problem IT31679
|
Status: Closed |
DURING DB2START, "SETTING NON-SHARD SQLLIB" MESSAGE IS STILL ADDED TO DB2DIAG.LOG IN THE DEFAULT DIAGPATH
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem 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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.5.4.0 or higher *
**************************************************************** |
| 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. |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT24179
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.01.2020
30.06.2020
30.06.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
