home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC84297 Status: Geschlossen

FEDERATION SERVER RECEIVED SQLCODE -1476 AND -430 INTERMITTENTLY. ERROR IS
LOGGED IN DB2DIAG.LOG.

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When federation server was interrupted, it tried to contact the 
associated fmp process for some cleanup. Due to a programming 
defect, federation server could not correctly determine the 
status of ipc resource between engine and fmp process. Then 
engine brought down the whole fmp process. For the applications 
which have already worked with that fmp, all subsequent requests 
could not proceed and resulting with error -1476/-430. 
 
This can happen when a busy application is forced, or receives a 
signal of interruption. 
 
In some relatively rare cases, this issue may cause an 
application hang with "DisconnectPending" status: 
 
The corresponding db2agent is holding these latches: 
SQLO_LT_SQLE_FEDFMP_APP_CB__fmpAppLatch 
SQLO_LT_sqlerFmpRow__ipcLatch 
 
and it gets stuck at following call stack: 
semop 
sqloSSemP 
sqlccipcWaitSynch 
sqlccipcinit 
sqlccinit 
sqlerInitCommsLayer 
sqlerMasterThreadReq 
sqlerInterruptThreadedFmp 
sqlerInterruptFmp 
sqlerFedInvokeFencedRoutine 
sqlriFedInvokeInvoker 
sqlqg_Call_FMP_Thread 
sqlqgDeleteServer 
sqlqgDeleteWrapper 
sqlqgApplicationTermination 
sqle_term_app_dj_cb 
sqlrr_appl_free_appl_cbs 
sqlrr_appl_term 
0AppStopUsing 
sqlesrspWrp 
sqleUCagentConnectReset 
sqljsCleanup 
 
This issue exists in DB2 V9.7 and later. 
This error can happen for all non-DRDA data sources.
Problem-Zusammenfassung:
User affected: 
  Users of InfoSphere Federation Server 
Problem description and summay: 
  See error description
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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 was fistly fixed in Version 10, FixPak 1. This 
fix should be applied on the federation Server.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
01.11.2012
01.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList