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

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
DB2 V10.5 FP4 will contain the fix.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.05.2014
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList