DB2 - Problem description
Problem IC66316 | Status: Closed |
DB2 EXPORT CREATES EXCESSIVE LOCKING ON CATALOG TABLES. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
Multiple locks on SYSDEPENDECIES and SYSSEQUENCES for rows that are not related to the table that is being exported. The problem occurs only when the select part of the statement uses the wild card *: db2 export to <FILE> of ixf messages <MSG FILE> select * from <source schema>.<source_table> The query that is executed againtst the catalog tables with the isolation level that the package has been bound. In this case RS. The problem can be avoided if it is exported to DEL or ASC. Also if the list of columns is provided in the export statament. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * db2 export causes excessive locking. Other * * applicationswilltimeout generally waiting for SYSDEPENCIES * **************************************************************** * RECOMMENDATION: * * Migrate to v95fp6Avoid using 'select *" in the * * exportcommand. Provide listof columns instead. * **************************************************************** | |
Local Fix: | |
1. Use export to DEL or ASC 2. List the name of the columns for export. Avoid using *. | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
fixed in v95fp6 | |
Workaround | |
not known / see Local fix | |
Comment | |
FIN | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC66531 IC66532 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.02.2010 22.06.2010 22.06.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP6, 9.5.FP6AVOID | |
Problem solved according to the fixlist(s) of the following version(s) |