|
Problem IT23619
|
Status: Closed |
TRANSACTION ID TABLE OVERFLOWED DURING HADR REPLAY |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
During replay of large transactions (e.g. an index reorg) on the
standby HADR database the transaction table may overflow and
bring down the standby with FODC_Panic.
The db2diag.log shows:
EDUID : 126523 EDUNAME: db2redom (sample) 0
FUNCTION: DB2 UDB, data protection services, sqlptintMore,
probe:701
DATA #1 : <preformatted>
Current usable transaction entries = 16639
...
Current usable transaction entries = 16767
...
Current usable transaction entries = 16895
...
Current usable transaction entries = 131071
EDUID : 126523 EDUNAME: db2redom (sample) 0
FUNCTION: DB2 UDB, data protection services, sqlptintMore,
probe:310
MESSAGE : ZRC=0x87100028=-2028994520=SQLP_TBOF
"Transaction ID table overflowed class 7 rc 40"
DIA8537C The transaction table overflowed.
DATA #1 : <preformatted>
Current usable transaction entries = 131071
...
FUNCTION: DB2 UDB, base sys utilities, sqle_panic, probe:10
MESSAGE : ADM14001C An unexpected and critical error has
occurred: "Panic". |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 Version 11.1 Mod 3 FixPack 3 *
**************************************************************** |
| Local Fix: |
Re-initialize the standby HADR database from a new backup |
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Db2 Version 11.1 Mod 3 FixPack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 04.01.2018
19.03.2018
19.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
