|
Problem IC66304
|
Status: Closed |
DB2 AUDIT FACILITY MAY NOT CAPTURE CONNECTION EVENTS USING DATABASE-LEVEL AUDIT SETTINGS EVEN THE DATABASE IS ACTIVATED |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
For the CONNECT and AUTHENTICATION events that occur during
connect, the instance-level audit settings are used until the
database is activated.
The database is activated either during the first connection or
when the ACTIVATE DATABASE command is issued.
However, in some cases, DB2 audit facility may not capture the
connection events using database-level audit settings even after
the database is activated. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* As same as Error description. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.8 FixPack 3. *
**************************************************************** |
| Local Fix: |
Configure for instance-level VALIDATE category to capture the
AUTHENTICATION event. |
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.8 FixPack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.02.2010
10.01.2011
10.01.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
