Informix - Problem description
Problem IT43578 | Status: Closed |
AF IN OPLOOKSUBQ DURING PREPARE OF MULTIPLE SQL STATEMENT WHICH INCLUDES SET ENVIRONMENT AND SSC IS ENABLED | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
The prepare of a string that has multiple SQL statements, one of which is SET ENVIRONMENT, will fail with an Assert Failure if the Shared Statement Cache is enabled. The stack will be of the form: afstack mt_ex_throw_sig afsig_handler oplooksubq oplooksubq oplooksubq foldviews qd_expandviews bldstructs sqcmd sq_prepare sqmain | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC16 and 14.10.xC11. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC16 or 14.10.xC11 (when * * available). * **************************************************************** | |
Local Fix: | |
A workaround is to either disable the Shared Statement Cache (set onconfig STMT_CACHE 0) or to set the undocumented onconfig parameter MULTI_STMT_THRESHOLD to 1. | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC16 and 14.10.xC11. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC16 or 14.10.xC11 (when * * available). * **************************************************************** | |
Comment | |
Fixed in Informix Server 12.10.xC16 and 14.10.xC11. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.04.2023 18.05.2023 18.05.2023 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |