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

"DB2ADUTL DELETE LOADCOPY OLDER THAN" fails in DB2 version 97fp5

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Following error can be seen: 
 
$ db2adutl delete loadcopy older than 30 days db <dbname> 
without prompting 
Error.  '30' is not a valid log file name. 
 
With former fixpack levels the command works fine.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V97fp6                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* NA                                                           * 
****************************************************************
Local Fix:
As an alternative "Keep n" or "taken at" clause can be used.
available fix packs:
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
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC84245 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.11.2011
06.06.2012
26.06.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.6 FixList