DB2 FOR LUW / DB2FORLUW / 950 - DB2

If you restore a V8.1/V8.2 (any FixPak level and bit) backup 
image to V9.5 or V9.7 (any FixPack level and bit) instance, you 
may receive a sigsegv at the migration stage and can not 
restore. 
 
You may find a similar stack trace as below in the associated 
trap file: 
    : 
... sqlpGetHeadLSN 
... sqlpGetHeadLSN 
... sqlbStartPools 
... sqlbinit 
... sqledint 
... FirstConnect 
... StartUsingLocalDatabase 
... AppStartUsing 
... sqlemigr 
    : 
 
This problem does not exist on V9.1, you can restore V8.1/V8.2 
image to V9.1.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.5                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.5 FixPack 7.                            * 
****************************************************************

There are two ways to work around this problem: 
1) Export V8.1/V8.2 data and then import into V9.5/V9.7. 
2) Upgrade from V8.1/V8.2 to V9.1 first then upgrade to 
V9.5/V9.7.

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
 

Problem was first fixed in DB2 UDB Version 9.5 FixPack 7.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC71071 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

25.06.2010
11.01.2011
11.01.2011

9.5.FP7