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.
On 7/17/06, Prateek Jain <prateekvjain@gmail.com> wrote:
> One table has got locked and the error number itis giving
> is 244 and 107(ISAM error)
> Before that delete query was fired on the above table but it was not
> executed and was in running mode and the session got closed.
>
> Now how to get rid of these error msg
>
> Table is locked
Which server? Which version? Which platform?
So, a DELETE was prepared but not executed, and the session terminated? And
then you ran into the locking error - in another session? What else was
happening at the same time?
Workarounds? Reboot IDS often works. Take server into admin mode (single
user mode - 10.00 only) and back into multi-user mode; take it into
quiescent mode and back into mulit-user mode. If those don't fix it, do
some serious work with oncheck to ensure that the disk storage is clean.
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/
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.