DB2 FOR LUW / DB2FORLUW / A50 - DB2

PD_GET_LOG_MSGS table function 'timestamp' parameter will act as 
if only 
NULL is passed in regardless of the value specified. 
 
This has been seen on V10.1 and V9.8 but not in older releases. 
 
For example running the query on: 
 
 SELECT substr(TIMESTAMP,1,10), substr(APPL_ID,1,10), 
substr(MSG,1,10) FROM TABLE ( PD_GET_LOG_MSGS( CURRENT_TIMESTAMP 
- 1 DAYS)) AS T ORDER BY TIMESTAMP ASC; 
 
On v9.7 release the following output is generated as expected: 
 
1          2          3 
---------- ---------- ---------- 
2013-10-10 none       ADM0503C 
2013-10-10 none       ADM7006E 
2013-10-10 none       ADM7513W 
2013-10-10 none       ADM10501W 
2013-10-10 none       ADM10501W 
 
 
On v10.1 (till FP3) all entries are returned by the query 
regardless of the '-1 
DAYS' input: 
1          2          3 
---------- ---------- ---------- 
2013-09-03 none       ADM7513W 
2013-09-05 none       ADM0503C 
2013-09-11 none       ADM7513W 
2013-09-13 none       ADM0503C 
2013-09-13 none       ADM7006E 
2013-09-13 none       ADM7513W 
2013-09-13 none       ADM0503C 
2013-09-13 none       ADM7006E 
2013-09-13 none       ADM7513W 
2013-09-13 none       ADM7513W 
2013-09-13 none       ADM7514W 
2013-09-13 none       ADM7514W 
2013-09-13 none       ADM7513W 
2013-09-13 none       ADM7006E 
2013-09-13 none       ADM7513W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1823E 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1823E 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1823E 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-13 *N0.nareen ADM1822W 
2013-09-18 none       ADM10501W 
2013-09-18 none       ADM10501W 
2013-09-18 *N0.nareen ADM4500W 
2013-09-18 *N0.nareen ADM4500W 
2013-09-23 none       ADM10500E 
2013-09-23 none       ADM10500E 
2013-09-23 none       ADM10500E 
2013-09-23 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM7519W 
2013-09-24 none       ADM7514W 
2013-09-24 none       ADM7514W 
2013-09-24 none       ADM7513W 
2013-09-24 none       ADM7006E 
2013-09-24 none       ADM7513W 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 none       ADM10500E 
2013-09-24 *N0.nareen ADM1611W 
2013-09-24 *N0.nareen ADM1602W 
2013-09-24 *N0.nareen ADM1611W 
2013-09-24 *N0.nareen ADM1602W 
2013-09-24 *N0.nareen ADM1611W 
2013-09-24 *N0.nareen ADM1602W 
2013-09-24 *N0.nareen ADM1611W 
2013-09-24 *N0.nareen ADM1602W 
2013-09-24 *N0.nareen ADM1611W 
2013-09-24 *N0.nareen ADM1602W 
2013-09-24 *N0.nareen ADM1611W 
2013-09-24 *N0.nareen ADM1602W 
2013-09-24 *N0.nareen ADM1611W 
2013-09-26 none       ADM0503C 
2013-09-26 none       ADM0503C 
2013-10-03 none       ADM7006E 
2013-10-03 none       ADM7513W 
2013-10-03 *LOCAL.nar ADM1713C 
2013-10-04 none       ADM0503C 
2013-10-04 none       ADM7006E 
2013-10-04 none       ADM7513W 
2013-10-10 none       ADM0503C 
2013-10-10 none       ADM7006E 
2013-10-10 none       ADM7513W 
2013-10-10 none       ADM10501W 
2013-10-10 none       ADM10501W 
2013-10-10 none       ADM0503C 
2013-10-10 none       ADM7513W 
2013-10-10 *LOCAL.nar ADM1530I 
2013-10-10 *LOCAL.nar ADM1531I 
 
  90 record(s) selected.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 3.                      * 
****************************************************************

A WHERE clause can be used to filter the entries at the cost of 
memory usage.

First fixed in DB2 Version 10.5 Fix Pack 3.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

28.04.2014
20.10.2014
20.10.2014