DB2v9.7 FP1 installfixpack problem

[#1]

Hello all,

we've got troubles with installation of fixpack on DB2 9.7 on SuSE 11

- installfixpack done successfully;

- when I call db2start I receive

06/21/2010 15:05:06 0 0 SQL1042C An unexpected system error occurred.

SQL1032N No start database manager command was issued. SQLSTATE=57019

so, we can't start db6_update_db.sh (application is SAP)

files in /db2/db2sid/sqllib/adm are not updated and are differ from /db2/db2sid/db2_software/adm

Regards,

Konstantin

[Former Member]

Hello,

here are logs from db2diag.log:

2010-06-21-13.37.49.341568+240 I77066E324 LEVEL: Error

PID : 6556 TID : 139801863501568PROC : db2acd 0

INSTANCE: db2opq NODE : 000

FUNCTION: DB2 UDB, common communication, sqlccipcdarihandshake, probe:4

RETCODE : ZRC=0x800F00FC=-2146500356=SQLO_INV_PARM "Invalid input parameter"

2010-06-21-14.05.39.976684+240 I77689E1007 LEVEL: Error

PID : 7849 TID : 139801901979392PROC : db2fm

INSTANCE: db2opq NODE : 000

FUNCTION: DB2 Common, Generic Control Facility, gcf_stop, probe:30

MESSAGE : ECF=0x9000036D=-1879047315=ECF_FM_DB2FMD_PROCESS_NOT_EXIST

There is no fault monitor daemon running

CALLED : OS, -, open

RETCODE : ECF=0x9000001A=-1879048166=ECF_FILE_DOESNT_EXIST

File doesn't exist

CALLSTCK:

[0] 0x00007F26275DEB4C pdOSSeLoggingCallback + 0x100

[1] 0x00007F262A4DD33C /db2/db2opq/db2_software/lib64/libdb2osse.so.1 + 0x1B233C

[2] 0x00007F262A4DE9FD ossLogRC + 0x6B

[3] 0x00007F2625BC5D0A gcf_stop + 0x410

[4] 0x00007F2629EE4FD1 ZN9GcfCaller4stopEP12GCFPartInfomP11GCF_RetInfo + 0x1B9

[5] 0x00000000004067E1 main + 0x25E9

[6] 0x00007F262942C586 __libc_start_main + 0xE6

[7] 0x0000000000404169 __gxx_personality_v0 + 0x149

[8] 0x0000000000000000 ?unknown + 0x0

[9] 0x0000000000000000 ?unknown + 0x0

2010-06-21-14.05.39.977361+240 I78697E973 LEVEL: Error

PID : 7849 TID : 139801901979392PROC : db2fm

INSTANCE: db2opq 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

0

DATA #2 : unsigned integer, 8 bytes

1

CALLSTCK:

[0] 0x00007F26275DEB4C pdOSSeLoggingCallback + 0x100

[1] 0x00007F262A4DD33C /db2/db2opq/db2_software/lib64/libdb2osse.so.1 + 0x1B233C

[2] 0x00007F262A4DEA51 ossLogRC + 0xBF

[3] 0x0000000000406874 main + 0x267C

[4] 0x00007F262942C586 __libc_start_main + 0xE6

[5] 0x0000000000404169 __gxx_personality_v0 + 0x149

[6] 0x0000000000000000 ?unknown + 0x0

[7] 0x0000000000000000 ?unknown + 0x0

[8] 0x0000000000000000 ?unknown + 0x0

[9] 0x0000000000000000 ?unknown + 0x0

To all questions about stopping db2 and other: I rebooted server and there are no processes and others in memory by db2.

Regards,

Konstantin

[paul_power]

Hello Konstantin,

Those db2diag.log entries really point to the fault monitor not being stopped which could explain the instance update issue.

If you are using a high availability clustering product such as HACMP,

MSCS, or IBM Tivoli System Automation for Multiplatforms, the fault

monitor facility must be turned off since the instance startup and shut

down is controlled by the clustering product.

To confirm that fault monitor is no longer running, please type the

following command:

ps -ef grep -i fm

An entry that shows db2fmd and DB2<sid> indicates that the fault monitor

is still running on that instance. To turn off the fault monitor, type

the following command as the instance owner:

db2fm -i db2inst1 -D

Disable the fault monitor processes.

To stop the Fault Monitor Daemon, issue the command: DB2DIR/bin/db2fm -i iname -D where DB2DIR is the location where the DB2 copy is installed and iname represents the instance owner name.

The command must be performed once for each instance in the DB2 copy. If the Fault Monitor Coordinator (FMC) is enabled, prevent your instances from auto-starting: To determine whether the FMC is enabled, issue the command: DB2DIR/bin/db2fmcu where DB2DIR is the location where the DB2 copy is installed. If the FMC is enabled, you will see output similar to the following:FMC: up: PID = 3415 .

If the FMC is disabled, the output from the db2fmcu command will be: FMC: down. If the FMC is enabled, determine whether any instances are configured to auto-start after each system restart. Issue the command: DB2DIR/instance/db2iset -i iname -all where DB2DIR is the location where the DB2 copy is installed and iname represents the instance owner name. The command must be performed once for each instance in the DB2 copy.

If the output from the db2set command includes the following, it means that the instance is configured to auto-start:DB2AUTOSTART=YES Prevent the instances from auto-starting. Issue the command: DB2DIR/instance/db2iauto -off iname where DB2DIR is the location where the DB2 copy is installed and iname represents the instance owner name. If desired, re-enable instance auto-start after you have completed the fix pack installation: DB2DIR/instance/db2iauto -on iname If there are any db2 related ipcs resources these need to be removed manualy with ipcrm command.

Regards,

Paul