|
Problem IT40798
|
Status: Closed |
ROLLBACK OF DELETE WHEN TABLE IS ALTERED BEFORE WILL CORRUPT THEFUNCTIONAL INDEX
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
The test is performed in AIX with 4k page size and with logged
database.
After alter table..
ALTER TABLE contkey DROP archived_phone;
begin work;
delete from contkey where keyserialno = 32400;
rollback;
a rollback can cause a corruption of the functional index
15:12:34 IBM Informix Dynamic Server Version 14.10.FC8
15:12:34 Assert Failed: Rollback error 126
15:12:34 Results: Log record (OLDRSAM:DELITEM) in log 23, offset
0xc9966c was not rolled back
$oncheck -cIn db5:contkey
Validating indexes for db5:informix.contkey...
Index tmp_index1
Index fragment partition dbspace2 in DBspace dbspace2
ERROR: Bad key information in TBLspace description.
ERROR: Index tmp_index1 for db5:informix.contkey is bad. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC16. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC16. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC16. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 12.10.xC16. *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC16. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 29.04.2022
05.05.2023
05.05.2023 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
