-113 ISAM error: file is locked
Jennifer
dbaccess and mistakenly hit Ctrl-Z instead of Ctrl-X. It canceled me
out of dbaccess, now the table is locked. I cannot select anything
from it, without getting the 113 file is locked error. The error
reference mentions a .lok file, but I have searched and no file was
found. I tried unlocking the table and dropping the table and
database without any luck. I have exhusted my references. Any ideas?
Thank you in advance.
Jennifer Duby
Michael Krzepkowski
HTH
Michael
Dirk Moolman
Use "onstat -u | grep your_login" to get the thread you aborted, then
use "onmode -z sid" to kill this session.
If you want, you can run the following between these 2 steps to see what
the session id is doing that you are looking at:
onstat -g sql sid
OR
onstat -g ses sid
Just note that, if the thread is in a critical stage (X flag in onstat -u),
you can bring down the database engine by killing the thread.
How big is the table, is it small ? If you can, leave it for a while
to see if it completes on its own, otherwise you will have to kill it.
** Can the gurus please comment on what happens to the table that was being
when the session aborted / or a session is killed. The process must
either
continue running in the background or rollback like a normal transaction,
right ?
-----Original Message-----
From: owner-inf...@iiug.org
[mailto:owner-inf...@iiug.org]On Behalf Of Jennifer
Sent: Thursday, October 25, 2001 5:13 PM
To: inform...@iiug.org
Subject: -113 ISAM error: file is locked
I need your help. I am using SE 7.2. I was altering a table in
dbaccess and mistakenly hit Ctrl-Z instead of Ctrl-X. It canceled me
out of dbaccess, now the table is locked. I cannot select anything
from it, without getting the 113 file is locked error. The error
reference mentions a .lok file, but I have searched and no file was
found. I tried unlocking the table and dropping the table and
database without any luck. I have exhusted my references. Any ideas?
Thank you in advance.
Jennifer Duby
==========================================================
This message contains information intended for the perusal, and/or use (if
so stated), by the stated addressee(s) only. The information is
confidential and privileged. If you are not an intended recipient, do not
peruse, use, disseminate, distribute, copy or in any manner rely upon the
information contained in this message (directly or indirectly). The sender
and/or the entity represented by the sender shall not be held accountable
in the event that this prohibition is disregarded. If you receive this
message in error, notify the sender immediately by e-mail, fax or telephone
representations contained in this message, whether express or implied, are
those of the sender only, unless that sender expressly states them to be
the views or representations of an entity or person, who shall be named by
the sender and who the sender shall state to represent. No liability shall
otherwise attach to any other entity or person.
==========================================================
Sergey E. Volkov
Jennifer,
Pressing C-z you put your dbaccess to the background.
Just type "fg" from the same terminal ( from a shell prompt ),
or find and kill it.
Paul Watson
session type 'fg'. If not find it on the ps listing and kill it if
it's still there.
--
Paul Watson #
Oninit Ltd # Growing old is mandatory
Tel: +44 1436 672201 # Growing up is optional
Fax: +44 1436 678693 #
www.oninit.com #
Dirk Moolman
Sorry, wasn't concentrating - didn't look at the SE 7.2
Maybe I should change my motto to "so much beer, so little time"
-----Original Message-----
From: Jenn [mailto:jdub...@yahoo.com]
Sent: Thursday, October 25, 2001 8:52 PM
To: Dirk Moolman
Subject: RE: -113 ISAM error: file is locked
Thank you for your reply, but unfortunately onstat and
onmode are not recognized. I am using Solaris 8. Any
other ideas?
Jennifer Duby
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com