DB2 - Problem description
Problem IT04213 | Status: Closed |
LOAD command writes row data into a transaction log when the row size exceeds the pagesize. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When the row expansion is enabled(i.e. the row size is larger than the tablespace pagesize) and the actual row data size is larger than the page size, the varchar or vargraphic columns data will be logged during LOAD. This may have an impact when many rows exceed the page size, but please note that extended row size support is effective when most of data rows can fit on a smaller page, but the table definition requires a bigger page size. If most of data rows cannot fit, then the table should be defined in larger page size tablespace appropriately. If most of data rows can fit within the page size, then this problem does not have a noticeable impact. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 7. * **************************************************************** | |
Local Fix: | |
Create the table in a tablespace with larger pagesize if most of data rows exceed the current pagesize. | |
Solution | |
First fixed in DB2 Version 10.5 Fix Pack 7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 05.09.2014 29.02.2016 29.02.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |