DB2 FOR LUW / DB2FORLUW / 970 - DB2

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.

USERS AFFECTED: All 
 
PROBLEM DESCRIPTION: 
see ERROR DESCRIPTION

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>

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
 

Problem was first fixed in Version 9.7 Fix Pack 1

see LOCAL FIX

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

26.10.2009
16.12.2009
16.12.2009

9.7.FP1