Fixes are available
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
APAR status
Closed as program error.
Error description
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.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * The user running Federation Server V9.7 and later and a * * non-DRDA fenced wrapper. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Federation Server V97 Fixpack 6 or later. * ****************************************************************
Problem conclusion
The issue is firstly fixed on V97 Fixpack 6.
Temporary fix
Comments
APAR Information
APAR number
JR41275
Reported component name
FEDERATION SERV
Reported component ID
5724N9700
Reported release
970
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-21
Closed date
2012-10-09
Last modified date
2012-10-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
FEDERATION SERV
Fixed component ID
5724N9700
Applicable component levels
R970 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS2K5T","label":"InfoSphere Federation Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021