How unlock the locked table?

[Liu Jiachuan]

Hello, everybody.
I have a problem: I locked a table via dbaccess, but forgot unlock
it, and exit dbaccess. Sometimes later my programs report error that
the table is locked by some process. I run dbaccess and try to unlock
the table , but it report that I am not the user which lock it. I
have no way to solve this problem. Fortunately after startup informix
again the table is unlocked. But I don't know how I unlock it if I
don't re-startup informix system. Can you give me some advice or
solution?
There is another problem. My friend have met a problem. Just when he
backup the database, power is stopped and the backup procedure is
not finished. When power comes again, all operation on the database
is not allowed. And the error is that the transaction isn't finished.
How can he end the transaction?

Thanks a lot.

[Sean Kelsey]

Unfortunately, you havn't given us a lot to go on...

What engine are you using ? Release/Version ? operating system ?

I will make some assumptions that you are using Informix ODS 7.2x

You can check if that particular sessions is still running using
'onstat -u'. If it is, try killing it off using 'onmode -z <sessid>'.
Alternatively, track down the particular lock using onstat -k then use
onmode -Z <address> to kill it off.

Hope this helps.

Sean

Liu Jiachuan wrote in message <771e4i$55s$1...@news.xmission.com>...

[June Tong]

Liu Jiachuan wrote:

> I have a problem: I locked a table via dbaccess, but forgot unlock
> it, and exit dbaccess. Sometimes later my programs report error that
> the table is locked by some process. I run dbaccess and try to unlock
> the table , but it report that I am not the user which lock it.

If you exited dbaccess normally, it should automatically release the
lock; you do not have to "remember" to unlock it. If it did not release
the lock, then either your dbaccess or your OnLine session is a zombie.
If it's your dbaccess, use kill (assuming you're on Unix) to kill
dbaccess, and hopefully your session will terminate itself and release
the lock. If it's your session, you can use onstat to identify your
session and try to kill it using onmode -z. Are you sure no one else had
the table locked? Use onstat -k to identify who is locking the table.

> There is another problem. My friend have met a problem. Just when he
> backup the database, power is stopped and the backup procedure is
> not finished. When power comes again, all operation on the database
> is not allowed. And the error is that the transaction isn't finished.
> How can he end the transaction?

I don't recognize this error that "the transaction isn't finished". Can
you provide more information? What was the status reported by onstat -,
and what errors were in the online.log?

June
--
jun...@hotmail.com
Grounded in Palo Alto, living on M&M's (plain)