DB2 - Problem description
Problem IT07975 | Status: Closed |
REDUCE SEVERITY OF DB2DIAG MESSAGES WHEN DISABLING FAULT MONITOR ING(FM) VIA DB2FM FOR AN INSTANCE THAT DOES NOT HAVE FM ENABLED | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
The following two db2diag.log error messages are logged when running the "db2fm -i <instname> -D" command to stop the fault monitor daemon in the case where the fault monitor daemon is already stopped: $ db2fm -S Gcf module 'fault monitor' is NOT operable $ ./sqllib/bin/db2fm -i db2inst1 -D ./sqllib/bin/db2fm return non-zero rc, please see log file '/work/db2users/db2inst1/sqllib/db2dump/db2diag.log' $ db2diag ... 2015-02-25-16.26.36.137650+540 I8171477E951 LEVEL: Error PID : 9236 TID : 47081699212400PROC : db2fm INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:60 MESSAGE : ECF=0x90000390=-1879047280=ECF_FM_INVALID_PROCESS_ID Invalid process id CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x00002AD20D483197 pdOSSeLoggingCallback + 0x265 [1] 0x00002AD20C4711F6 /opt/ibm/db2/V9.7/lib64/libdb2osse.so.1 + 0x1D91F6 [2] 0x00002AD20C472A40 ossLog + 0xD4 [3] 0x00002AD2101C6C3A gcf_stop + 0x364 [4] 0x00002AD20CB7BFE1 _ZN9GcfCaller4stopEP12GCF_PartInfomP11GCF_RetInfo + 0x1B9 [5] 0x0000000000406861 main + 0x25E9 [6] 0x00000030FAE1D994 __libc_start_main + 0xF4 [7] 0x00000000004041E9 __gxx_personality_v0 + 0x151 [8] 0x0000000000000000 ?unknown + 0x0 [9] 0x0000000000000000 ?unknown + 0x0 2015-02-25-16.26.36.144505+540 I8172429E1057 LEVEL: Error PID : 9236 TID : 47081699212400PROC : db2fm INSTANCE: db2inst1 NODE : 000 FUNCTION: DB2 Common, Fault Monitor Facility, db2fm, probe:170 MESSAGE : ECF=0x90000349=-1879047351=ECF_FM_FAIL_TO_STOP_GCF_FM Failed to stop the GCF fm module CALLED : DB2 Common, Generic Control Facility, GcfCaller::stop DATA #1 : signed integer, 8 bytes 1 DATA #2 : unsigned integer, 8 bytes 0 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x00002AD20D483197 pdOSSeLoggingCallback + 0x265 [1] 0x00002AD20C4711F6 /opt/ibm/db2/V9.7/lib64/libdb2osse.so.1 + 0x1D91F6 [2] 0x00002AD20C47290B ossLogRC + 0xBF [3] 0x00000000004068F4 main + 0x267C [4] 0x00000030FAE1D994 __libc_start_main + 0xF4 [5] 0x00000000004041E9 __gxx_personality_v0 + 0x151 [6] 0x0000000000000000 ?unknown + 0x0 [7] 0x0000000000000000 ?unknown + 0x0 [8] 0x0000000000000000 ?unknown + 0x0 [9] 0x0000000000000000 ?unknown + 0x0 The logging severity of the above two db2diag.log messages will be reduced to Info and Warning levels respectively. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 fault monitor user * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 Version 10.5 FixPack 7 or higher * **************************************************************** | |
Local Fix: | |
N/A | |
Solution | |
Problem was first fixed in Version 10.5 FixPack 7 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.03.2015 20.01.2016 20.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |