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

DB2 AUTOCONFIGURE WILL RETURN SQL0450N IF THE DATABASE HAS A LARGE NUMBER
OF BUFFER POOLS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DB2 AUTOCONFIGURE will return SQL0450N if the database has a 
large number of buffer pools. 
 
$   db2 autoconfigure apply db and dbm 
SQL0450N  Routine "db2CfgSg" (specific name 
"SQL140331173323540") has 
generated a result value, SQLSTATE value, message text, or 
scratchpad which is 
too long.  SQLSTATE=39501
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all platform                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 FP4.                                    * 
****************************************************************
Local Fix:
If any apply option were specified the autoconfigure command has 
successfully applied changes but the output cannot be displayed. 
If possible you might want to consider decreasing the number of 
buffer pools created if they are not absolutely necessary.
Solution
DB2 V10.5 FP4 will contain the fix.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.05.2014
08.09.2014
08.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList