DB2 FOR LUW / DB2FORLUW / A50 - DB2

In MSFC(Microsoft failover cluster) environment, stopping 
instance may report SQL6048N when the cluster goes offline. 
After this error the DB2 instance resource may be brought down 
hard, so the crash recovery could run at the next database 
activation time. 
 
db2diag.log reports the error as follows: 
 
2014-10-22-12.10.29.184000+540 I17065F409           LEVEL: Error 
PID     : 1234                 TID : 56789          PROC : 
db2syscs.exe 
INSTANCE: DB2INST1             NODE : 000 
HOSTNAME: MYHOST 
EDUID   : 56789 
FUNCTION: DB2 UDB, base sys utilities, sqleGetStartStopOptions, 
probe:10 
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
 
2014-10-22-12.10.29.240000+540 I17476F340           LEVEL: Error 
PID     : 1234                 TID : 56789          PROC : 
db2syscs.exe 
INSTANCE: DB2INST1             NODE : 000 
HOSTNAME: MYHOST 
EDUID   : 56789 
FUNCTION: DB2 UDB, base sys utilities, sqleGetStartStopOptions, 
probe:15 
MESSAGE : Receive failure on startstopOptions 
 
2014-10-22-12.10.29.245000+540 I17818F432           LEVEL: 
Severe 
PID     : 1234                 TID : 56789          PROC : 
db2syscs.exe 
INSTANCE: DB2INST1             NODE : 000 
HOSTNAME: MYHOST 
EDUID   : 56789 
FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:1552 
MESSAGE : ZRC=0xFFFFE860=-6048 
          SQL6048N  A communication error occurred during START 
or STOP 
          DATABASE MANAGER processing.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using MSFC                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 7.                      * 
****************************************************************

First fixed in DB2 Version 10.5 Fix Pack 7.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

22.11.2014
29.02.2016
29.02.2016