Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC61570 Status: Closed

SQLCODE 20459 WHILE EXPLAINING QUERIES VIA DATA STUDIO WHEN EXPLAIN
TABLES EXIST IN BOTH SESSION USERS & SYSTOOLS SCHEMA

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
problem: 
 
SQLCODE 20459 with SQLSTATE 01H55 WHILE EXPLAINING QUERIES VIA 
DATA STUDIO WHEN EXPLAIN TABLES EXISTS IN BOTH THE SESSION 
USER'S AND THE SYSTOOLS SCHEMA 
 
description: 
 
When explain tables exist in the session user's schema and the 
SYSTOOLS schema, explaining queries in Data Studio fails with: 
 
    Failed to collect explain data for the query access plan for 
the target data server with SQLSTATE 01H55. 
    This error is caused by: db2luw20459E: SQLCODE: 20459, 
SQLSTATE: 01H55, SQL20459W  The procedure "SYSPROC.EXPLAIN_SQL" 
has encountered an internal processing error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Data Studio users                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* SQLCODE 20459 WHILE EXPLAINING QUERIES VIA DATA STUDIO       * 
* WHENEXPLAIN TABLES EXIST IN BOTH SESSION USERS & SYSTOOLS    * 
* SCHEMA                                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to next fixpak release as necessary.                 * 
****************************************************************
Local Fix:
Have only one set of explain tables, either the session user 
schema or the SYSTOOLS schema.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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

Solution
First fixed in 9.7 FP1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
18.06.2009
20.05.2010
20.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList