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 IT06400 Status: Geschlossen

PREC_NUM_WOCB SETTING IN DB2BPVARS.CFG NOT TAKING EFFECT

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
PREC_NUM_WOCB setting in db2bpvars.cfg is expecting a buffer 
pool ID.  So any new setting is not being picked up with 
PREC_NUM_WOCB = xxxx.  The db2diag.log will give the following 
message: 
 
The correct syntax is PREC_NUM_WOCB = <value>,<buffer pool id> 
(use * for <buffer pool id> to apply the configuration to all 
buffer pools). 
This configuration parameter is ignored.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 fix pack 7.                              * 
****************************************************************
Local-Fix:
As a workaround, perform the following: 
 
db2set DB2BPVARS=/home/smkivell/sqllib/cfg/DB2BPVARS.cfg 
db2stop 
db2start 
 
where DB2BPVARS.cfg contains: 
 
(smkivell@db2debug) /home/smkivell/sqllib/cfg 
$ cat DB2BPVARS.cfg 
---------------------------------------------- 
PREC_NUM_WOCB = 8192,* 
 
----------------------------------------------
Lösung
First fixed in DB2 10.5 fix pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.01.2015
27.01.2016
27.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList