|
Problem IC76213
|
Status: Closed |
REMOVE LIMIT ON BACK GROUND SYSTEM APPLICATIONS THAT WAS ADDED IN V9.5 FP7 |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
APAR IC67852 added a limit on back ground system applications
(such as asynchronous index cleanup, admin task scheduler,
health monitor) in v9.5 fp7. This limit was determined
dynamically based on workload and sometimes it was too low
resulting in too many SQL1226N errors being encountered. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See error description above. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.5 FP8 or higher *
**************************************************************** |
| Local Fix: |
The limit can be disabled by using
db2set DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:500
This is a dynamic setting so the instance does not have to be
recycled. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
As of v9.5 fp8, the limit on background system applications
introduced in v9.5 FP7 has been turned off by default thus
restoring the behaviour in prior fixpacks. When this APAR is
applied,
a fixed limit on background system applications can be enabled
using db2set
DB2_PMODEL_SETTINGS=MAX_BACKGROUND_SYSAPPS:<num> where num is
the limit. The limit should be based on the expected number of
concurrent background maintenance tasks. A value of 150 is
suggested as a good starting point. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.05.2011
27.06.2011
27.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP7,
9.5.FP8,
9.5.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.8
|
 |
