Informix - Problem description
Problem IT28278 | Status: Closed |
UTF8 REPLICATION CAN CRASH WITH INADVERTENT SCHEMA DIFF BEYOND ONLY CHAR LIKE COLUMNS | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
A crash in following stack can be reproduced when schema differences between replicated tables exceed mere *CHAR* column size differnces (which are allowed and may be required even for code set conversion): 11:02:14 Assert Failed: Condition Failed (Bad allocation size (-1912602623) for pool 'CDRD_2' (0x4aca8040)), In (mt_shm_malloc_segid) 11:02:14 Who: Session(272, informix@darkwood, 0, 0x452b6c08) Thread(300, CDRD_2, 4527e438, 1) File: mtshpool.c Line: 4701 (oninit) afstack (oninit) afhandler (oninit) affail_interface (oninit) mem_asfail (oninit) mt_shm_malloc_segid (oninit) mt_malloc (oninit) cdrCnvFromUTF8 (oninit) dsiCopyColumn (oninit) dsiGetReplRow (oninit) dsiResolverThread (oninit) cdrTrampolineThread (oninit) th_init_initgls (oninit) startup Presumably (master) replicate definition should have failed up front verifying participating schemas, but is a bit too relaxed regarding allowed schema differences. The problem does not occur if schemas were congruent (regarding all non *CHAR* columns) at replicate definition time and target table got altered with replication already in place. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of IDS prior to 12.10.xC13. * **************************************************************** * PROBLEM DESCRIPTION: * * UTF8 replication can crash with inadvertent schema * * differences beyond only char like columns. * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
Local Fix: | |
Make sure only difference between schemas is in *CHAR* columns' sizes when defining a --UTF8=y replicate. | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.03.2019 24.09.2019 24.09.2019 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC13 | |
Problem solved according to the fixlist(s) of the following version(s) |