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

"MEMEORY VISUALIZER" DOES NOT DISPLAY "DATABASE GLOBAL
MEMORY" FOR ALL DATABASES.

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
"Memeory Visualizer" does NOT display "Database Global Memory" 
for all databases. 
 
Here is an example of how to reproduce it. 
-- 1. Create a DB2 instance named "db2inst1". 
-- 2. Create 3 local databases under the instance "db2inst1": 
sample1 
sample2 
sample3 
-- 3. Start up the instance "db2inst1" by "db2start" command. 
-- 4. Connect to the 3 databases respectively in 3 DB2 CLP 
windows: 
db2 connect to sample1 
db2 connect to sample2 
db2 connect to sample3 
-- 5. Issue "db2 list active databases" and make sure all the 3 
databases are active. 
-- 6. Launch DB2 "Memory Visualizer". 
-- 7. Select the instance "db2inst1" when Memory Visualizer 
prompts you to select an instance. 
-- 8. In Memory Visualizer, expand the cascading menu "Database 
Global Memory". 
Then you will only see the database "sample3", although all the 
3 databases are active. 
Even if you clicked on the "Refresh", nothing would change. 
 
The fix of this problem will make "Memeory Visualizer" display 
"Database Global Memory" for all databases.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.5 on Linux, Unix and                  * 
* Windowsplatforms.                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* "Memeory Visualizer" does NOT display "Database              * 
* GlobalMemory" for all databases.Here is an example of how to * 
* reproduce it.-- 1. Create a DB2 instance named "db2inst1".-- * 
* 2. Create 3 local databases under the                        * 
* instance"db2inst1":sample1sample2sample3-- 3. Start up the   * 
* instance "db2inst1" by "db2start"command.-- 4. Connect to    * 
* the 3 databases respectively in 3 DB2 CLPwindows:db2 connect * 
* to sample1db2 connect to sample2db2 connect to sample3-- 5.  * 
* Issue "db2 list active databases" and make sure allthe 3     * 
* databases are active.-- 6. Launch DB2 "Memory Visualizer".-- * 
* 7. Select the instance "db2inst1" when Memory                * 
* Visualizerprompts you to select an instance.-- 8. In Memory  * 
* Visualizer, expand the cascading menu"Database Global        * 
* Memory".Then you will only see the database "sample3",       * 
* although allthe 3 databases are active.Even if you clicked   * 
* on the "Refresh", nothing would change.The fix of this       * 
* problem will make "Memeory Visualizer"display "Database      * 
* Global Memory" for all databases.                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.5 FixPak 6 or higher levels.    * 
****************************************************************
Local-Fix:
Launch "Memory Visualizer" prior to activating the databases. 
 
Using the same example mentioned in "Problem Description", 
the steps will be: 
-- 1. Start up the instance "db2inst1" by "db2start" 
command. 
-- 2. Launch DB2 "Memory Visualizer". 
-- 3. Select the instance "db2inst1" when Memory Visualizer 
prompts you to select an instance. 
-- 4. Connect to the 3 databases respectively in 3 DB2 CLP 
windows: 
db2 connect to sample1 
db2 connect to sample2 
db2 connect to sample3 
-- 5. Issue "db2 list active databases" and make sure all the 
3 databases are active. 
-- 6. In Memory Visualizer, expand the cascading menu 
"Database Global Memory". 
Then you will all the 3 databases.
verfügbare FixPacks:
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

Lösung
First fixed in DB2 UDB Version 9.5 FixPak 6
Workaround
Launch "Memory Visualizer" prior to activating the databases. 
 
 
Using the same example mentioned in "Problem Description", 
 
the steps will be: 
-- 1. Start up the instance "db2inst1" by "db2start" 
 
command. 
-- 2. Launch DB2 "Memory Visualizer". 
 
-- 3. Select the instance "db2inst1" when Memory Visualizer 
 
prompts you to select an instance. 
-- 4. Connect to the 3 databases respectively in 3 DB2 CLP 
windows: 
db2 connect to sample1 
db2 connect to sample2 
db2 connect to sample3 
-- 5. Issue "db2 list active databases" and make sure all the 
 
3 databases are active. 
-- 6. In Memory Visualizer, expand the cascading menu 
 
"Database Global Memory". 
 
Then you will all the 3 databases.
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC63422 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
18.09.2009
25.05.2010
25.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version