Re: Any Known Upgrade Problems?
Posted in 1998
Topics: Installation, Setup & Upgrades, Error Codes & Troubleshooting, Connectivity: ESQL/C, 4GL & Embedded SQL
Jonathan Leffler wrote:
> On Thu, 17 Sep 1998, Dan Frascella wrote:
> > I am going to have to upgrade my current tools (4Gl, ISQL, ESQL etc.)
> > from version 6.0 to 7.2 (Yes it is for Y2K compliance).
>
> If going from 6.05 to 7.2, it should be straight-forward. If going from
> 6.00 to 7.2, then there may be some problems, though it should still be
> relatively simple.
>
> > My current engine is Online 7.30 and I am wondering if anybody knows
> > of any problems that I might encounter?
>
>
Sorry for replying to a reply, but our server no longer has the original
message.
We just upgraded from 7.23 to 7.30 UC3-1, and I ran into a definite problem
with the following syntax:
DELETE FROM tab1
WHERE keycol2 IN (SELECT col_a FROM temp_tab);
Before it ran fine. After the upgrade, the statement would run for 10 minutes
before failing with:
244: Could not do a physical-order read to fetch next row.
134: ISAM error: no more locks
In the release notes, I see this noted as a supposedly fixed bug:
72545 CAN RUN OUT OF LOCKS (-244/-134) WHEN EXECUTING A DELETE OR UPDATE
STATEMENT THAT DOESN'T USE AN INDEX FOR SEARCHING.
So I changed the SQL so that it used an index containing keycol1 and keycol2:
DELETE FROM tab1
WHERE 1 IN (
SELECT 1 FROM temp_tab t
WHERE t.col_a = tab1.keycol1
AND t.col_b = tab1.keycol2
);
And now it works fine. I will be submitting this to Informix as a problem.
--
Matt Reprogle
IS Engineer, Delphi Delco Electronics Systems
phone:(765)451-9651 FAX: (765)451-8230 mcreprog@ictest.delcoelect.com