may be the transaction is not completed, is it a distributed transaction ? if it is, then, one of the option is,
- make sure there are no distributed transactions running on the database
- issue onstat -x and identify the transaction (the fifth character in the flag will be a 'G'),
- issue onmode -H or onmode -Z on the transaction id (this may kill the open transaction and release the lock)
-----Original Message-----
From: owner-informix-list@iiug.org
[mailto:owner-informix-list@iiug.org]On Behalf Of tomcaml@yahoo.com
Sent: Tuesday, March 22, 2005 8:57 AM
To: informix-list@iiug.org
Subject: orphaned lock process
hello all,
i have the situation where a lock is left on a table but there is no
session id associated with it. is there a way to kill this orphaned
lock?
thanks!
sending to informix-list