|
Problem IC84383
|
Status: Closed |
DROP TABLE COMMANDS ARE SOMETIMES SLOW IN DB2 PURESCALE ENVIRONMENTS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
DROP TABLE commands may take longer in purescale environments.
This APAR addresses the issue and improves the performance of
the DROP TABLE commands especially in
those cases where the group buffer pool (GBP) is large. |
| Problem Summary: |
DROP TABLE commands may take longer in purescale environments.
This APAR addresses the issue and improves the performance of
the DROP TABLE commands especially in
those cases where the group buffer pool (GBP) is large. |
| Local Fix: |
If the same table will be created again after the drop, then
rename the table to be dropped and create the new table.
Drop the renamed table later in a maintenance window. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
If the same table will be created again after the drop, then
rename the table to be dropped and create the new table.
Drop the renamed table later in a maintenance window. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
19.04.2013
19.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
