DB2 - Problembeschreibung
Problem IT26085 | Status: Geschlossen |
LOAD'S SQL3227W MESSAGE AFTER HITTING WARNINGCOUNT LIMIT MAY GIVE INCORRECT LINE NUMBER | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
When running LOAD with CPU_PARALLELISM > 1 (and when "modified by anyorder" option is not used explicitly or implicitly), LOAD ridder thread emits SQL3227W messages to map tokens such as "F6-1368" to row number. When WARNINGCOUNT option is used, LOAD should stop processing as soon as WARNINGCOUNT limit is reached, and for technical reasons LOAD ridder can no longer keep track of row number accurately after WARNINGCOUNT limit is first reached. However, because LOAD runs multiple formatter threads asynchronously when CPU_PARALLELISM > 1, after the first formatter thread hits WARNINGCOUNT limit (and LOAD begins to terminate), other formatter threads may also hit WARNINGCOUNT limit before they receive notification to terminate, and they emit warning messages that cause ridder thread to emit SQL3227W messages, and these SQL3227W messages (after the one at the time when WARNINCOUNT limit is first hit) may contain incorrect row number. This fix is to make LOAD stop emitting SQL3227W messages after we hit WARNINCOUNT limit the first time, thus avoid giving SQL3227W messages with incorrect row numbers. Secondly, if dumpfile option is used, then we also stop any subsequent formatter threads that hit WARNINGCOUNT limit (after the first formatter that hit it) from writing the row-that-caused-warning into the dumpfile, thus the dumpfile will only contain one row that is written due to hitting WARNINGCOUNT limit. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * some RFE request, give more error. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * REF and delivered * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 27.08.2018 08.07.2019 08.07.2019 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |