Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Eddie Hulme — — source: Informix-list mailing list archive (1991-1998)
In article: <2f9be823@aventure.teuto.de>
Joerg.Spilker@p0.f0.n0.z0.aventure.teuto.de (Joerg Spilker) writes:
>
> Hi,
>
> i've a program which unload tables to an ascii file and updates a specific
> column in the rows after they are written to the file.
>
> Isolation mode is set to repeatable read to avoid rows to be written to
the
> file which are not committed.
>
> Everything was fine but if there are open transactions over some rows of a
> table i got repeated errors in the range -242 to -246 (depends if the
table is
> indexed or not) until all transactions for this table are completed. Is
there a
> way to "jump" over the locked rows?
>
I am using 5.01 and am getting exactly the same problem when 2 or more users
access the same table. ie 246. It seems that Informix is still locking the
index of an adjacent row. The help message in finderr is not correct and
this is a definate bug.
I seem to remember that this bug was present in 4.10.
I also would be most interested in a workaround. Will gather together more
details of the testing we have done and post.
--
Eddie Hulme
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.