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

DB2UPDV97 CAUSES REBIND AND QUERY FAILURES ON SYSTEM OBJECTS IF
DB2_WORKLOAD=SAP IS SET

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If the DB2_WORKLOAD=sap registry variable is set while running 
the db2updv97 utility, numerous system objects will be 
incorrectly invalidated.  These system objects can not be 
re-validated, hence can no longer be used without the help of 
DB2 Service. 
 
Some errors that will arise due to this problem include, 
 
db2 " select * from SYSIBMADM.TBSP_UTILIZATION " 
SQL0567N  "SYSIBM" is not a valid authorization ID. 
SQLSTATE=42602 
 
or 
 
db2rbind will unexpectedly fail with a SQL0440 error.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Version 9.7 Fix Pack 1 users who have the            * 
* DB2_WORLOAD=sap registry variable set and are running        * 
* db2updv97.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Under the DB2_WORLOAD=sap registry variable, CREATE VIEW     * 
* statements are converted automatically to CREATE OR REPLACE  * 
* statements. The db2updv97 infrastructure relies on CREATE    * 
* VIEW statements not being converted in order to function     * 
* properly.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Unset the DB2_WORKLOAD registry variable when running        * 
* db2updv97 or see "Local Fix".                                * 
****************************************************************
Local Fix:
Restore the database to a point just before running db2updv97, 
turn OFF the DB2_WORKLOAD=sap variable, then re-issue db2updv97. 
 Once the utility completes successfully, turn the 
DB2_WORKLOAD=sap registry variable back on.
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 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
Problem first fixed in DB2 Version 9.7 Fix Pack 2 and all 
subsequent Fix Packs.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.11.2009
08.04.2010
08.04.2010
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