DB2 - Problembeschreibung
Problem IC67371 | Status: Geschlossen |
LOAD SHOULD NOT TRY TO OPEN HISTORY FILE IF IF WE ARE FILTERING OUT (NOT WRITING TO HISTORY FILE) LOAD RECORDS. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problembeschreibung: | |
LOAD should not try to open the history file, if we are filtering out (not writing to history file) LOAD records using DB2_HISTORY_FILTER, and load is not a "COPY YES LOAD". | |
Problem-Zusammenfassung: | |
Users Effected: All users on Lunix/Unix/Windows Problem Description: LOAD should not try to open the history file, if we are filtering out (not writing to history file) LOAD records using DB2_HISTORY_FILTER, and load is not a "COPY YES LOAD" Problem Summary: LOAD should not try to open the history file, if we are filtering out (not writing to history file) LOAD records using DB2_HISTORY_FILTER, and load is not a "COPY YES LOAD" | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows | |
Lösung | |
defect wsdbu00629352 CSD First fixed in DB2 UDB Version 9.1, FixPak 10 module engn_squ | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC67851 IC67855 IC70665 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 23.03.2010 13.06.2011 13.06.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.1. | |
Problem behoben lt. FixList in der Version | |
9.1.0.10 |