DB2 FOR LUW / DB2FORLUW / 970 - DB2

"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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.7 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.7 FixPak 2 or higher levels.    * 
****************************************************************

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.

DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 UDB Version 9.7 FixPak 2.

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.

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

25.09.2009
14.05.2010
14.05.2010

9.7.