DB2 - Problembeschreibung
Problem IT04850 | Status: Geschlossen |
DB2READLOG() API CAN RETURN RECORDS FORMATTED AS DB2READLOG_FILTER_ON EVEN WHEN DB2READLOG_FILTER_OFF WAS SET | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
This will happen in the very rare case where we have one connection (i.e. application) using the db2ReadLog() API that drives 'read' requests while specifying alternating filter options (i.e. switching between DB2READLOG_FILTER_ON and DB2READLOG_FILTER_OFF). Example: Application: connect to db Application: db2ReadLog reads records between LRI 'Val1' and 'Val2' (FILTER ON) Application: db2ReadLog reads records between LRI 'Val1' and 'Val2' (FILTER OFF) What matters is that in BOTH cases 'LRI Val2' should be the same for both connections. 'LRI Val1' does not matter and can be different. In other words, the second scan is continuing from the end of the previous scan (with filtering OFF). This second scan will return information as if the filter ON option was still specified (implying the output structure is different) even though filter OFF was used. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 users which utilize db2 read log API. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2_v101fp5, db2_v105fp6 or newer. * * * * If you do not want to upgrade do not switch, use a different * * connection for the read log API filter OFF if your main scan * * is using FILTER ON. * **************************************************************** | |
Local-Fix: | |
Lösung | |
This was fixed in V105FP5 and V105FP6, now you can switch without any issues. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 09.10.2014 06.08.2015 06.08.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.5 |