DB2 - Problem description
Problem IC87775 | Status: Closed |
DB2LOOK GENERATES DDL FOR DMS TABLESPACE WITH MAXSIZE ROUNDED DOWN. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When the create tablespace command is issued for a DMS talespace with the MAXSIZE not a multiple of GB or MB then db2look generates the DDL statement with MAXSIZE rounded down. This can cause confusion especially if the DMS tablespaces are very large in Giga bytes and not an exact multiple of GB. e.g. $ db2 "create tablespace xxxxx pagesize 4096 managed by database using (FILE '/xxxx/xxxx/xxxx/xxxxx/tbs2' 1024k) BUFFERPOOL bp4k AUTORESIZE YES MAXSIZE 1536k" DB20000I The SQL command completed successfully. and corresponding db2look output CREATE LARGE TABLESPACE "xxxxx" IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 4096 MANAGED BY DATABASE USING (FILE '/xxxx/xxxx/xxxx/xxxxx/tbs2' 256) EXTENTSIZE 32 PREFETCHSIZE AUTOMATIC BUFFERPOOL BP4K OVERHEAD 7.500000 TRANSFERRATE 0.060000 AUTORESIZE YES MAXSIZE 1 M NO FILE SYSTEM CACHING DROPPED TABLE RECOVERY ON; This defect will address this issue by providing the MAXSIZE in terms of actual KB when MAXSIZE is not an exact multiple of GB or MB. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version V9.7 Fix Pack 8 or Later. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 Version V9.7 Fix Pack 8 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.11.2012 30.09.2013 30.09.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.8 |