DB2 - Problem description
Problem IC61813 | Status: Closed |
UNPROCESSED XML LOG RECORDS DURING ROLLFORWARD | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
During a rollforward operation of a table containing XML data, there is a possibility that some XML log records could be unintentionally ignored. This can only happen if the XML data is in a separate table space from that of the base table data and if there is also no LOB or Long Field columns in the table. This APAR corrects the issue and ensures that all XML log records are processed during rollforward operations. This APAR also ensures that an error message will be returned if the user incorrectly attempts to rollforward through only the XML log records, and not the associated base table log records as well. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * XML Users * **************************************************************** * PROBLEM DESCRIPTION: * * If XML log records are ignored during roll forward then * * users may find XML tables are missing * * updates/inserts/deletes. * * If the users incorrectly attempt to roll forward only the * * XML tablespace log records without rolling forward through * * the base data table as well, then no error message returned * * and the procedure appears to succeed. * **************************************************************** * RECOMMENDATION: * * Upgrade to 9.05.005 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
This APAR corrects both conditions. After installing this APAR none of the XML log records will be ignored during roll forward operations. If the user attempts to roll forward the XML tablespace only then an error will be returned. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.06.2009 17.02.2010 17.02.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.5.005 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.5 |