Informix - Problem description
Problem IT41816 | Status: Closed |
SQL WITH "CONNECT BY" CLAUSE THROWS ERROR -264 COULD NOT WRITE TO A TEMPORARY FILE. / ISAM ERROR -112 | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
The server throws a 264/112 error when ISQL runs the following SQL file: -- t2.sql -- SETUP phase drop table if exists t1; drop table if exists t2; create table t1(c1 int); create table t2(c1 serial unique not null); --create table t2(c1 serial not null); -- no error if there is no index insert into t1 values (1); --insert into t1 values (2); -- no errors if there is a second row in the table -- RUN phase insert into t2 select 0; select first 1 c1 from t1 connect by 1=1; -- t2.sql Same SQL file works without errors from dbaccess, but only because dbaccess does things a little bit different, like doing a SQ_RELEASE for the insert statement which means both insert and select (.. connect by) will use the same statement id. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.xC9. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 14.10.xC9. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.xC9. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 14.10.xC9. * **************************************************************** | |
Comment | |
Fixed in Informix Server 14.10.xC9. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 18.08.2022 05.10.2022 05.10.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |