DB2 - Problem description
Problem IC98874 | Status: Closed |
DATABASE MIGRATION FROM DB2 V98 TO V10.5 FAILS | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
During database migration from db2 V98 to V10.5 the following failure occurs (the failure is related to the number of members in a cluster. Numbers above 4 might trigger the failure) SQL0902C A system error occurred. Subsequent SQL statements cannot be processed. IBM software support reason code: "SYSSCHEMAAUTH Migration DMS rc=8b05004b: Create indexes". SQLSTATE=58005 The following db2diag.log errors can be seen. 2013-11-21-11.42.33.336598-300 I13562966A3229 LEVEL: Info PID : 25886794 TID : 7988 PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DB1 APPHDL : 0-54 APPID: *N0.DB1.******* AUTHID : **** HOSTNAME: hostname EDUID : 7988 EDUNAME: db2agent (DB1) 0 FUNCTION: DB2 UDB, data management, SQLD_TCB_GSS::sqldFinalizeTcbGss, probe:1352 RETCODE : ZRC=0x8B05004B=-1962606517=SQLE_SCA_NOMEM "No memory in the SCA heap" DIA8300C A memory heap error has occurred. MESSAGE : Error allocating global memory DATA #1 : unsigned integer, 2 bytes 0 DATA #2 : unsigned integer, 2 bytes 37 DATA #3 : unsigned integer, 4 bytes 0 DATA #4 : unsigned integer, 8 bytes 0 DATA #5 : unsigned integer, 8 bytes 0 DATA #6 : unsigned integer, 8 bytes 2 CALLSTCK: (Static functions may not be resolved correctly, as they are resolved to the nearest symbol) [0] 0x090000001A45C1E4 sqldFinalizeTcbGss__12SQLD_TCB_GSSFP8sqeAgentP8SQLD_TCB17SQLE_GS S_SYNCTYPE + 0x4B4 [1] 0x090000001A46CDC8 sqldLoadTCB__FP8sqeAgentP8SQLD_TCBi + 0x6E54 [2] 0x090000001AD9DE7C sqldFixTCB__FP8sqeAgentiN32PP8SQLD_TCBUiT7 + 0x19C [3] 0x090000001ADA545C sqldLockTableFixTCB__FP8sqeAgentUsT2UcUliN26N25T6PcT6T12_T6P14SQ LP_LOCK_INFOPP8SQLD_TCBUiT18_ + 0x844 [4] 0x0900000019737100 sqldLockTableForInxBld__FP8sqeAgentP17SQLD_CREATEINX_CBPUiUsPP8S QLD_TCB + 0x2A4 [5] 0x090000001C6F8B28 sqldBeginIndexCreate__FP8sqeAgentP17SQLD_CREATEINX_CB + 0x884 [6] 0x090000001E1A9CDC sqlrlmci_CrtIndexes__FP8sqeAgentiT2P8sqlr_tidPUsP12sqlrl_catpdsT 2PUc + 0x35C [7] 0x090000001EF6FFAC sqlemigr__FP8SQLE_BWAP14db2UCinterface + 0x78A4 [8] 0x090000001EF68BD4 sqlemigr__FP8SQLE_BWAP14db2UCinterface + 0x4CC [9] 0x090000001EF3E594 sqlemigr__FP8SQLE_BWAP14db2UCinterface + 0x1034 [10] 0x0900000019FC2174 AppLocalStart__14sqeApplicationFP14db2UCinterface + 0x1340 [11] 0x0900000019F958E8 AppLocalStart__14sqeApplicationFP14db2UCinterface + 0xD50 [12] 0x0900000019F94B14 sqlelostWrp__FP14db2UCinterface + 0x44 [13] 0x0900000019F943EC sqleUCengnInit__FP14db2UCinterfaceUs + 0x240 [14] 0x0900000019F97EB8 sqleUCagentConnect + 0x400 [15] 0x0900000019FA7DB4 sqljsConnectAttach__FP13sqljsDrdaAsCbP14db2UCinterface + 0x628 [16] 0x0900000019FA6C00 sqljs_ddm_accsec__FP14db2UCinterfaceP13sqljDDMObject + 0x32C [17] 0x0900000019FA686C sqljsParseConnect__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UCinte rface + 0x208 [18] 0x0900000019F22C7C sqljsParse__FP13sqljsDrdaAsCbP14db2UCinterfaceP8sqeAgentb@OL@246 49 + 0x76C [19] 0x090000001A885BD0 @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x30 [20] 0x090000001A8A237C @72@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb + 0x530 [21] 0x090000001BE18A08 @72@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0x1E0 [22] 0x090000001BE193BC @72@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x5E0 [23] 0x090000001A114568 RunEDU__8sqeAgentFv + 0x3BC04 [24] 0x090000001A15A53C RunEDU__8sqeAgentFv + 0xDC [25] 0x090000001B4BA048 EDUDriver__9sqzEDUObjFv + 0x110 [26] 0x090000001A4CB66C sqloEDUEntry + 0x38C [27] 0x0900000000497E10 _pthread_body + 0xF0 [28] 0xFFFFFFFFFFFFFFFC ?unknown + 0xFFFFFFFF 2013-11-21-11.42.33.353560-300 I13566196A571 LEVEL: Severe PID : ***** TID : **** PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DB1 APPHDL : 0-54 APPID: *N0.*****.****** AUTHID : ***** HOSTNAME: hostname EDUID : **** EDUNAME: db2agent (***) 0 FUNCTION: DB2 UDB, catalog services, sqlrlmci_CrtIndexes, probe:25 RETCODE : ZRC=0x8B05004B=-1962606517=SQLE_SCA_NOMEM "No memory in the SCA heap" DIA8300C A memory heap error has occurred. 2013-11-21-11.42.33.363922-300 E13566768A785 LEVEL: Error PID : ******** TID : **** PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DB1 APPHDL : 0-54 APPID: *N0.***.131121155002 AUTHID : **** HOSTNAME: hostname EDUID : 7988 EDUNAME: db2agent (***) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:30 MESSAGE : ADM14005E The following error occurred: "AppErr". First Occurrence Data Capture (FODC) has been invoked in the following mode: "Automatic". Diagnostic information has been recorded in the directory named "/db2/***/db2dump/FODC_AppErr_2013-11-21-11.42.33.362145_2588679 4_798 8_000/". <> and later 2013-11-21-11.42.33.445839-300 I13571187A911 LEVEL: Severe PID : ****** TID : **** PROC : db2sysc 0 INSTANCE: db2inst1 NODE : 000 DB : DB1 APPHDL : 0-54 APPID: *N0.****.131121155002 AUTHID : DB2GEB HOSTNAME: hostname EDUID : **** EDUNAME: db2agent (***) 0 FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, probe:300 DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes sqlcaid : SQLCA sqlcabc: 136 sqlcode: -902 sqlerrml: 55 sqlerrmc: SYSSCHEMAAUTH Migration DMS rc=8b05004b: Create indexes sqlerrp : SQLRM010 sqlerrd : (1) 0x00000002 (2) 0xFFFFFFFF (3) 0x00000000 (4) 0x00000003 (5) 0xFFFFEDD8 (6) 0x00000000 sqlwarn : (1) W (2) (3) (4) (5) S (6) (7) (8) (9) (10) (11) sqlstate: | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 LUW SERVER EDITION * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Fixed in DB2 V10.5.0.4 * **************************************************************** | |
Local Fix: | |
In order to correct this failure we set : db2set DB2_SCA_GSS_PERCENT=26 26 was the lower bound. A value of 25 still resulted in a failure. If the upgrade still fails in the same manner (SCA Heap exhaustion), then please increment to 30, 35, 40, etc until success. Once the database upgrade has succeeded, please unset the registry variable: db2set DB2_SCA_GSS_PERCENT= | |
available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.01.2014 08.09.2014 08.09.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.4 |