|
Problem IC94330
|
Status: Closed |
MEMBER FAILED TO START ON HOME HOST DUE TO SQL1677N ERROR |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The following error is reported during db2start processing:
db2start member 3
05/17/2013 15:31:32 3 0 SQL1677N DB2START or DB2STOP
processing failed due to a DB2 cluster services error.
SQL1677N DB2START or DB2STOP processing failed due to a DB2
cluster services error.
The root cause is that the db2 vendor operation being processed
(sqlhaDisableResourceGroup in this case) timed out:
2013-05-17-15.31.32.014426-300 I10523608A438 LEVEL: Error
PID : 16646348 TID : 1 PROC :
db2star2
INSTANCE: db2inst01 NODE : 003
HOSTNAME: host01
EDUID : 1
FUNCTION: DB2 UDB, oper system services,
sqloInvokeVendorFunction, probe:1774
MESSAGE : ZRC=0x870F00B3=-2029059917=SQLO_NPIPE_TIMEOUT
"Operation on named pipe timed out."
DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes
0x870F00B3
2013-05-17-15.31.32.014944-300 I10524047A1121 LEVEL: Event
PID : 16646348 TID : 1 PROC :
db2star2
INSTANCE: db2inst01 NODE : 003
HOSTNAME: host01
EDUID : 1
FUNCTION: DB2 UDB, oper system services, sqlossig, probe:10
MESSAGE : Sending SIGKILL to the following process id
DATA #1 : signed integer, 4 bytes
13828150
CALLSTCK: (Static functions may not be resolved correctly, as
they are resolved to the nearest symbol)
[0] 0x090000000BC7691C sqlossig + 0x21C
[1] 0x090000000C7BED98
@93@sqloSendDestroyToVendorProcess__FCP18SQLO_VENDOR_HANDLECb +
0x5B4
[2] 0x090000000C7BF06C
@93@sqloCleanupVendorProcess__FCP18SQLO_VENDOR_HANDLECb + 0x234
[3] 0x090000000B114B14 sqloInvokeVendorFunction + 0x604
[4] 0x090000000F593AD4 sqlhaDisableResourceGroup2__FUiPvT2i +
0x31C
[5] 0x090000000B122540 sqlhaDisableResourceGroup + 0x238
[6] 0x090000000B14DBE0
sqlhaSetStartPreconditions__FP25SQLHA_CLUSTER_OBJECT_INFOP19SQLH
A_CONTROL_BLOCK + 0x14E4
[7] 0x0000000100009BFC DB2StartMain + 0x91DC
[8] 0x0000000100012550 main + 0x10
[9] 0x00000001000002F8 __start + 0x70
This APAR fix allows for the db2vend process to collect
additional diagnostic information which will be recorded in the
syslog file. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 4. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 Version 10.1 Fix Pack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.07.2013
02.06.2014
02.06.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
