Informix - Problem description
Problem IT06194 | Status: Closed |
OPTIMIZING QUERY WITH A SUBQUERY IN THE WHERE CLAUSE CAN CAUSE A CRASH IN SQOPTIM() | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
If you run a query which has a subquery in its WHERE clause, the optimization of such query can lead to a crash in the sqoptim() function. On 12.10.FC4 this leads to a complete crash of the instance, on 12.10.FC4W1 the AF and shmem files are generated, the client application receives the error -874, but the instance stays online. Stack trace of the failing thread is the same on both versions: afstack afhandler affail_interface mt_ex_throw_sig afsig_handler <signal frame> sqoptim bldstructs sqcmd sq_cmnd sq_prepare sqmain spawn_thread th_init_initgls startup | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of 12.10.xC4. * **************************************************************** * PROBLEM DESCRIPTION: * * A query involving subqueries may result in assertion failure * * and -874 error under the following conditions: * * - there are more than 1 main query tables * * - there are more than 1 subquery tables * * - subquery is flattened * * - one of the subuqery tables has a unique index on the * * join column between subquery table and a main query table * * - the other subquery does not have such a unique index * **************************************************************** * RECOMMENDATION: * * Update to IBM Informix Server 12.10.xC5. * **************************************************************** | |
Local Fix: | |
The problem doesn't reproduce if the subquery flattening is turned off. Set the NO_SUBQF environment variable to 1 in the client environment. | |
Solution | |
Problem Fixed In IBM Informix Server 12.10.xC5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 19.12.2014 16.10.2015 16.10.2015 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
12.10.xC5 | |
12.10.xC5.W1 |