home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC61970 Status: Closed

DB2 instance can get trap during 32-bit to 64-bit upgrade.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 Instance can get trap during 32-bit to 64-bit 
upgrade (DB2 V9.5 -> DB2 V9.7 or DB2 V9.1 -> DB2 V9.7 or DB2 
V8 -> DB2 V9.7) 
 
 
 
db2 restore db sample 
SQL2519N  The database was restored but the restored database 
was not upgraded to the current release.  Error "-1224" with 
tokens "-2097151957 * * * * SEMAPHORE WAIT" is returned. 
 
db2 upgrade db sample 
SQL1224N  The database manager is not able to accept new 
requests, has terminated all requests in progress, or has 
terminated the specified request because of an error or a forced 
interrupt.  SQLSTATE=55032 
 
db2 migrate db sample 
SQL1224N  The database manager is not able to accept new 
requests, has terminated all requests in progress, or has 
terminated the specified request because of an error or a forced 
interrupt.  SQLSTATE=55032 
 
 
db2diag.log shows error related to SQLO_NOMEM/SQLO_NOMEM_APPH 
eg. 
 
 2009-07-14-19.58.38.474437-240 I904428E483         LEVEL: 
Warning 
 PID     : 8176                 TID  : 183328827744 PROC : 
db2sysc 
 INSTANCE: skharche             NODE : 000          DB   : 
SAMPLE 
 APPHDL  : 0-10                 APPID: 
*LOCAL.skharche.090714235833 
 AUTHID  : SKHARCHE 
 EDUID   : 283                  EDUNAME: db2agent (SAMPLE  ) 
 FUNCTION: DB2 UDB, catalog migration, sqlrlm_catalog_migrate, 
probe:4888 
 DATA #1 : <preformatted> 
 Begin migrating catalog table: SYSTABLES 
 
 2009-07-14-19.58.38.946778-240 E904912E732         LEVEL: 
Warning 
 PID     : 8176                 TID  : 183328827744 PROC : 
db2sysc 
 INSTANCE: skharche             NODE : 000          DB   : 
SAMPLE 
 APPHDL  : 0-10                 APPID: 
*LOCAL.skharche.090714235833 
 AUTHID  : SKHARCHE 
 EDUID   : 283                  EDUNAME: db2agent (SAMPLE  ) 
 FUNCTION: DB2 UDB, SQO Memory Management, 
sqloMemLogPoolConditions, probe:30 
 DATA #1 : <preformatted> 
 Out of memory failure for Application Heap (APPLHEAPSZ). 
 Requested block size           : 2415919104 bytes. 
 Physical heap size             : 131072 bytes. 
 Configured heap size           : 1048576 bytes. 
 Unreserved memory used by heap : 0 bytes. 
 Unreserved memory left in set  : 0 bytes. 
 
 2009-07-14-19.58.38.949835-240 I905645E873         LEVEL: 
Severe 
 PID     : 8176                 TID  : 183328827744 PROC : 
db2sysc 
 INSTANCE: skharche             NODE : 000          DB   : 
SAMPLE 
 APPHDL  : 0-10                 APPID: 
*LOCAL.skharche.090714235833 
 AUTHID  : SKHARCHE 
 EDUID   : 283                  EDUNAME: db2agent (SAMPLE  ) 
 FUNCTION: DB2 UDB, catalog migration, sqlrlmXmlrnStatsUpgrade, 
probe:1917 
 MESSAGE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
           "No memory available in 'Application Heap'" 
           DIA8301C No memory available in the application heap. 
 CALLED  : DB2 UDB, catalog migration, sqlrlmLogErr 
 RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
           "No memory available in 'Application Heap'" 
            DIA8301C No memory available in the application 
heap. 
 DATA #1 : String with size, 26 bytes 
 Migration DMS rc=8b0f0001 
 
 2009-07-14-19.58.38.962053-240 I906519E924         LEVEL: 
Severe 
 PID     : 8176                 TID  : 183328827744 PROC : 
db2sysc 
 INSTANCE: skharche             NODE : 000          DB   : 
SAMPLE 
 APPHDL  : 0-10                 APPID: 
*LOCAL.skharche.090714235833 
 AUTHID  : SKHARCHE 
 EDUID   : 283                  EDUNAME: db2agent (SAMPLE  ) 
 FUNCTION: DB2 UDB, catalog migration, sqlrlm_95toCobra_tablepd, 
probe:1733 
 MESSAGE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
          "No memory available in 'Application Heap'" 
           DIA8301C No memory available in the application heap. 
 CALLED  : DB2 UDB, catalog migration, sqlrlmLogErr 
 RETCODE : ZRC=0x8B0F0001=-1961951231=SQLO_NOMEM_APPH 
           "No memory available in 'Application Heap'" 
           DIA8301C No memory available in the application heap. 
 DATA #1 : String with size, 76 bytes 
 Migration DMS rc=8b0f0001: Migrate Datapart PD Failed: 
SYSIBM.SYSXSROBJECTS 
 
Provided condition : 
* XML tables must exist 
* XML table must have had RUNSTATS issued on it at one point 
  before upgrading. 
 
If there are no statistics gathered on xml tables, then you will 
not be hitting this problem for your upgrade from 32-bit to 
64-bit. 
 
 
Problem here is incorrect usage of structures which have been 
updated in v9.7.
Problem Summary:
**************************************************************** 
* USERS AFFECTED: 
* 
*          All users who are upgrading to DB2 Version 9.7 and 
*          have the following conditions: 
*             * XML tables must exist 
*             * XML table must have had RUNSTATS issued on it 
*               at one point before upgrading. 
* 
*          NOTE: If there are no statistics gathered on XML 
*          tables, then you will not be encounter this problem 
*          during your upgrade from 32-bit to 64-bit. 
* 
**************************************************************** 
* PROBLEM DESCRIPTION: 
* 
*          DB2 Instance can get trap during 32-bit to 64-bit 
*          upgrade (DB2 V9.5 -> DB2 V9.7 or DB2 V9.1 -> DB2 V9.7 
*          or DB2 V8 -> DB2 V9.7) 
* 
*          Problem was caused by incorrect usage of structures 
*          which were introduced in DB2 Version 9.7 GA (FP0) 
* 
**************************************************************** 
* RECOMMENDATION: 
* 
*          First Fixed in DB2 Version 9.7 fix pack 1 
* 
*          Upgrade to DB2 Version 9.7 fix pack 1 or higher. 
* 
*          Use the download links at the top of this APAR to 
*          obtain the fix pack. 
* 
****************************************************************
Local Fix:
Please contact IBM DB2 Support for further assistance on how to 
workaround this issue.
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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
First fixed in DB2 Version 9.7 fix pack 1
Workaround
n/a
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.07.2009
14.12.2009
05.03.2012
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList