INFORMIX EXT XP / 5724C1900 / 851 - Informix 8.51

When a fragmented table is created, it must acquire a tabid bit
in the Safewrite area "SW_CONFIG_MGR_TABID".  When a fragmented
table is dropped or consumed by another fragmented table it
should remove this bit to free it for another fragmented table
to use.  However, when a fragmented table is attached to an
existing fragmented table with hybrid fragmentation that the
TABID bit for the consumed fragmented table is not removed.

Consider this scenario:
Multiple coservers
DBA detaches a fragment from a hybrid fragmented table
DBA does some sort of work on the detached table (drops and
recreates, truncates , deletes the rows, updates rows, etc)
DBA reattaches the fragmented detached table back into the
original hybrid fragmented table

Over a long period of time, these operations on the hybrid
fragmented table will "leak" tabid bitmap entries for the
consumed table resulting in a full bitmap that causes the
following scenarios:

-261 error trying to create ANY fragmented table
-23521 or -23525 error when trying to detach a fragment from any
hybrid fragmented table

****************************************************************
* USERS AFFECTED:                                              *
* Create/Alter fragmented tables                               *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to XPS-8.51.xC4                                       *
****************************************************************

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

01.01.2016
16.06.2017
16.06.2017