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.
Richard Thomas — — source: Informix-list mailing list archive (1991-1998)
Stanley,
I get this problem if the server has crashed while someone was using
perform (add or update) - the row they were in stays locked even though
the isql process has terminated. Check that this is the case (ie that=20
no one really is using that row [:-)], and try the following:
In unix, cd to the xxx.dbs directory (where xxx is the name of the=20
database) and type 'clearlok' at the prompt. This should solve it.
Cheers,
Richard.
----------------------------------------------------------------- =20
| _ =AF\\ | Richard Thomas |
| \\ 0_ | r.thomas@csl.gov.uk |
| \\ / | |
| oo/ | "20 Regal and a four-pack, |
| / \\ | I guess I'm set for the night" |
| \\_/ | - "TV Tan" The Wildhearts |
-----------------------------------------------------------------
>=20
> I am working in Informix V4 SE. The error occurs within a=20
> PowerBuilder application. My problem is that I can't delete a row=20
> from a table. The error I get is -263 with ISAM -107. Could not=20
> lock row for UPDATE. I am not sure how to resolve this problem.
>=20
> When in ISQL on UNIX I get a message that the row is currently in=20
> use by another user.
>=20
> Any advice is appreciated
>=20
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.