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

The "USERID" and "AUTHID" for all events in the AUDIT
category are incorrect.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Problem Description: 
 
When using DB2 Audit facility, all events in the AUDIT category 
have the "USERID" and "AUTHID" recorded as the user ID of the 
instance owner regardless of the real user ID that called 
db2audit. 
 
For example, your instance owner was "DB2INST1" and you logged 
into the system using another account "USER1" and then issued 
some Audit administration commands like: 
-- db2audit configure 
-- db2audit start 
-- db2audit stop 
The audit facility will log the "USERID" and "AUTHID" which 
called those events as "DB2INST1" while the expected id is 
"USER1".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users of version 9.7 on Linux, Unix and                  * 
* Windowsplatforms.                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When using DB2 Audit facility, all events in the             * 
* AUDITcategory have the "USERID" and "AUTHID" recorded as the * 
* userID of the instance owner regardless of the real user ID  * 
* thatcalled db2audit.For example, your instance owner was     * 
* "DB2INST1" and youlogged into the system using another       * 
* account "USER1" andthen issued some Audit administration     * 
* commands like:-- db2audit configure-- db2audit start--       * 
* db2audit stopThe audit facility will log the "USERID" and    * 
* "AUTHID" whichcalled those events as "DB2INST1" while the    * 
* expected id is"USER1".                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.7 FixPak 2 or higher levels.    * 
****************************************************************
Local Fix:
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
First fixed in DB2 UDB Version 9.7 FixPak 2.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.12.2009
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList