DB2 - Problembeschreibung
Problem IT01710 | Status: Geschlossen |
CONNECTION TO CF FAILS RESULTING IN SLOW CRASH RECOVERY | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
Connection to CF fails due to inactive port use resulting in slow crash recovery Following messages are seen in db2diag.log FUNCTION: DB2 UDB, RAS/PD component, pdLogCaPrintf, probe:876 DATA #1 : <preformatted> PsConnectNtfy: notify_connect failed: 0x80090029 DATA #1 : <preformatted> If a CF return code is displayed above and you wish to get more information then please run the following command: FUNCTION: DB2 UDB, Shared Data Structure Abstraction Layer for CF, SAL_InternalConnectNotify, probe:5533 MESSAGE : CA RC= 2148073513 DATA #1 : String, 24 bytes PsConnectNotify failure. DATA #2 : PsToken_t, PD_TYPE_SD_PSTOKEN, 152 bytes Eye Catcher = CATOKEN CF Server Info : - Unique Sequence Number = 0 (0x0) - Port Number = 56001 - Node Identifier = 0 - Instance Identifier = 0 - Netname = <netname> Local Member Info : - uDAPL Device = <incorrect port> Transport Type = UDAPL (0x1) Cmd Connection Use Types = NORMAL (0x0) DATA #3 : unsigned integer, 8 bytes 10 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * V10.5 FP2 and below * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix * * Pack 4) or higher. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Lösung | |
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 09.05.2014 08.09.2014 15.10.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.4 |