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

UPGRADE FROM DB2 9.1 TO 9.7 FAILS DUE TO XMLRN_RC_BUFFER_TOO_SMALL ERROR

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
You may experience the following error while trying to upgrade a 
database containing XML data from V9.1 to V9.7 using 
restore-upgrade db approach. 
 
db2 restore db SAMPLE from ... TAKEN AT ... 
DB20000I  The RESTORE DATABASE command completed successfully. 
 
$ db2start 
SQL1063N  DB2START processing was successful. 
 
$ db2 connect to SAMPLE 
SQL5035N  The database must be upgraded to the current release. 
 
$ db2 upgrade database 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 contains the following error entry: 
 
FUNCTION: DB2 UDB, catalog migration, 
sqlrlmUpgradeXmlrnStatsPathValV9, 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] 0x00002B11768CD914 pdLog + 0x398 
  [1] 0x00002B1178E4E2D8 _Z15xmlrnLogErrorRcmiiPc + 0xD6 
  [2] 0x00002B11788B8220 
_Z32sqlrlmUpgradeXmlrnStatsPathValV9P8sqlrr_cbPcjPjS2_PP17XmlrnS 
tatsPathVal + 0xFC 
  [3] 0x00002B11788B8FE0 
_Z28sqlrlmXmlrnStatsUnpackDescV9P8sqlrr_cbPcjPjS2_PP10XmlrnStats 
+ 0x382 
  [4] 0x00002B11788B8B8F 
_Z25sqlrlmUpgradeXmlrnStatsV9P8sqlrr_cbPcjPjPP14XmlrnStatsInfo + 
0x275 
  [5] 0x00002B11788B730B 
_Z23sqlrlmXmlrnStatsUpgradeP8sqeAgentP14v95sqlrg_genpdPPcPj + 
0x8B 
  [6] 0x00002B11788B6B29 
_Z24sqlrlm_95toCobra_tablepdP8sqeAgenttPcP10SQLD_VALUEP8sqlr_tid 
P11v95sqlrg_pdmP20vCobrasqlrg_2pt_namePS1_Pj + 0xF19 
  [7] 0x00002B11787E0C1F 
_Z26sqlrlm_95toCobra_systablesP8sqeAgenttP10SQLD_VALUEP8sqlr_tid 
PcPS5_PlPbS8_ + 0x397 
  [8] 0x00002B117888BC21 
_Z19sqlrlm_catalogFixupP8sqlrr_cbtllm17sqlrlm_catChangesPc8sqlr_ 
tidPS3_P18sqlrlm_runstatsCmd + 0x121F 
  [9] 0x00002B11786F8C53 
_Z22sqlrlm_catalog_migrateP8sqeAgentsP5sqlca + 0x15B1 
 
This behaviour is similar to APAR IC66957; however, it is a 
separate issue as it occurs at a different probe.
Problem Summary:
APAR fix was provided in Fixpack 4.
Local Fix:
Restore and upgrade the database on V9.7 base, and then install 
Fixpack 2.
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
The fix resolves the problem that was preventing successful 
upgrade from 9.1 to 9.7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.01.2011
09.05.2011
09.05.2011
Problem solved at the following versions (IBM BugInfos)
9.1.,
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList