record locked
On the order table (IDS 9.40) I had a record locked for quite a while.
I could not even read it. (Could not fetch row error appeared from
dbaccess).
I could work fine with all of the other records on that table, insert,
delete, update without any problem.
I think there was a little routine (we got tens of them made by
someone else and I do not know about all of them yet) keeping this
record locked.
How can I identify what process keeps a record locked and how to get rid of it?
Thank you
Gentian
The following shows the total number of locks by object and process:
http://groups.google.com/group/comp.databases.informix/browse_frm/thread/1b38ad8daedd3d4a/7ada92ad4898b19c?lnk=gst&q=syslocks+lawry&rnum=2#7ada92ad4898b19c
Either kill the process or stop the thread using "onstat -u" and "onmode -z
sid". This is obviously easier if you install a GUI such as ISA or Server
Studio.
--
Regards,
Doug Lawry
www.douglawry.webhop.org
"Gentian Hila" <genti.tech@gmail.com> wrote in message
news:mailman.282.1155738706.20706.informix-list@iiug.org...
> On the order table (IDS 9.40) I had a record locked for quite a while.
> I could not even read it. (Could not fetch row error appeared from
> dbaccess).
>
> I could work fine with all of the other records on that table, insert,
> delete, update without any problem.
>
> I think there was a little routine (we got tens of them made by
> someone else and I do not know about all of them yet) keeping this
> record locked.
>
> How can I identify what process keeps a record locked and how to get rid of
> it?
>
> Thank you
>
> Gentian
ISA is a good idea, but I am already using appache on the dbserver for
the application, and ISA needs to be installed only on that server. I
can try to use some other web server of course with a different port
rather then 80 or 443
On 8/16/06, Doug Lawry <lawry@nildram.co.uk> wrote:
> The following shows the total number of locks by object and process:
>
> http://groups.google.com/group/comp.databases.informix/browse_frm/thread/1b38ad8daedd3d4a/7ada92ad4898b19c?lnk=gst&q=syslocks+lawry&rnum=2#7ada92ad4898b19c
>
> Either kill the process or stop the thread using "onstat -u" and "onmode -z
> sid". This is obviously easier if you install a GUI such as ISA or Server
> Studio.
>
> --
> Regards,
> Doug Lawry
> www.douglawry.webhop.org
>
>
> "Gentian Hila" <genti.tech@gmail.com> wrote in message
> news:mailman.282.1155738706.20706.informix-list@iiug.org...
> > On the order table (IDS 9.40) I had a record locked for quite a while.
> > I could not even read it. (Could not fetch row error appeared from
> > dbaccess).
> >
> > I could work fine with all of the other records on that table, insert,
> > delete, update without any problem.
> >
> > I think there was a little routine (we got tens of them made by
> > someone else and I do not know about all of them yet) keeping this
> > record locked.
> >
> > How can I identify what process keeps a record locked and how to get rid of
> > it?
> >
> > Thank you
> >
> > Gentian
>
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list
>
Gentian Hila wrote: > ISA is a good idea, but I am already using appache on the dbserver for > the application, and ISA needs to be installed only on that server. I > can try to use some other web server of course with a different port > rather then 80 or 443 > If you do a standard ISA installation, you'll get an apache setup in an ISA subdirectory. The install process will ask for a port number for accessing ISA. The ISA apache doesn't conflict with any previous apache setup (unless you choose port 80). The installation documentation also has good description on how to setup ISA manually using an existing apache server. Claus