hi,

In our prod envi db2 server is getting rebooted, Os team is confirming that it is because of db2, and when i check the logs of db2 i could see this error stating GCF is failed

[db2inst1@WESSSTDW01 ~]$ less /home/db2inst1/sqllib/db2dump/db2diag.log
CALLED : DB2 Common, Generic Control Facility, gcf_reset
RETCODE : ECF=0x90000298=-1879047528=ECF_GCF_FAILURE
Failure as reported through GCF standard (GCF_FAILURE)
CALLSTCK:
[0] 0x00002B706A63D0A8 pdOSSeLoggingCallback + 0x100
[1] 0x00002B70696BE30C /opt/ibm/db2/V9.7/lib64/libdb2osse.so.1 + 0x1B230C
[2] 0x00002B70696BF9CD ossLogRC + 0x6B
[3] 0x00002B7069D8E2F4 _ZN9GcfCaller8getStateEP12GCF_PartInfomP11GCF_RetI nfo + 0x11A
[4] 0x000000000040586E main + 0x1676
[5] 0x0000003F3E61D994 __libc_start_main + 0xF4
[6] 0x0000000000404169 __gxx_personality_v0 + 0x149
[7] 0x0000000000000000 ?unknown + 0x0
[8] 0x0000000000000000 ?unknown + 0x0
[9] 0x0000000000000000 ?unknown + 0x0

2012-01-04-09.36.48.976256+330 I30335106E995 LEVEL: Error
PID : 18615 TID : 47761862511152PROC : db2fm
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 Common, Fault Monitor Facility, db2fm, probe:180
MESSAGE : ECF=0x9000034B=-1879047349=ECF_FM_FAIL_TO_GETSTATE_GCF_FM
Failed to get the state of the GCF fm module
CALLED : DB2 Common, Generic Control Facility, GcfCaller::getState
DATA #1 : signed integer, 8 bytes
-1879047540
DATA #2 : unsigned integer, 8 bytes
0
CALLSTCK:
[0] 0x00002B706A63D0A8 pdOSSeLoggingCallback + 0x100
[1] 0x00002B70696BE30C /opt/ibm/db2/V9.7/lib64/libdb2osse.so.1 + 0x1B230C
[2] 0x00002B70696BFA21 ossLogRC + 0xBF
[3] 0x0000000000405976 main + 0x177E
[4] 0x0000003F3E61D994 __libc_start_main + 0xF4
[5] 0x0000000000404169 __gxx_personality_v0 + 0x149
[6] 0x0000000000000000 ?unknown + 0x0
[7] 0x0000000000000000 ?unknown + 0x0
[8] 0x0000000000000000 ?unknown + 0x0
[9] 0x0000000000000000 ?unknown + 0x0

Kindly advice how to overcome ...

This is fault monitor, either you can try to increase timeout

db2fm -i <instance> -I /# (# is some numerical value, try setting to 60, I believe it's in seconds)

Or, you can disable it,

https://www-304.ibm.com/support/docv...id=swg21224009

hi amit thanks for your response,

before setting how do i check the current value ?

Also i could see
"Unable to find donor to satisfy minSize constraint" in the diaglog.

I believe default timeout is 20 sec.

"Unable to find donor to satisfy minSize constraint" , this is related to STMM.
A little bit detailed logs, and dbm/db configuration might help. And what operation you were doing when these errors got logged in diag.log ?

Activity performed during this time is "we have lot of scripts running"
The error is repeating continously

"2012-01-04-12.51.13.143115+330 I4987121E490 LEVEL: Warning
PID : 22015 TID : 47384742586688PROC : db2sysc
INSTANCE: db2inst1 NODE : 000 DB : WAREHOUS
APPHDL : 0-70 APPID: *LOCAL.DB2.120103112723
AUTHID : DB2INST1
EDUID : 83 EDUNAME: db2stmm (WAREHOUS)
FUNCTION: DB2 UDB, Self tuning memory manager, stmmEnforceMinSizeConstraints, probe:2358
MESSAGE : Unable to find donor to satisfy minSize constraint"

And the paramter for db cfg /dbm cfg

What are the paramters to be checked ?

-thanks

what version of db2 ? is it happen to V9.5... there are few APAR's related to this error:

https://www-304.ibm.com/support/docv...id=swg1IC67582

amit, we are using db2 9.7 FP0... will updating to the latest fix pack can solve the issue ?

most likely.

saying : most likely... is very strong
ok fp0 is not recommended (base code)
if you do not see any specific apar that matches the problem.. it might be corrected ..
or new problems can occur..