Subject | Re: SQLCODE: -913 Deadlock |
---|---|
Author | Chooi-Ting |
Post date | 2003-09-05T05:02:34Z |
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@t...>
wrote:
Previously I have deadlock error when I update a table thru my
application. After get the error, I terminated the application by
using CTRL-C, since it is a C-program application. Then, I issued
select count(*) command thru isql, and got this error -913.
Chooi Ting
wrote:
> At 01:50 AM 5/09/2003 +0000, you wrote:from
> >hi,
> >
> >I am having the above error code while I issueing a select query
> >isql:avoid
> >select count(*) from table1;
> >
> >it returns:
> >Statement Failed, SQLCODE= -913
> >deadlock
> >
> >
> >What should I do to clear the deadlock? and what should I do to
> >this error happen again?SNAPSHOT or
>
> This is weird. It shouldn't happen at all in isolation levels
> READ COMMITTED. isql runs DML in SNAPSHOT by default. Writers inthese
> isolation levels don't block readers, so you should never get alock
> conflict just counting rows.you are using?
>
> Can you provide some information about what database and version
> What else was going on the database 1) inside your isql session 2)outside it?
>I am runing firebird 1.0 in Sun Sparc (S0-V1.0.0.796 Firebird 1.0).
> heLen
Previously I have deadlock error when I update a table thru my
application. After get the error, I terminated the application by
using CTRL-C, since it is a C-program application. Then, I issued
select count(*) command thru isql, and got this error -913.
Chooi Ting