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

Execute category audit logs contain incorrect event values when viewed in
table format

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The EXECUTE Audit category, when the audit log is viewed, can 
contain multiple rows describing one event. The first record 
describes the main event, and its event column contains the key 
word STATEMENT. The remaining rows describe the parameter 
markers or host variables, one row per parameter, and their 
event column should contain the key word DATA, but instead also 
contain STATEMENT. 
 
For example, querying the table containing the audit data would 
return something similar to this: 
 
CATEGORY EVENT      STMTVALINDEX STMTVALDATA STMTTEXT 
-------- ---------- ------------ ----------- ---------- 
EXECUTE  STATEMENT             - -           SELECT ... 
EXECUTE  STATEMENT             1          12 - 
EXECUTE  STATEMENT             2       Kevin - 
EXECUTE  STATEMENT             3        2011 - 
 
  4 record(s) selected.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Audit facility users                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP3                                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 10.1 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2013
25.11.2013
25.11.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList