INFORMIX SERVER / 5725A3900 / B70 - IDS 11.70

A UNION query with corresponding LVARCHAR columns in its 
branches can fail in various ways if those lvarchar columns were 
defined with differing sizes and NOT NULL constraints. 
 
E.g.: 
 
create table lvc1 (text lvarchar(200) not null); 
create table lvc2 (text lvarchar(300) not null); 
select * from lvc1   UNION ALL   select * from lvc2; 
 
On Intel platforms (Linux, Windows) a UNION ALL query of this 
type would cause a memory assertion (and hang the backend thread 
if so configured) during 'describe': 
 
 (oninit) afstack 
 (oninit) mt_ex_throw_sig 
 (oninit) afsig_handler 
 (Linux) <signal frame> 
 (oninit) putcoltype 
 (oninit) putndescribe 
 (oninit) sq_ndescribe 
 (oninit) sqmain 
 (oninit) spawn_thread 
 (oninit) th_init_initgls 
 (oninit) startup 
 
On e.g. AIX the same query would run into: 
 
  486: Illegal data type found during data conversions. 
 
Without the ALL keyword this would cause: 
 
 9832: Could not find routine (compare) while resolving compare 
routine.

**************************************************************** 
* USERS AFFECTED:                                              * 
* 12.10.XCX                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10.XC6                      * 
****************************************************************

Alter the LVARCHAR definitions to have same size (would be slow 
alter) or remove at least one NOT NULL constraint (quick alter).

Problem Fixed In IBM Informix Server 12.10.XC6

not known / see Local fix

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

17.08.2015
30.12.2015
30.12.2015

12.10.xC6