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

SECURITY: User continues to have privilege to execute a non-DDL statement
after their DBADM authority has been revoked.

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
After a user's DBADM authority is revoked, the user can still 
execute the non-DDL statement where the statement has already 
completed the authorization checking and before the revoke 
operation.  The user will continue to be able to re-execute the 
same statement until they disconnect from the database or 
attempt to execute another statement.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW version 9.1 fp10                          * 
****************************************************************
Local Fix:
available fix packs:
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
Problem was fixed in DB2 LUW version 9.1 fp10
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66814 IC66815 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.03.2010
16.06.2011
16.06.2011
Problem solved at the following versions (IBM BugInfos)
9.1.FP10
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList