JR28129: EXPLAIN QUERY WINDOW DOESN'T APPEAR FOR DATABASE ON OTHER LOCAL INSTANCE CATALOGGED ON LOCAL NODE.

DB2 Version 9.1 Fix Pack 7  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 7a  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 8  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

APAR status

• Closed as program error.

Error description

• Explain Query window doesn't appear for database on other local
  instance catalogged on local node.
  
  Steps to recreate the problem on windows platform:
  --------------------------------------
  1. default instance: DB2_01
  
  2. create another instance:
      db2icrt V9ST2
  
  3. on v9st2, create a database: tes
      set db2instance=v9st2
      db2 terminate
      db2 create db tes
  
  4. on another db2clp window, set db2instnace to DB2_01
      set db2instance=db2_01
      db2 terminate
  
      db2 catalog local node v9st2 instance v9st2
      db2 catalog db tes at node v9st2
  
      check tes can be connected from instance DB2_01
  
  5. Still on DB2_01 db2clp
      set db2instance=db2_01
      db2 terminate
  
      on the same db2 command window, start db2 control center:
  db2cc
  
      Find out database TES, right click TES, choose "Explain
  Query", the window does not appear.
  --------------------------------------
  
  This problem does not happen on V8.
  
  This problem does not occur on v9 if the other local instance is
  catalogged as tcpip node. For example,
  similar as the previous steps, on step 4, catalog a tcpip node
  instead of local node,
  
  --------------------------------------
  1. default instance: DB2_01
  
  2. create another instance:
      db2icrt V9ST2
  
  3. on v9st2, create a database: tes
      set db2instance=v9st2
      db2 terminate
      db2 create db tes
  
      Enable tcpip for it:
      db2set db2comm=tcpip
      db2 update dbm cfg using svcename 50000
      db2stop
      db2start
  
  4. on another db2clp window, set db2instnace to DB2_01
      set db2instance=db2_01
      db2 terminate
  
      db2 catalog tcpip node v9st2 remote localhost server 50000
      db2 catalog db tes at node v9st2
  
      check tes can be connected from instance DB2_01
  ------------------------------------
  

Local fix

• Catalog the node as tcpip node instead of local node.
  

Problem summary

• Users affected: All
  Problem Description: See above
  Problem Summary: See above
  

Problem conclusion

• will be fixed in v91fp7
  

Temporary fix

• N/A
  

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  JR31851 JR31852 JR31853 JR31854 JR31855

Fix information

• Fixed component name

  DB2 UDB WSE WIN

• Fixed component ID

  5765F3501

Applicable component levels

• R910 PSY

     UP