|
Problem IC64159
|
Status: Closed |
HIGH SYSTEM CPU DURING ONLINE BACKUP DUE TO LARGE NUMBER OF DB2BM THREADS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Running an online backup may cause very high system cpu usage on
the system.
This is caused by the number of db2bm threads created compared
to the number of db2med threads actually writing out the data
to the backup location.
This APAR addresses a change to the autonomic tuning algorithm
to prevent the creation of an excessive number of db2bm threads. |
| Problem Summary: |
USERS AFFECTED: All
PROBLEM DESCRIPTION:
see ERROR DESCRIPTION |
| Local Fix: |
Manually adjust the number of db2bm threads during backup
using option PARALLELISM
e.g.
db2 backup db <DBNAME> online load <LIBRARY> open <# SESSIONS>
sessions parallelism <# BUFFERMANIPULATORS> |
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 1 |
| Workaround |
see LOCAL FIX |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.10.2009
16.12.2009
16.12.2009 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
