|
Problem IC70261
|
Status: Closed |
SECONDS PART OF THE TIMESTAMP FOR THE DB2 AUDIT UTILITY ARCHIVED LOG FILENAME GOES UP TO 60 INSTEAD OF UP TO 59 |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
The seconds part of the timestamp for the DB2 audit utility
archived log filename goes up to 60 instead of up to 59.
You may observe archived log files with name like:
db2audit.instance.log.0.20100603105960
ending with 60 (range used 00-60) which is incorrect, 0-59 is
expected as there are only 60 seconds.
This problem affects only the file naming, not the contents of
the audited activity which is not affected by this issue. The
issue can be seen as only cosmetic but it may have an impact on
the application or utility that handles these files if it
expects the seconds to be 00-59 as it should be instead of
00-60. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All Users *
****************************************************************
* PROBLEM DESCRIPTION: *
* The seconds part of the timestamp for the DB2 audit utility *
* *
* archived log filename goes up to 60 instead of up to 59. *
* *
* *
* *
* You may observe archived log files with name like: *
* *
* *
* *
* db2audit.instance.log.0.20100603105960 *
* *
* *
* *
* ending with 60 (range used 00-60) which is incorrect, 0-59 *
* is *
* expected as there are only 60 seconds. *
* *
* *
* *
* This problem affects only the file naming, not the contents *
* of *
* the audited activity which is not affected by this issue. *
* The *
* issue can be seen as only cosmetic but it may have an impact *
* on *
* the application or utility that handles these files if it *
* *
* expects the seconds to be 00-59 as it should be instead of *
* *
* 00-60. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to D2 version 9.7 Fix Pack 4 *
**************************************************************** |
| 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 DB2 version 9.7 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.07.2010
02.05.2011
02.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
|
 |
