|
Problem IT29428
|
Status: Closed |
LOG MESSAGES IN CLPBP_INSTALL_SIGNALS FLOODING THE DB2DIAG.LOG
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
When DB2_OBJECT_STORAGE_LOCAL_STAGING_PATH registry variable is
set, the following messages will be flooding the db2diag.log:
PID : 35012 TID : 47966864943104 PROC :
db2bp
INSTANCE: db2inst1 NODE : 000
HOSTNAME: host1
FUNCTION: DB2 UDB, command line process, clpbp_install_signals,
probe:1000
DATA #1 : Codepath, 8 bytes
0
DATA #2 : String, 0 bytes
Object not dumped: Address: 0x0000000000598D04 Size: 0 Reason:
Zero-length data
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00000000004A591E
_Z21clpbp_install_signalsPFviP7siginfoPvES3_S3_S3_ + 0x2BE
[1] 0x00000000004B46EC _Z11clp_bp_initPPc + 0x16C
[2] 0x00000000004A2CF0 main + 0x220
[3] 0x00002BA02D634B15 __libc_start_main + 0xF5
[4] 0x0000000000413889
/mnt/blumeta0/home/db2inst1/sqllib/bin/db2bp + 0x13889
This message is writing a zero length string and seems to be
tagged as an "EVENT" such that it shows up regardless of the
db2diag level. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Users on db2 v10.5 and v11.1 FP 4 and lower *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2 v11.1 Mod 4 FP5 *
**************************************************************** |
| Local Fix: |
db2 registry variable DB2_OBJECT_STORAGE_LOCAL_STAGING_PATH may
be turned off. |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.06.2019
03.01.2020
03.01.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
