Fixes are available
DB2 Version 9.1 Fix Pack 4a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 4 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 5 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 6a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
APAR status
Closed as new function.
Error description
Two enhancements are implemented in the fenced mode process (db2fmp) for better handling of the fenced threadsafe stored procedure calls: . You can enable and disable the db2agent caching db2fmp worker for both threadsafe and not threadsafe fenced mode processes. You might consider this feature if the applications are using connection pooling and you want the fenced mode processes (FMPs) to be reused instead of having different FMPs associated to each of the db2agents that are servicing the connections. . You can also limit the number of threads that can run within a fenced mode process. When this limit is reached, a new fenced mode process will be started to support new requests, and the existing one will be able to service incoming calls once any of its threads is are returned to the pool. You might consider using this feature if your threadsafe Java routines use a large amount of java heap. . Because these two DB2 registry variables DB2_AGENT_CACHING_FMP and DB2_MAX_THREADS_PER_FMP might have an impact on your overall system, contact DB2 Support for technical guidance for when to use them and how to enable them.
Local fix
Problem summary
User Affected: DB2 SP/UDF users Problem Description: db2fmp enhancements. Problem Summary: see ERROR DESCRIPTION
Problem conclusion
Problem was first fixed in Version 9.1 FixPak 4 (s071028).
Temporary fix
Comments
APAR Information
APAR number
IZ03666
Reported component name
DB2 UDB ESE SOL
Reported component ID
5765F4102
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-08-23
Closed date
2007-11-26
Last modified date
2009-04-24
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
DB2 UDB ESE SOL
Fixed component ID
5765F4102
Applicable component levels
R910 PSY
UP
Document Information
Modified date:
07 January 2022