|
Problem IC86418
|
Status: Closed |
DB2 9.7FP6 "DB2ADUTL DELETE OLDER THAN N DAYS WITHOUT PROMPTING"DELETES ARCHIVE LOGS BOTH OLDER AND NEWER THAN N DAYS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
"db2adutl delete older than n days without prompting"
This syntax used in DB2 Version 9.5 deleted all backup images
older than 'n' days (full, loadcopy, tablespace), but left
archive
logs in TSM. After upgrading to DB2 Version 9.7fp6, the same
syntax deletes also all archive logs both older and newer than
n days.
'without prompting' clause just confirms what was returned by
'db2adutl delete ...', transaction logs are being returned (even
newer that 'n' days).
According to the documentation, this syntax should not delete
archive logs. Only when 'logs' clause is specified are logs
deleted.
The problem started after upgrade to DB2 v9.7 FP6. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 and Fix Pack 7 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 and Fix Pack 7 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC88674
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 07.09.2012
25.10.2012
25.10.2012 |
| 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.7
|
 |
