INFORMIX SERVER / 5725A3900 / E10 - 

When migrating data from non-UTF to UTF through ER UTF8
replication, even providing up to 4 times the space in target
schema for e.g. CHAR fields, you can incurr data truncation with
data growing through byte expansion, or replication might fail
with ISAM error -202 ('illegal character').

This happens with master replicates and with the (smaller)
source schema ending up being the master schema.
Note that
 - replicates by default are master replicates now
 - the first participant incurred in 'cdr define replicate'
    command, by default, is chosen as master node

****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server documentation prior to 14.10.xC7.   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************

Make sure one of these is true at replicate definition:
 - explicitly specify (UTF) target node as master node, using -M

 - put target participant first in replicate definition
 - force classic (non-master) replicate using --classic option
   (not recommended)

****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server documentation prior to 14.10.xC7.   *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************

The documentation has been corrected.

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

06.12.2021
07.04.2022
07.04.2022