|
Problem IC76955
|
Status: Closed |
MISSING XML VALUES INDEX ENTRIES FROM CREATE INDEX. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
There is a possibility that an XML Index Object can be created
and still have XML
Values index keys missing for an Indexable XML document that was
concurrently
being updated through some other transaction running an XML
Transform statement
during the time of CREATE INDEX.
This can only happen in the following conditions:
1. CREATE INDEX starts
2. A separate transaction performs an XML UPDATE on Document
which is currently being indexed
3. CREATE INDEX finishes
The create index and xml update will terminate normally, but the
resulting INDEX could have missing
xml values entries for those documents which where updated. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users with XML column type. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When update on XML columns are done during XML index *
* creation, the new XML data may be lost. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to fixpack 5 to fix the issue. *
**************************************************************** |
| Local Fix: |
Avoid running any XML Updates concurrently with Create Index. |
| available fix packs: |
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 |
Problem first fixed in Db2 V9.7 fixpack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2011
03.01.2012
03.01.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP5
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.5
|
 |
