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

XML SCHEMA REGISTER , UPDATE, COMPLETE STATEMENTS MAY MARK THE DB BAD
DURING A ROLL BACK IF AN ERROR IS ENCOUNTERED

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
XML Schema register, update, complete statements may bring DB2 
down on a rollback when an error is encountered due to incorrect 
handling of save points. 
 
       The database will be marked bad and a restart will be 
needed. 
 
Examples of XML Schema statements that may cause this problem 
are : 
 
 db2 "REGISTER XMLSCHEMA http://schemaTest from 
foo/schemaTest.xsd as schemaTest" 
        db2 "COMPLETE XMLSCHEMA schemaTest 
 
Using the following stored procedures to manage XML schema may 
also cause the problem, if an error is encountered during 
processing. 
 
XSR_ADDSCHEMADOC procedure 
XSR_COMPLETE procedure 
XSR_DTD procedure 
XSR_EXTENTITY procedure 
XSR_REGISTER procedure 
XSR_UPDATE procedure
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* XML SCHEMA REGISTER , UPDATE, COMPLETE STATEMENTS MAY MARK   * 
* THE                                                          * 
* DB BAD DURING A ROLL BACK IF AN ERROR IS ENCOUNTERED         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.7 FP1                                          * 
****************************************************************
Local Fix:
After restart, drop the XML schema using the "DROP XSROBJECT 
schemaName" statement and try to re-register the schema.
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
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC65416 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.09.2009
04.02.2010
04.02.2010
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