Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT08188 Status: Closed

CHANGE APPLICATION_ID FUNCTION FROM NON-THREADSAFE TO THREADSAFE TO AVOID
HIGH NUMBER OF DB2FMP PROCESSES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
This APAR is to change the APPLICATION_ID built in function from 
non-theadsafe to threadsafe.  This will allow simultaneous 
executions of APPLICATION_ID to run as multiple threads within a 
single db2fmp process rather than a separate db2fmp process per 
call. 
 
Without this APAR fix, a system may experience a high number of 
db2fmp processes. 
 
To identify if APPLICATION_ID is the function in question 
causing the high number of db2fmp processes, first run the 
command: 
db2pd -fmpexechistory 
 
Then look at the output to identify which routine id is 
displayed most often. 
 
Then run a query such as this which assumes routine id 65681 is 
the one that showed up often in the db2pd output. 
select routinename from sysibm.sysroutines where routine_id = 
65681 
 
If the routine name is APPLICATION_ID then the application is 
calling this function many times. 
 
In order to have the APPLICATION_ID changed to threadsafe after 
applying the Fixpack that contains this APAR, please run 
db2updv95 to update the database to the newest functions.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V9.7 users                                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fix Pack 11 or higher.                   * 
****************************************************************
Local Fix:
To a avoid a high number of persistent db2fmp processes on the 
system in the event there is a spike of db2fmp processes because 
of many simultaneous calls to APPLICATION_ID, the FENCED_POOL 
parameter can be tuned to a lower value.  This will control the 
number of db2fmp processes that will remain in the event of a 
spike in calls. 
 
db2 update dbm cfg using fenced_pool <number>
Solution
Fixed in DB2 V9.7 Fix Pack 11.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.04.2015
16.10.2015
16.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.