Informix - Problem description
Problem IT37371 | Status: Closed |
WRONG TABLE GETTING FRAGMENT ADDED ONCE INSERT COMING FROM TRIGGER HITTING PARTITION LIMIT | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
Consider a table A with a trigger defined on it and the trigger inserting into a different table B, now B getting full, so next insert would have to add a new round-robin fragment (with B being RR fragmented and AUTOLOCATE on). What can happen instead, with next activity on A executing the trigger, is that A is getting a fragment added while B remains full, and since nothing changed in B, this might even happen again. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC15 and 14.10.xC7. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when * * available). * **************************************************************** | |
Local Fix: | |
This might be a transient problem. To completely prevent it, don't rely on AUTOLOCATE for adding a new round-robin fragment. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC15 and 14.10.xC7. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when * * available). * **************************************************************** | |
Comment | |
Fixed in Informix Server 12.10.xC15 and 14.10.xC7. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 22.06.2021 31.08.2021 31.08.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |