home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC64580 Status: Closed

DBA3065E RETURNED WHEN RUNNING VISUAL EXPLAIN AGAINST A PRE V9.7 DATABASE.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A  "DBA3065E"  error is obtained whenever we try to 
generate an access plan.  Even simple queries such as: 
"SELECT * FROM SYSCAT.TABLES" 
result with the error. 
 
From a trace we see: 
243838      jdbc_VE_processBLOB exit [rc = 0xFFFFFFFF = -1] 
 
 
The jdbc_VE_processBLOB exit [rc=0xFFFFFFFF = -1] indicates that 
the snapshot is corrupted.  This means the explain BLOB 
generated by the V9 server cannot be parsed by V97 Client.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* A  "DBA3065E"  error is obtained whenever we try to          * 
* useexplain to a lower level of DB2.  An explain from         * 
* theControl Center for"SELECT * FROM SYSCAT.TABLES" results   * 
* with the DBA3065Eerror.From a trace we see:243838            * 
* jdbc_VE_processBLOB exit [rc = 0xFFFFFFFF = -1]The error     * 
* found in the trace says that the snapshot iscorrupted.  This * 
* only occurs when accessing a Database atlower version than   * 
* 9.7.                                                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 Fixpack 2                     * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
Problem was first fixed in DB2 UDB Version 9.7 Fixpack 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.11.2009
17.05.2010
25.01.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList