Informix - Problem description
Problem IT39582 | Status: Closed |
DEFRAGMENT TABLE CORRUPTS INDEX STRUCTURE | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
After a defragment table subsequent operations like an insert report corruptions on one of the existing indexes on the table. On LINUX we can see a assertion with 0x000000000170643c (oninit) bycmpr 0x0000000000e49a69 (oninit) bycompare 0x0000000000e43bb9 (oninit) btcpybck 0x0000000000e45435 (oninit) btusearch 0x0000000000e37123 (oninit) btadditem 0x0000000000e38d2f (oninit) rsbtadditem 0x00000000015cb9dd (oninit) fm_idxinsert 0x00000000015a571d (oninit) fmwrite 0x000000000071d403 (oninit) aud_sqiswrite 0x000000000090c733 (oninit) chkrowcons 0x00000000008ae301 (oninit) addone 0x00000000008aaaa1 (oninit) ins1row 0x00000000008ad29b (oninit) insone_next 0x00000000009179c0 (oninit) doinsert On AIX we see 07:02:39 Assert Warning: No parent node 07:02:39 Who: Session(49, informix@db-vyvoj, 8585774, 70002000139b068) Thread(67, sqlexec, 70002000135bd40, 8) File: rskey.c Line: 1321 0x00000001006baa7c (oninit)kybad 0x00000001001b7ac8 (oninit)btusearch 0x00000001001b5c58 (oninit)btadditem 0x00000001001ba508 (oninit)rsbtadditem 0x0000000100a14da0 (oninit)isbtadditem 0x00000001005a880c (oninit)fm_idxinsert 0x00000001006f48f4 (oninit)fmwrite 0x00000001007ff3c4 (oninit)aud_sqiswrite 0x0000000100fb64b4 (oninit)chkrowcons 0x0000000100fd1be4 (oninit)addone 0x0000000100fd17cc (oninit)ins1row 0x0000000100fccf3c (oninit)insone_next or Database selected. 271: Could not insert new row into the table. 105: ISAM error: bad isam file format. Error in line 1 Near character position 104 Database closed. $ oncheck -cDI db:table Validating indexes for db:informix.tab... Index i_tab Index fragment partition rootdbs in DBspace rootdbs ERROR: Bad key information in TBLspace description. ERROR: Keys in leaf node 0x1 have no rowids.ISAM error: illegal key descriptor (too many parts or too long). | |
Problem Summary: | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.01.2022 02.02.2023 17.02.2023 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |