Latest versionsfixlist
11.1.0.6 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC66531 Status: Closed

DB2 EXPORT CREATES EXCESSIVE LOCKING ON CATALOG TABLES.

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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 statemt 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:                                         * 
* Excessive locking while running db2 export. It will          * 
* locktimeout other applications generally waiting on          * 
* SYSDEPENCIEStable                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Migrate to v97fp2 oravoid using "select * " in the export    * 
* command. Instead usethe list of columns                      * 
****************************************************************
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.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem fixed in v97fp2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.02.2010
25.05.2010
25.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.