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

VISUAL EXPLAIN FAILS WITH DBA3065E(SNAPSHOT CANNOT BE PROCESSED DUE TO A
CLI ERROR) WHEN QUERY ACCESS PLAN HAS A MERGE JOIN

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
When trying to get an access plan via DB2 Visual Explain, you 
might encounter the error DBA3065E (Snapshot cannot beprocessed 
due to a CLI error) when the query access plan has a Merge Join 
operator in it. 
This problem was introduced into V91 FP7, V95 FP4 and V97 GA. 
 
To confirm this fix will correct the DBA3065E error from Visual 
Explain, you can use the "db2exfmt" tool to manually get the 
access plan from the Explain Facility and then check if there is 
a MSJOIN operator in the plan by examining the output from 
"db2exfmt". 
 
The fix for this problem should be applied to the DB2 server 
side.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.1 on Linux, Unix andWindowsplatforms. * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When trying to get an access plan via DB2 Visual Explain,you * 
* might encounter the error DBA3065E (Snapshot cannot          * 
* beprocessed due to a CLI error) when the query access plan   * 
* has a Merge Join operator in it. This problem was introduced * 
* into V91 FP7, V95 FP4 and V97 GA. To confirm this fix will   * 
* correct the DBA3065E error from Visual Explain, you can use  * 
* the "db2exfmt" tool to manually get the access plan from the * 
* Explain Facility and then check if there is a MSJOIN         * 
* operator in the plan by examining the output from"db2exfmt". * 
* The fix for this problem should be applied to the DB2        * 
* serverside.                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the server to DB2 Linux, Unix and Windows,           * 
* Version9.1 FixPak 9 or higher levels.                        * 
****************************************************************
Local Fix:
View the access plan with the Explain Facility and the db2exfmt 
tool.
available fix packs:
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

Solution
First fixed in DB2 Linux, Unix and Windows, Version 9.1 FixPak 
 
9.
Workaround
View the access plan with the Explain Facility and the db2exfmt 
tool.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.11.2009
03.05.2010
03.05.2010
Problem solved at the following versions (IBM BugInfos)
9.0.,
9.1.
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.