home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC80774 Status: Geschlossen

USING DB2ADUTL "QUERY LOGS BETWEEN" AND THE ".LOG"
EXTENSION ON THE LOG FILE NAME RETURNS AN INCORRECT LOG LIST

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
This problem was introduced in v9.7 FP5. 
 
Using db2adutl in version 9.7 FP5 with "query logs between" and 
specifying the .LOG extension does not works anymore and 
incorrect query results are being returned. This can lead to 
incorrect files being deleted. 
 
 
Consider the following content in the query result: 
 
$ db2adutl query logs  db sample 
 
Query for database SAMPLE 
 
Retrieving LOG ARCHIVE information. 
 
   Log file: S0137876.LOG, Chain Num: 4, DB Partition Number: 0, 
Taken    at: 2011-01-26-09.54.51 
   Log file: S0137877.LOG, Chain Num: 4, DB Partition Number: 0, 
Taken    at: 2011-02-02-14.28.46 
---------------------------------------------------------------- 
-------------------------------------------------- 
 
 
In the following command using the "BETWEEN" syntax, the two log 
numbers passed in parameter do not exist (note that they start 
with S1 and S2 respectively instead of S0 as above): 
 
$ db2adutl query logs between S1137876.LOG and S2137878.LOG db 
sample 
 
Query for database SAMPLE 
 
Retrieving LOG ARCHIVE information. 
 
   Log file: S0137876.LOG, Chain Num: 4, DB Partition Number: 0, 
Taken      at: 2011-01-26-09.54.51 
   Log file: S0137877.LOG, Chain Num: 4, DB Partition Number: 0, 
Taken      at: 2011-02-02-14.28.46 
---------------------------------------------------------------- 
---------------------------------------------------- 
 
You can see that with the above "BETWEEN" syntax, all log 
entries are returned instead of returning no entries as it 
should. 
 
 
Another type of wrong results is showing an empty list returned 
instead of the expected list of logs shown above in the first 
query when using different parameters for the "BETWEEN" syntax: 
 
$ db2adutl query logs between S0137876.LOG and S0137878.LOG db 
sample 
 
Query for database SAMPLE 
 
  Retrieving LOG ARCHIVE information. 
 
  No LOG ARCHIVE images found for SAMPLE
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Same as Apar description                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP6 or use the given Local Fix.              * 
****************************************************************
Local-Fix:
Do not specify the ".LOG" extension at the end of the log file 
name in the db2adutl query as follows: 
 
$ db2adutl query logs between  S0137876 and S0137878 db sample 
 
  Query for database SAMPLE 
 
  Retrieving LOG ARCHIVE information. 
 
   Log file: S0137876.LOG, Chain Num: 1, DB Partition Number: 0, 
Taken   at: 2011-01-26-09.54.51 
   Log file: S0137877.LOG, Chain Num: 1, DB Partition Number: 0, 
Taken   at: 2011-02-02-14.28.46
verfügbare FixPacks:
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

Lösung
First fixed in V9.7 FP6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.01.2012
05.06.2012
05.06.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP6
Problem behoben lt. FixList in der Version
9.7.0.6 FixList