|
Problem IC64258
|
Status: Closed |
IF REORG TABLE INCLUDING INDEX, TABLESPACE + LONGTABLESPACE, IT MAY CAUSE HISTORY LOG CORRUPTION. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Data corruption might happen on the 18th entry when REORG
happened including index+tablespace+longlobspace clause
3045 3243 3237 3634 3A30 3030 363A 3030 0E2C2764:0006:00
3036 4635 4331 3A30 3030 3030 3331 353A 06F5C1:00000315:
3039 3035 3033 3030 3A30 3930 3530 3330 09050300:0905030
303A 413A 3030 3030 3030 3145 3A30 3030 0:A:0000001E:000
3030 3030 303A 3030 3030 3030 3038 3A30 00000:00000008:0
3030 3030 3030 423A 3030 3030 3030 3030 000000B:00000000
3A30 3030 3030 3030 303A 3030 3030 3030 :00000000:000000
3030 3A20 2020 2020 2020 2020 2020 2020 00:
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 200A .
473A 543A 463A 5553 4520 3135 2020 2020 G:T:F:USE 15
2020 2020 2020 203A 3230 3039 3130 3231 :20091021
3133 3430 3132 3A53 3030 3038 3830 372E 134012:S0008807.
4C4F 473A 5330 3030 3838 3038 2E4C 4F47 LOG:S0008808.LOG
3A30 3030 3030 3030 3030 3030 303A 2D20 :000000000000:-
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 3A2D 3A20 2020 2020 2020 :-:
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 200A .
The 18th field in this case is USE 15, which is not expected.
The expected entry should be something similar to
20091102094625001, which shouldn't include any space.
The corruption of history file may fail database backup request. |
| Problem Summary: |
Problem Description:
IF REORG TABLE INCLUDING INDEX, TABLESPACE + LONGTABLESPACE, IT
MAY CAUSE HISTORY LOG CORRUPTION.
Problem Summary:
Data corruption might happen on the 18th entry when REORG
happened including index+tablespace+longlobspace clause
3045 3243 3237 3634 3A30 3030 363A 3030 0E2C2764:0006:00
3036 4635 4331 3A30 3030 3030 3331 353A 06F5C1:00000315:
3039 3035 3033 3030 3A30 3930 3530 3330 09050300:0905030
303A 413A 3030 3030 3030 3145 3A30 3030 0:A:0000001E:000
3030 3030 303A 3030 3030 3030 3038 3A30 00000:00000008:0
3030 3030 3030 423A 3030 3030 3030 3030 000000B:00000000
3A30 3030 3030 3030 303A 3030 3030 3030 :00000000:000000
3030 3A20 2020 2020 2020 2020 2020 2020 00:
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 200A .
473A 543A 463A 5553 4520 3135 2020 2020 G:T:F:USE 15
2020 2020 2020 203A 3230 3039 3130 3231 :20091021
3133 3430 3132 3A53 3030 3038 3830 372E 134012:S0008807.
4C4F 473A 5330 3030 3838 3038 2E4C 4F47 LOG:S0008808.LOG
3A30 3030 3030 3030 3030 3030 303A 2D20 :000000000000:-
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 3A2D 3A20 2020 2020 2020 :-:
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 200A .
The 18th field in this case is USE 15, which is not expected.
The expected entry should be something similar to
20091102094625001, which shouldn't include any space.
The corruption of history file may fail database backup request. |
| Local Fix: |
Remove db2rhist.asc and db2rhist.bak from database directory |
| available fix packs: |
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 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 9a 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 |
Problem is first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
Remove db2rhist.asc and db2rhist.bak from database directory |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.11.2009
13.05.2010
13.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
