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 IC61892 Status: Closed

DB2 CRASHES DURING LOAD WHEN A PREVIOUS LOAD USING VENDOR SORT FAILS

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
DB2 crashes with signal # 11 during LOAD when a previous LOAD 
using vendor sort fails. 
 
Crash only occurs if 
1. A third party vendor sort tool is used and 
DB2SORT registry variable is pointing to the vendor library 
 
2. The table has index that has include columns 
 
3. This table index is marked bad due to a previous LOAD 
failure.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 V9.5                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 crashes with signal # 11 during LOAD when a previous     * 
* LOAD                                                         * 
* using vendor sort fails.                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* First Fixed in DB2 V9.5 FP5                                  * 
****************************************************************
Local Fix:
1. Avoid using third party sort tool 
 
2. Recreate indexes without INCLUDE columns
available fix packs:
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Crash only occurs if 
1. A third party vendor sort tool is used and 
DB2SORT registry variable is pointing to the vendor library 
 
2. The table has index that has include columns 
 
3. This table index is marked bad due to a previous LOAD 
failure.
Workaround
Avoid using third party sort tool
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC64067 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.07.2009
22.12.2009
22.12.2009
Problem solved at the following versions (IBM BugInfos)
9.5.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.5 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.