Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC88532 Status: Geschlossen

DB2HAICU FAILS ON SOLARIS WITH "PIPE READ FROM VENDOR PROCESS WAS
INTERRUPTED"

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
db2haicu fails on solaris at the following question: 
 
Enter the host name of a machine to add to the domain: 
host1 cannot be reached. Re-enter the node name again. 
 
db2diag.log (DIAGLEVEL 4) shows: 
 
2012-09-25-11.22.13.658983+060 I346438A462        LEVEL: Warning 
PID     : 28432                TID  : 1           PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 1 
FUNCTION: DB2 UDB, oper system services, 
sqloInvokeVendorFunction, probe:50 
MESSAGE : ZRC=0x870F0009=-2029060087=SQLO_EOF "the data does not 
exist" 
          DIA8506C Unexpected end of file was reached. 
DATA #1 : String, 46 bytes 
Pipe read from vendor process was interrupted. 
 
2012-09-25-11.22.13.663716+060 I346901A501        LEVEL: Info 
PID     : 28432                TID  : 1           PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 1 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaIsClusterNodeAlive, probe:500 
MESSAGE : 
ECF=0x9000052D=-1879046867=ECF_SQLHA_VENDOR_CALL_PROG_ERROR 
          HA Infrastructure vendor function call internal error 
DATA #1 : String, 62 bytes 
Error from HA Infrastructure, could not invoke vendor function 
 
2012-09-25-11.22.13.666023+060 E347403A583        LEVEL: Warning 
PID     : 28432                TID  : 1           PROC : 
db2haicu 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 1 
FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, 
sqlhaIsHostAlive, probe:35 
MESSAGE : 
ECF=0x9000052D=-1879046867=ECF_SQLHA_VENDOR_CALL_PROG_ERROR 
          HA Infrastructure vendor function call internal error 
DATA #1 : String, 37 bytes 
Specified hostname/IP is not pingable 
DATA #2 : String, 38 bytes 
host1 
DATA #3 : Pointer, 8 bytes 
0x00000001006f38b0 
 
In most cases there will be a trap file belonging to 
db2vend_DB2NAME 
with the following stack: 
 
PC location: _gettimeofday + 0xc 
Object file: /lib/sparcv9/libc.so.1 (offset 0xda7dc) 
</Registers> 
<StackTrace> 
##### Object: /lib/sparcv9/libc.so.1 
_gettimeofday(0x1,0x100319ae8,0x0,0x0,0x48,0xffffffff7fffe338) + 
0xc 
##### Object: /export/home/db2hadr1/sqllib/adm/db2havend 
__1cHsend_v46F_v_(0x1,0x100319ae8,0x0,0x0,0x48,0xffffffff7fffe33 
8) + 0x68 
__1cIreadloop6F_i_(0x10000dc50,0x0,0x0,0x0,0x1002a4b38,0xdd0) + 
0xcc 
__1cPsqleIsHostAlive6Fpc_i_(0x10034f590,0x4,0x100327950,0x0,0x10 
02a4b38,0x2) + 0x17c 
__1cY_sqlhaIsClusterNodeAlive6FIpv_I_(0xf6950,0x10034ce20,0x1003 
4f570,0x0,0x10004ebd7,0 
xee) + 0x1f0 
__1cZsqlhaInvokeVendorFunction6Fpv_v_(0x10034ce20,0x0,0x7,0xa,0x 
10624dd3,0x10624c00) + 
0x6ac 
main(0x10,0x1380,0x5,0x4,0x1002a7360,0xffffffff7fffe7b0) + 0x294 
_start(0x0,0x0,0x0,0x0,0x0,0x0) + 0x17c 
</StackTrace>
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Platforms                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpack 3                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem First Fixed in DB2 v10.1 Fixpack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.11.2012
21.10.2013
21.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList