|
Problem IC67371
|
Status: Closed |
LOAD SHOULD NOT TRY TO OPEN HISTORY FILE IF IF WE ARE FILTERING OUT (NOT WRITING TO HISTORY FILE) LOAD RECORDS. |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| 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: |
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: |
|
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
defect wsdbu00629352
CSD First fixed in DB2 UDB Version 9.1, FixPak 10
module engn_squ |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67851 IC67855 IC70665
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.03.2010
13.06.2011
13.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
