|
Problem IC70436
|
Status: Closed |
EXECUTE AUDIT LOG RECORDS SOMETIMES GET WRITTEN WHEN YOU USE AN AUDIT POLICY FOR WHICH THE EXECUTE CATEGORY IS NOT DEFINED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
EXECUTE audit log records sometimes get written when you use an
audit policy that is applied to a table, even though the EXECUTE
category for that audit policy is not defined. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of DB2 for Linux, UNIX and Windows *
****************************************************************
* PROBLEM DESCRIPTION: *
* EXECUTE audit log records sometimes get generated when you *
* use an audit policy even though the EXECUTE category for *
* that audit policy is not defined. *
****************************************************************
* RECOMMENDATION: *
* . *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC70620
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.08.2010
25.05.2011
25.05.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.4
|
 |
