DB2 FOR LUW / DB2FORLUW / 970 - DB2

The db2exfmt explain table format command or Optim Query Tuner 
(OQT)'s access plan graph tuning activity might fail depending 
on the authorizations of the user who is executing the 
operation.  The problem can occur only when the tool is 
exercised for the first time against a database, or when the 
tool is used for the first time after the DB2 server has been 
upgraded to a new fix pack level. 
 
For db2exfmt, the user will observe: 
 
SQL0001N  Binding or precompilation did not complete 
successfully. 
 
 
The information will direct the user to a message file: 
 
Error during bind. 
Bind messages can be found in db2exfmt.msg 
 
 
The message file will contain SQL0551N errors of the form: 
 
LINE    MESSAGES FOR db2exfmt.bnd 
------ 
---------------------------------------------------------------- 
---- 
        SQL0061W  The binder is in progress. 
29223   SQL0551N  "ZURBIE" does not have the required 
authorization 
                  or privilege to perform operation "EXECUTE" on 
object 
                  "SYSPROC.EXPLAIN_FROM_SECTION". 
SQLSTATE=42501 
29251   SQL0551N  "ZURBIE" does not have the required 
authorization 
                  or privilege to perform operation "EXECUTE" on 
object 
                  "SYSPROC.EXPLAIN_FROM_ACTIVITY". 
SQLSTATE=42501 
29279   SQL0551N  "ZURBIE" does not have the required 
authorization 
                  or privilege to perform operation "EXECUTE" on 
object 
                  "SYSPROC.EXPLAIN_FROM_CATALOG". 
SQLSTATE=42501 
        SQL0082C  An error has occurred which has terminated 
                  processing. 
        SQL0092N  No package was created because of previous 
errors. 
        SQL0091N  Binding was ended with "5" errors and "0" 
warnings. 
 
 
 
For OQT, the exact error screen seen may differ depending on the 
version of the DB2 server and/or the version of the OQT client. 
A db2trc at the DB2 server will show a sqlcode -551 with 
sqlerrmc:  username  EXECUTE  SYSPROC.EXPLAIN_FROM_SECTION. 
 
 
This problem was first introduced in DB2 V9.7 Fix Pack "0".

**************************************************************** 
* USERS AFFECTED:                                              * 
* N/A                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2EXFMT OR ACCESS PLAN GRAPH FROM OPTIM QUERY TUNER         * 
* MIGHTFAIL WITH SQLCODE -551.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 3.                       * 
****************************************************************

For db2exfmt, have a database administrator execute:  BIND 
db2exfmt.bnd.   After a successful bind of this bnd file, the 
original user who observed the problem will be able to run 
db2exfmt. 
 
For OQT, 
1. Have a database administrator (or the database creator) be 
the first to exercise the access plan graph tuning activity  for 
the database.   After first successful execution of access plan 
graph, the original user who observed the problem will be able 
to exercise access plan graph as well. 
2. Have a database administrator execute: BIND 
db2ExplainRtns.bnd.  After a successful bind of this bnd file, 
the original user who observed the problem will be able to 
exercise access plan graph.

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
 

Problem was first fixed in Version 9.7 Fix Pack 3.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC67520 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

19.03.2010
27.09.2010
27.09.2010

9.7.FP3