|
Problem IC71052
|
Status: Closed |
INSTANCE CRASH CAN BE CAUSED BY DATABASE MIGRATION FROM DB2 V9.1 TO V9.7 OF DB BACKUP IMAGE INCLUDING XML COLUMN |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When database restore is attempted on DB2 V9.7 with the older
version of backup ( from V9.1 ) 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-08-13-18.03.42.192034-240 I949473E489 LEVEL:
Warning
PID : 27210 TID : 47086397548864PROC :
db2sysc 0
INSTANCE: XXXX NODE : 000 DB : XXXX
APPHDL : 0-249 APPID: *XXXX
AUTHID : XXXX
EDUID : 202 EDUNAME: db2agent (XXXX ) 0
FUNCTION: DB2 UDB, catalog migration, sqlrlm_catalog_migrate,
probe:4945
DATA #1 : <preformatted>
Begin migrating catalog table: SYSTABLES
2010-08-13-18.03.45.114604-240 I949963E1577 LEVEL: Severe
PID : 27210 TID : 47086397548864PROC :
db2sysc 0
INSTANCE: XXXX NODE : 000 DB : XXXX
APPHDL : 0-249 APPID:
*LOCAL.nytit011.100813215255
AUTHID : XXXX
EDUID : 202 EDUNAME: db2agent (XXXX ) 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] 0x00002AD0EAAC93FA pdLog + 0x398
[1] 0x00002AD0ED0B72A8 _Z15xmlrnLogErrorRcmiiPc + 0xD6
[2] 0x00002AD0ECB155CC
_Z29sqlrlmUpgradeXmlrnStatsPathV9P8sqlrr_cbPcjPjS2_PP14XmlrnStat
sPath
+
0xFE
[3] 0x00002AD0ECB16680
_Z28sqlrlmXmlrnStatsUnpackDescV9P8sqlrr_cbPcjPjS2_PP10XmlrnStats
+ 0x310
[4] 0x00002AD0ECB162A1
_Z25sqlrlmUpgradeXmlrnStatsV9P8sqlrr_cbPcjPjPP14XmlrnStatsInfo +
0x275
[5] 0x00002AD0ECB145E5
_Z23sqlrlmXmlrnStatsUpgradeP8sqeAgentP14v95sqlrg_genpdPPcPj +
0x8F
[6] 0x00002AD0ECB13DD1
_Z24sqlrlm_95toCobra_tablepdP8sqeAgenttPcP10SQLD_
VALUEP8sqlr_tidP11v95sqlrg_pdmP20vCobrasqlrg_2pt_namePS1_Pj +
0xF43
[7] 0x00002AD0ECA3B796
_Z26sqlrlm_95toCobra_systablesP8sqeAgenttP10SQLD_
VALUEP8sqlr_tidPcPS5_PlPbS8_ + 0x384
[8] 0x00002AD0ECAE7959
_Z19sqlrlm_catalogFixupP8sqlrr_cbtllm17sqlrlm_cat
ChangesPc8sqlr_tidPS3_P18sqlrlm_runstatsCmd + 0x1243
[9] 0x00002AD0EC9524EC
_Z22sqlrlm_catalog_migrateP8sqeAgentsP5sqlca +
0x1570 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* INSTANCE CRASH CAN BE CAUSED BY DATABASE MIGRATION FROM DB2 *
* V9.1 TO V9.7 OF DB BACKUP IMAGE INCLUDING XML COLUMN *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fixpak 3. *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 V9.7 Fixpak 3. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC72983
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.09.2010
29.04.2011
29.04.2011 |
| 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.4
|
 |
