|
Problem IC96727
|
Status: Closed |
SELECT OF A TABLE AFTER A TABLE SPACE ROLLFORWARD OF AN INFLIGHT ONLINE REORG TRANSACTION MAY GET SQL1656C DUE TO A BAD PAGE. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The scenario at risk is an online reorg that is in progress when
the
database crashes and the ensuing crash recovery or database
recovery (including a database rollforward after a restore
rebuild) leaves a table space in restore or rollforward pending.
The ensuing table space recovery takes place and incorrectly
compensates the online reorg transaction.
Any table access afterwards will possibly detect a bad page and
a FODC_BadPage directory will be generated in the
~/sqllib/db2dump directory.
If this table access is a select statement then you may see:
SQL1656C An error occurred while processing data. The operation
could not be
completed, but the database remains accessible. Contact IBM
Software Support.
SQLSTATE=58004 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* The scenario at risk is an online reorg that is in progress *
* when the database crashes and the ensuing crash recovery or *
* database recovery (including a database rollforward after a *
* restore rebuild) leaves a table space in restore or *
* rollforward pending. The ensuing table space recovery takes *
* place and incorrectly compensates the online reorg *
* transaction. *
* *
* Any table access afterwards will possibly detect a bad page *
* and a FODC_BadPage directory will be generated in the *
* ~/sqllib/db2dump directory. *
* *
* If this table access is a select statement then you may see: *
* *
* SQL1656C An error occurred while processing data. The *
* operation *
* could not be completed, but the database remains accessible. *
* Contact IBM *
* Software Support. SQLSTATE=58004 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.5 Fix Pack 3. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 10.5 Fix Pack 3. At a
minimum, this fix should be applied on the server. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.10.2013
10.01.2014
10.01.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
| 10.5.0.4
|
|
