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 IC69550 Status: Closed

UPDATE DBM CFG COMMAND FAILS WITH SQL5126N FOR CLIENT NODE TYPE DUE TO
FCM_NUM_BUFFERS SET TO A NON-ZERO VALUE

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
The database manager configuration parameter, FCM_NUM_BUFFERS, 
is not supported for CLIENT node type and should always have a 
value of 0. 
 
Starting in v9.5 FP4, the minimum for FCM_NUM_BUFFERS has been 
increased to 895. During major release upgrade and fix pack 
update, the value of FCM_NUM_BUFFERS needs to be verified and 
may be set to the new minimum if it's below 895. However, this 
special handling was not exempt from CLIENT node type, causing 
FCM_NUM_BUFFERS to be set to a value that's out of range for the 
CLIENT node type. 
 
This will result the following error for any update attempt to 
any database manager configuration parameters: 
 
db2 update dbm cfg using CATALOG_NOAUTH NO 
 
SQL5126N An attempt was made to modify the database manager 
configuration parameter "fcm_num_buffers" which is not valid for 
a node type of "2".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Customers running on DB2 v9.5 FP4 or higher                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The database manager configuration                           * 
* parameter,FCM_NUM_BUFFERS,is not supported for CLIENT node   * 
* type and should always haveavalue of 0.Starting in v9.5 FP4, * 
* the minimum for FCM_NUM_BUFFERS hasbeenincreased to 895.     * 
* During major release upgrade and fix packupdate, the value   * 
* of FCM_NUM_BUFFERS needs to be verifiedandmay be set to the  * 
* new minimum if it's below 895. However,thisspecial handling  * 
* was not exempt from CLIENT node type,causingFCM_NUM_BUFFERS  * 
* to be set to a value that's out of range fortheCLIENT node   * 
* type.This will result the following error for any update     * 
* attempttoany database manager configuration parameters:db2   * 
* update dbm cfg using CATALOG_NOAUTH NOSQL5126N An attempt    * 
* was made to modify the database managerconfiguration         * 
* parameter "fcm_num_buffers" which is not validfora node type * 
* of "2".                                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* There is not a local fix.  Contact DB2 service for           * 
* theutility to fix the databasemanager configuration file     * 
* (db2systm).                                                  * 
****************************************************************
Local Fix:
None, contact DB2 service for the utility to fix the database 
manager configuration file (db2systm).
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC69570 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.06.2010
16.08.2010
16.08.2010
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)