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

THE INSTANCE CAN CRASH BY RESTORING OR MIGRATING DATABASE INCLUDING
XML COLUMN TABLE FROM OLDER VERSION DATABASE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When database restore is attempted on v9.7fp1 with the older 
version database backup image which includes XML column tables, 
the restoring database can fail with SQL2519N error and the 
instance goes to down during database migration phase. 
The database migration command also fails with SQL1224N error 
and the instance goes to down. 
db2diag.log shows XMLRN_RC_BUFFER_TOO_SMALL error in 
sqlrlmUpgradeXmlrnStatsPathV9 duringmigrating catalog table: 
SYSTABLES as below. 
 
2010-02-23-12.52.00.640000+540 I384069H501        LEVEL: Warning 
PID     : 3160                 TID  : 2660        PROC : 
db2syscs.exe 
INSTANCE: DB2_04               NODE : 000         DB   : DB01 
APPHDL  : 0-7                  APPID: *LOCAL.DB2_04.100223035104 
AUTHID  : ADMINISTRATOR 
EDUID   : 2660                 EDUNAME: db2agent (DB01) 0 
FUNCTION: DB2 UDB, catalog migration, sqlrlm_catalog_migrate, 
probe:4945 
DATA #1 : <preformatted> 
Begin migrating catalog table: SYSTABLES 
 
2010-02-23-12.52.03.921000+540 I384572H1436       LEVEL: Severe 
PID     : 3160                 TID  : 2660        PROC : 
db2syscs.exe 
INSTANCE: DB2_04               NODE : 000         DB   : DB01 
APPHDL  : 0-7                  APPID: *LOCAL.DB2_04.100223035104 
AUTHID  : ADMINISTRATOR 
EDUID   : 2660                 EDUNAME: db2agent (DB02) 0 
FUNCTION: DB2 UDB, catalog migration, 
sqlrlmUpgradeXmlrnStatsPathV9, probe:30 
MESSAGE : ZRC=0x82A4007C=-2103181188=XMLRN_RC_BUFFER_TOO_SMALL 
          "buffer too small" 
          DIA11100E An XML runtime node manager error has 
occurred.   "". 
DATA #1 : String, 4 bytes 
none 
CALLSTCK: 
  [0] 0x6CC8FB63 pdLog + 0x2E3 
  [1] 0x6E77A873 xmlrnLogErrorRc + 0xB7 
  [2] 0x6E584E42 
?sqlrlmUpgradeXmlrnStatsPathV9.@@YAHPAUsqlrr_cb@@PADIPAI2PAPAVXm 
lrnStatsPath@@@Z 
+ 0xB6 
  [3] 0x6E584B6F 
?sqlrlmXmlrnStatsUnpackDescV95.@@YAHPAUsqlrr_cb@@PADIPAI2PAPAVXm 
lrnStats@@@Z 
+ 0x295 
  [4] 0x6E584806 
?sqlrlmUpgradeXmlrnStatsV95.@@YAHPAUsqlrr_cb@@PADIPAIPAPAVXmlrnS 
tatsInfo@@@Z 
+ 0x1C6 
  [5] 0x6E58448F 
?sqlrlmXmlrnStatsUpgrade.@@YAHPAVsqeAgent@@PAVv95sqlrg_genpd@@PA 
PADPAI@Z 
+ 0x9F 
  [6] 0x6E583EB7 
?sqlrlm_95toCobra_tablepd.@@YAHPAVsqeAgent@@GPADPAUSQLD_VALUE@@P 
AUsqlr_tid@@PAUv95sqlrg_pd@@IPAVvCobrasqlrg_2pt_name@@PAPADPAI@ 
+ 0xC26 
  [7] 0x6E5533C3 sqlrlm_95toCobra_systables + 0x2A1 
  [8] 0x6E52B772 sqlrlm_catalogFixup + 0xE78 
  [9] 0x6E41A88C sqlrlm_catalog_migrate + 0x10E2
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Migration user                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The restoring database can fail with SQL2519N error and      * 
* theinstance goes to down during database migration phase     * 
* ifdatabase restore is attempted on v9.7fp1 with the          * 
* olderversion database backup image which includes XML        * 
* columntables.                                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 Version 9.7 FixPak 2                          * 
****************************************************************
Local Fix:
available fix packs:
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 6 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 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
Problem was first fixed in Version 9.7 FixPak 2
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC67171 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.03.2010
16.07.2010
27.07.2010
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList