DB2 FOR LUW / DB2FORLUW / 950 - DB2

When we try to get the access plan from Visual Explain for a 
query that contains an IXSCAN, Visual Explain crashes. An 
example of a simple query that exhibits this behaviour is: 
 
SELECT POLICY FROM SYSTOOLS.POLICY 
 
Using Visual Explain, the client v9x talks to the server 
instance v91 fp9, and Visual Explain crashes. 
 
You can verify if you are encountering this problem by obtaining 
a db2exfmt explain of the query: 
1) ensure the explain tables have been created, if not 
previously used: 
  - connect to the database, and use "db2 -tvf 
sqllib/misc/EXPLAIN.DDL" 
2) connect to the database, and generate the explain for the 
query using the explain statement: 
  - explain plan for ...sql_statement... 
  - where "...sql_statement..." is replaced by the sql statement 
that you want to check. 
3) use the db2exfmt utility to format the generated plan: 
  - db2exfmt -d ...db_name... -1 -o check_plan.exfmt 
  - where "...db_name..." is replaced with the database name. If 
password authentication is needed, you may be prompted for a 
userid and password. 
4) edit or grep the explain format utility's out to determine if 
there is an IXSCAN operator: 
  - grep IXSCAN check_plan.exfmt 
5) If the above check indicates there is one or more IXSCAN 
operators found in the explain, then you have encountered this 
APAR.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All LUW users of DB2 Control Center Visual Explain.          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When we try to get the access plan from Visual Explain for   * 
* aquery that contains an IXSCAN, Visual Explain crashes.      * 
* Anexample of a simple query that exhibits this behavior      * 
* is:SELECT POLICY FROM SYSTOOLS.POLICYUsing Visual Explain,   * 
* the client v9x talks to the serverinstance v95 fp6, and      * 
* Visual Explain crashes.You can verify if you are             * 
* encountering this problem byobtaininga db2exfmt explain of   * 
* the query:1) ensure the explain tables have been created, if * 
* notpreviously used:- connect to the database, and use "db2   * 
* -tvfsqllib/misc/EXPLAIN.DDL"2) connect to the database, and  * 
* generate the explain for thequery using the explain          * 
* statement:- explain plan for ...sql_statement...- where      * 
* "...sql_statement..." is replaced by the sqlstatementthat    * 
* you want to check.3) use the db2exfmt utility to format the  * 
* generated plan:- db2exfmt -d ...db_name... -1 -o             * 
* check_plan.exfmt- where "...db_name..." is replaced with the * 
* databasename. Ifpassword authentication is needed, you may   * 
* be prompted for auserid and password.4) edit or grep the     * 
* explain format utility's out todetermine ifthere is an       * 
* IXSCAN operator:- grep IXSCAN check_plan.exfmt5) If the      * 
* above check indicates there is one or more IXSCANoperators   * 
* found in the explain, then you have encounteredthisAPAR.     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the server to DB2 V9.5 Fixpack 7.                    * 
****************************************************************

Use the db2exfmt utility, or the Optim tools (for DB2 V9.1 and 
on), to obtain the explain instead of Visual Explain.

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
 

The problem is corrected in DB2 V9.5 Fixpack 7.

not known / see Local fix

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

13.09.2010
15.11.2010
15.11.2010

9.5.FP7