Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Got error 243 : Could not position within a table table-name

982 views
Skip to first unread message

PCGRP Yakov Berkovitch 5055

unread,
May 18, 1998, 3:00:00 AM5/18/98
to

Hi,

when several processes are trying to update the same row in the same
table, i got the error 243.

It's very strange, because this error seems related to an hardware error
(see finderr). But the table seems Ok because the oncheck utility didn't
detect a problem.
Also the program is designed like this:
- set lock mode to wait 100
- select for update
- update row,
BUT the process got the error immediately. It didn't wait 100 seconds.

My questions are:
- why the process didn't wait ?
- what can cause the error 243.

My configuration is : Informix 7.20 on AIX 4.1.5.

Thanks for any responses.
--

Regards.
________________________________________________
yakov.be...@telrad.co.il
(972)-89134414

David Williams

unread,
May 18, 1998, 3:00:00 AM5/18/98
to

In article <355FE6...@cpm.elex.co.il>, PCGRP Yakov Berkovitch 5055
<be...@cpm.elex.co.il> writes

>Hi,
>
>when several processes are trying to update the same row in the same
>table, i got the error 243.
>
What is the ISAM error code?
It may not be a locking problem...

>It's very strange, because this error seems related to an hardware error
>(see finderr). But the table seems Ok because the oncheck utility didn't
>detect a problem.
>Also the program is designed like this:
> - set lock mode to wait 100
> - select for update
> - update row,
>BUT the process got the error immediately. It didn't wait 100 seconds.
>
>My questions are:
> - why the process didn't wait ?
> - what can cause the error 243.
>
>My configuration is : Informix 7.20 on AIX 4.1.5.
>
>Thanks for any responses.

--
David Williams

Maintainer of the Informix FAQ
Primary site (Beta Version) http://www.smooth1.demon.co.uk
Official site http://www.iiug.org/techinfo/faq/faq_top.html

I see you standin', Standin' on your own, It's such a lonely place for you, For
you to be If you need a shoulder, Or if you need a friend, I'll be here
standing, Until the bitter end...
So don't chastise me Or think I, I mean you harm...
All I ever wanted Was for you To know that I care

Wolfgang Beutner

unread,
May 21, 1998, 3:00:00 AM5/21/98
to

>>>>>>>>>>>>>>>>>> Ursprüngliche Nachricht <<<<<<<<<<<<<<<<<<

Am 18.05.98, 09:43:30, schrieb PCGRP Yakov Berkovitch 5055 <be...@cpm.elex.co.il> zum Thema Got error 243 : Could not position within a table table-name:


> Hi,
> 
> when several processes are trying to update the same row in the same
> table, i got the error 243.
> 
> It's very strange, because this error seems related to an hardware error
> (see finderr). But the table seems Ok because the oncheck utility didn't
> detect a problem.
> Also the program is designed like this:
>       - set lock mode to wait 100
>       - select for update
>       - update row,
> BUT the process got the error immediately. It didn't wait 100 seconds.
> 
> My questions are:
>       - why the process didn't wait ?
>       - what can cause the error 243.
> 
> My configuration is : Informix 7.20 on AIX 4.1.5.
> 
> Thanks for any responses.
> -- 
> 
> Regards.
> ________________________________________________
> yakov.be...@telrad.co.il
> (972)-89134414

Hello Yarkov,

what about the isolation level? If there are several processes that concurrently read the row they may have placed a shared lock on the row that is to be updated.

I am not sure whether a lock timeout has to expire in that situation. Nevertheless it may as well be a problem with adjacent key locking. That should not happen anymore with version 7... but we have encounterd situations that cannot be explained i a different way.

Hope it's helpful.

Wolfgang

Wolfgang Beutner

unread,
May 21, 1998, 3:00:00 AM5/21/98
to

Wolfgang Beutner

unread,
May 21, 1998, 3:00:00 AM5/21/98
to

Scott Kolaya

unread,
May 22, 1998, 3:00:00 AM5/22/98
to
The 243 error is not so strange if you inspect the associated ISAM error also.   A 243 just says that you couldn't get to the row requested.  The ISAM error will tell you why (ex. record is locked).  Check the ISAM to see what's really going on.  Without it you can only guess why.
 
Scott Kolaya
Wolfgang Beutner wrote in message <19980521...@100024.1520>...
0 new messages