|
Problem IT18236
|
Status: Closed |
ASSERT FAILURE MESSAGE "ATTEMPTING TO ALLOCATE SLOT ON IN-USE OLD VERSION PAGE" IS UNHELPFUL
|
| product: |
INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70 |
| Problem description: |
When a table is altered with an in-place alter mechanism the
bitmap value for all existing data pages is updated to value 0xc
to indicate "very full" thereby blocking further attempts to
insert new rows onto that page. When secondary servers, such as
HDR or RSS, are used there are occasions when the bitmap page on
the secondary server may not be updated in the same way. If the
server is promoted to a primary a later insert operation on the
table may generate an Assert Failure of the form:
allocvslot: Attempting to allocate slot on in-use old (0)
version page - new version is 1
allocvslot:partnum 0x10014c tr_pagenum 1
with a similar message in the online log of the form:
Assert Failed: Slot allocation error for
'test:"informix".tab442'
IBM Informix Dynamic Server Version 11.70.FC7XBU
Who: Session(49, informix@host1, 22282406, 7000000203a93f0)
Thread(81, sqlexec, 700000020371f60, 1)
File: rsbitmap.c Line: 3285
Results: Internally corrected
Action: Run 'oncheck -cDI test:"informix".tab442'
The result is that the bitmap is internally corrected and the
insert operation succeeds. For this specific discrepancy in
expected and actual bitmap values the Assert Failure is
unhelpful and its generation may cause further problems on
replicated servers if the generation of the AF file takes a long
time potentially leading to a failover scenario. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix clustering. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to IBM Informix Server 11.70.xC9 *
**************************************************************** |
| Local Fix: |
A workaround to avoid this situation is to resolve the
outstanding in-place alters by performing a dummy update on
every row of the table. |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.12.2016
22.06.2017
22.06.2017 |
| Problem solved at the following versions (IBM BugInfos) |
11.70.xC9
|
| Problem solved according to the fixlist(s) of the following version(s) |
