home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66944 Status: Geschlossen

SETTING PRIORITY OF EDU VIA DB2_RESOURCE_POLICY EDU_PRIORITY
DOESN'T WORK ON LINUX

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Setting priority of an EDU (DB2's engine thread) via 
DB2_RESOURCE_POLICY EDU_PRIORITY doesn't work on Linux.  For 
example, given the following setting, 
 
>> db2set 
DB2_RESOURCE_POLICY=/home/db2inst1/loggerpri.cfg 
>> cat loggerpri.cfg 
<RESOURCE_POLICY> 
   <SCHEDULING_POLICY> 
      <PRIORITY_VALUE>75</PRIORITY_VALUE> 
      <EDU_PRIORITY> 
         <EDU_NAME>db2loggw</EDU_NAME> 
         <PRIORITY_VALUE>60</PRIORITY_VALUE> 
      </EDU_PRIORITY> 
   </SCHEDULING_POLICY> 
</RESOURCE_POLICY> 
 
All EDUs should have the priority of 75, except the db2loggw 
(log writer), which should have 60.  However, none of them has 
any priority change.  This APAR will address this problem. 
 
Note that one can view the priority of DB2 EDUs by 
cross-referencing 'ps -lLfp <PID of db2sysc>' and 'db2pd -edus'. 
 
Also note that changing priority of EDUs can greatly impact the 
overall performance of DB2 as well as the server both positively 
and negatively.  Only experienced DBAs should make use of it 
after a large amount of tests.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 servers on Linux platform that makes use of              * 
* DB2_RESOURCE_POLICY registry variable                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Same as ERROR DESCRIPTION                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fix Pack 2 or later.                      * 
****************************************************************
Local-Fix:
To change the priority of DB2 EDU's without DB2_RESOURCE_POLICY, 
one can manually run renice command.
verfügbare FixPacks:
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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

Lösung
Fixed in DB2 9.7 Fix Pack 2.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67205 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.03.2010
08.04.2010
08.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList