DB2 - Problem description
| Problem IC65445 | Status: Closed | 
| LOAD FROM CURSOR FROM A TABLE WITH LOB COLUMN IN DPF ENVIRONMENT MIGHT LOAD WRONG RESULTS IN THE TARGET TABLE LOB COLUMN | |
| product: | |
| DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
| Problem description: | |
| In a partitioned database environment, if you have a table A with a LOB column with hundreds of thousands of rows, running the LOAD FROM CURSOR from table A to a table B might load incorrect data into the LOB column in table B. The following example shows an scenario where you can experience this problem: 1. Create table A and table B with the same definition including a LOB column. 2. Insert more than one houndred thousand rows in table A. 3. db2 "DECLARE mycurs CURSOR FOR SELECT * FROM A" 4. db2 "LOAD FROM mycurs OF cursor INSERT INTO B" The LOAD command fetches rows from table A using a cursor and inserts them into table B. The LOB columns in table B might have incorrect data after the LOAD command is completed. | |
| Problem Summary: | |
| **************************************************************** * USERS AFFECTED: * * All users in DPF environmet using Load from cursor with LOB * * data * **************************************************************** * PROBLEM DESCRIPTION: * * LOAD FROM CURSOR FROM A TABLE WITH LOB COLUMN IN DPF * * ENVIRONMENT MIGHT LOAD WRONG RESULTS IN THE TARGET TABLE LOB * * COLUMN * **************************************************************** * RECOMMENDATION: * * Please upgrade to Vesion 9.5 Fixpak 6 or later * **************************************************************** | |
| Local Fix: | |
| Use one of the following alternatives: 1. Use the LOAD command to load from a file instead of a cursor. 2. Use the IMPORT command. | |
| available fix packs: | |
| DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
| Solution | |
| Problem is first fixed in Version 9.5 Fixpak 6 | |
| Workaround | |
| Use one of the following alternatives: 1. Use the LOAD command to load from a file instead of a cursor. 2. Use the IMPORT command. | |
| Timestamps | |
| Date - problem reported : Date - problem closed : Date - last modified : | 06.01.2010 24.06.2010 24.06.2010 | 
| Problem solved at the following versions (IBM BugInfos) | |
| 9.5. | |
| Problem solved according to the fixlist(s) of the following version(s) | |








 
