DB2 - Problem description
| Problem IT04372 | Status: Closed |
DB2DIAG.LOG FILLS WITH "UPDATING IN MEMORY VERSION OF DBM CONFIG WITH ON DISK INFORMATION (SYS PROFILE)" messages | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
Several messages might fill up db2diag.log file at a rapid rate.
These messages look like the following:
2014-09-10-13.40.49.571852+120 I1656E840 LEVEL:
Warning
PID : 10813 TID : 140737353987872 PROC
:db2fmd
INSTANCE: db2inst1 NODE : 000
HOSTNAME: machine1
FUNCTION: DB2 UDB, config/install, sqlfcsys, probe:10
MESSAGE : Updating in memory version of DBM config with on disk
information
(SYS PROFILE).
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x00007FFFF3413747 _Z8sqlfcsysP9sqlf_kcfdm + 0x227
[1] 0x00007FFFEE16D556 gcf_getstate + 0x1816
[2] 0x00007FFFF7224329
_ZN9GcfCaller8getStateEP12GCF_PartInfomP11GCF_RetInfo + 0x189
[3] 0x0000000000404ED1 _Z11fmMainLogicP6fmInfoh + 0x4C1
[4] 0x000000000040480C main + 0xD4C
[5] 0x00007FFFF62E6C16 __libc_start_main + 0xE6
[6] 0x0000000000403A29 __gxx_personality_v0 + 0x151
This does not have direct impact on the normal functioning of
the instance, but monitoring the db2diag.log for issues could
become very difficult. | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to version 10.5 Fix Pack 5 * **************************************************************** | |
| Local Fix: | |
Note that the process that is reported is the db2fm, so disabling the Fault manager might avoid the issue | |
| Solution | |
First fixed in version 10.5 Fix Pack 5 | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.09.2014 13.03.2015 13.03.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.5 |
|