IT37371: WRONG TABLE GETTING FRAGMENT ADDED ONCE INSERT COMING FROM TRIGGER HITTING PARTITION LIMIT

APAR status

• Closed as program error.

Error 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.
  

Local fix

• This might be a transient problem. To completely prevent it,
  don't rely on AUTOLOCATE for adding a new round-robin fragment.
  

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).                                                  *
  ****************************************************************
  

Problem conclusion

• Fixed in Informix Server 12.10.xC15 and 14.10.xC7.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INFORMIX SERVER

• Fixed component ID

  5725A3900

Applicable component levels