home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT06400 Status: Closed

PREC_NUM_WOCB SETTING IN DB2BPVARS.CFG NOT TAKING EFFECT

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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,* 
 
----------------------------------------------
Solution
First fixed in DB2 10.5 fix pack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.01.2015
27.01.2016
27.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList