|
Problem IT44925
|
Status: Closed |
COLLECTION SUBQUERY RETURNING A LVARCHAR CAN THROW ASSERT FAILED IN CHECK_SUBQUERY_REMAKE
|
| product: |
INFORMIX SERVER / 5725A3900 / E10 - |
| Problem description: |
Consider a table with the following schema:
file_name lvarchar(255) not null
The query below with produce an assert failure with the
following stack
select doc_name from
(select
(select file_name from ...... ) as doc_name
from ...)
0x00000000008ff69d (oninit) check_subquery_remake
0x00000000008ffa51 (oninit) exsubq
0x00000000016cf8f5 (oninit) ev_cb
0x00000000016c692f (oninit) new_eval
0x0000000000877a00 (oninit) evalcols
0x0000000000875f3d (oninit) getrow
0x00000000008755de (oninit) fetchrow
0x0000000000608244 (oninit) exfetch
0x0000000000ab8a2d (oninit) sql_nfetch
0x0000000000ab8304 (oninit) sq_nfetch
0x0000000000b9701e (oninit) sqmain |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC11. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 14.10.xC11. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix Server 14.10.xC11. *
**************************************************************** |
| Comment |
Fixed in Informix Server 14.10.xC11. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 09.11.2023
07.06.2024
07.06.2024 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
