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 IC66574 Status: Closed

DB2ADVIS MAY EXIT WITH ERROR CODE -220. ALTERNATIVELY, COMPILATI ON UNDER
ANY ADVISOR EXPLAIN MODES MAY FAIL WITH SQL0220N

product:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problem description:
The DB2 Design Advisor (db2advis) may exit with error code -220. 
Alternatively, compilation of a query under any of the various 
available recommendation EXPLAIN modes may fail with SQLCODE 
-220 (SQL0220N). 
For either of these situations to occur, the database in use 
must have been created in VARCHAR2 compatibility mode, i.e., 
with the DB2_COMPATIBILITY_VECTOR registry variable set to ORA 
or with the sixth bit set (0x020).
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.8 Fix Pack 3 or later.              * 
****************************************************************
Local Fix:
None available.
available fix packs:
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Solution
First fixed in DB2 Version 9.8 Fix Pack 3.
Workaround
None available.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.02.2010
10.01.2011
10.01.2011
Problem solved at the following versions (IBM BugInfos)
9.8.FP3
Problem solved according to the fixlist(s) of the following version(s)
9.8.0.3 FixList