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

DB2PD CONTINUES CHECKING USER AUTHORITIES INSTEAD STOPPING AFTERCONFIRMING
USER HAS THE REQUIRED AUTHORITY.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
db2pd continues checking user authorities instead stopping after
confirming user has the required authority. For example, if the
user has SYSADMIN authority, db2pd will continue to check if the
user has SYSCTRL, SYSMAINT and SYSMON. If Audit is active, this
behaviour may generate CHECKING events if the user doesn't also
possess SYSCTRL, etc. If the user has SYSADMIN authority, there
is no requirement for the user to also have the 'lesser'
authorities.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All users                                                    *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 10.5 Fix Pack 10                              *
****************************************************************
Local Fix:
None
To prevent the additional Checking Audit records from being
generated, add the user to all of SYSADM_GROUP, SYSCTRL_GROUP,
SYSMAINT_GROUP and SYSMON_GROUPs.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT24656 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.04.2017
16.07.2018
16.07.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)