Informix - Problembeschreibung
Problem IT27533 | Status: Geschlossen |
ASSERT FAILURE MEMORY CORRUPTION FOLLOWED BY 937 ERROR ON INSERTINTO TABLE WITH BTS INDEX | |
Produkt: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problembeschreibung: | |
There is memory block header corruption detected in the free list linked pointers. Someone wrote to the block after the block was freed. After the af file , all attempts to insert something to the table always return -937. Sample Assertion failure and stack of thread trying to insert is mentioned below. Multiple variations of behavior was also seen after the AF. Some times engine crashed while other time hang was seen with a deadlock. onstat -g wmx show waits on different mutexes with a deadlock. Once after the the AF, when you try inserting records in table using dbaccess we get the following : Eg. if you then try to insert records into the table in dbaccess. INSERT INTO notice VALUES ( 0, 30, "xxxxx", 5, NULL, "ddd", NULL, CURRENT, "2018-1-14 23:59:59", 10, "ddd" ); (BTSA1) - bts clucene error: IO error: FSE IO cannot open file /informix/i_bts_notice_1/1049072/segments Assert failure message of memory corruption : ------------------------------------------------------- 10:08:58 Pool 'SES.126.164' (0x4d995040) 10:08:58 Bad free block 0x4d9cb458 10:08:58 Assert Warning: Memory free block header corruption detected in mt_shm_free 5 10:08:58 IBM Informix Dynamic Server Version 12.10.FC10 10:08:58 Who: Session(126, informix@server, 2479, 0x44cea618) Thread(164, sqlexec, 44caa6a8, 18) File: mtshpool.c Line: 2857 10:08:58 Results: Pool free list repaired 10:08:58 Action: Please notify IBM Informix Technical Support. 10:08:58 stack trace for pid 28861 written to /informix/products/12.10.FC10/tmp/af.48c0ee1 10:08:58 See Also: /informix/products/12.10.FC10/tmp/af.48c0ee1 10:08:58 Memory free block header corruption detected in mt_shm_free 5 10:08:58 Assert Failed: Memory freed at bad boundary. 1 blocks at 4d9cb470 10:08:58 IBM Informix Dynamic Server Version 12.10.FC10 10:08:58 Who: Session(126, informix@server, 2479, 0x44cea618) Thread(164, sqlexec, 44caa6a8, 18) File: mtshblk.c Line: 526 10:08:58 Results: Memory lost 10:08:58 Action: Please notify IBM Informix Technical Support. 10:08:58 stack trace for pid 28861 written to /informix/products/12.10.FC10/tmp/af.48c0ee1 10:08:58 See Also: /informix/products/12.10.FC10/tmp/af.48c0ee1, shmem.48c0ee1.0 Stack trace of thread trying to insert - ------------------------------------------ Stack for thread: 165 sqlexec base: 0x000000004d425000 len: 69632 pc: 0x000000000140e8a6 tos: 0x000000004d432c20 state: mutex wait vp: 18 (oninit) yield_processor_mvp (oninit) mt_lock_wait (oninit) mt_slock (/informix/products/12.10.FC10/extend/bts.3.11/bts.bld) bts_lock_acquire_read_lock (/informix/products/12.10.FC10/extend/bts.3.11/bts.bld) bts_init (/informix/products/12.10.FC10/extend/bts.3.11/bts.bld) bts_am_insert_on_vpid (/informix/products/12.10.FC10/extend/bts.3.11/bts.bld) bts_am_insert (oninit) udrlm_clang_execute_internal (oninit) udrlm_clang_execute (oninit) udrlm_exec_routine (oninit) udr_execute (oninit) vii_insert (oninit) fm_idxinsert (oninit) fmwrite (oninit) aud_sqiswrite (oninit) chkrowcons (oninit) addone (oninit) insone_next (oninit) doinsert (oninit) excommand (oninit) sq_execute (oninit) sqmain (oninit) spawn_thread (oninit) th_init_initgls (oninit) startup | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users of IDS 12.10.xC10 and older releases. * **************************************************************** * PROBLEM DESCRIPTION: * * Assert failure memory corruption followed by -937 error on * * insert into table with BTS index. * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 24.12.2018 07.10.2019 07.10.2019 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
12.10.xC11 | |
Problem behoben lt. FixList in der Version |