INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10

It seems to see the issue the table that the select/delete are
occurring on would use a BSON type, and additionally there would
be indexes of the BSON type indexing the BSON data.

For example, consider the following SQL run on an updatable
secondary:

begin work;

select c2::json from t1 where c1 = 450;
delete from t1 where c1 = 450;

select c1, bson_value_lvarchar(c2,"col21") from t1
where
bson_get(c2,"col21") =
'{"col21":"gomviyudfxdosbtwmcbrfxgrqvhqrpxxfmuomrttoyiizdenfhfmg
ngwjpoceoakawamntgdtqlstrhazmnhatelkunpipziozxdudhntuhoooopddwfw
aqhxfyfxxqlynosqxhluqziepxjttorwgatmyyjxowvdkptkwgemhmtxje"}'::j
son::bson;

In this case, the 2nd select which would be trying to return the
same row that was deleted, could potentially return the 12097
error.  If this 2nd query didn't use an index on the BSON column
and just did a sequential scan instead, it would just return "no
rows found".

****************************************************************
* USERS AFFECTED:                                              *
* Users of IDS prior to 12.10.xC13.                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* 12097 error possible on updatable secondary if transaction   *
* deletes a row and then runs query which could potentially    *
* return that row.                                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

10.12.2018
26.09.2019
26.09.2019

12.10.xC13