Latest versionsfixlist
11.1.0.7 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

DB2 - Problem description

Problem IC97260 Status: Closed

DATABASE UPGRADE TO DB2 V10 MAY TRAP WITH SEGMENTATION VIOLATION IN
FUNCTION SQLRLM_CHECKMIGRATEFLAG

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
During database upgrade to DB2 V10, catalog migration may trap 
with segmentation violation in function sqlrlm_checkMigrateFlag 
and the following stack: 
 
sqlrlm_checkMigrateFlag 
sqlrlm_postCatalogMigrationTasks 
sqlrlm_catalog_migrate 
sqlefmig 
sqlemigr 
AppLocalStart 
sqlelostWrp 
sqleUCengnInit 
sqleUCagentConnect 
sqljsConnectAttach 
sqljs_ddm_accsec 
sqljsParseConnect 
sqljsParse 
sqljsSqlam 
sqljsDriveRequests 
sqljsDrdaAsInnerDriver 
sqljsDrdaAsDriver 
RunEDU 
EDUDriver 
sqlzRunEDU 
sqloEDUEntry
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 4.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC97261 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.10.2013
23.06.2014
23.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList