I use 7.3 for NT 4.0. My clients frecuently receive this message :
SQL error -211 !Cannot read system catalog
(sysprocplan) ISAM error:154Isam error: Lock timeout Expired
This is generated by programs (PowerB + SPL) that have left a
transaction opened (a Begin), then I have to kill these processes to
resolve the problem. I want to know why "sysprocplan" is locked,
why a client that is processing a transaction locked so much this
table, how could I avoid it.
Thanks in Advanced.
↪ replying to Duran Grande, Jorge
Sysprocplan is one of the system tables that holds info about your
stored procedures. If this stored procedure is new, or has been changed
or tables that it references have been changed then sysprocplan will try
to regenerate itself on the fly, which can lead to locks. The way to
avoid this is to do update statistics for the whole database after you
change the stored procedure or it's tables,
-----Original Message-----
From: Duran Grande, Jorge [mailto:jduran@bcrp.gob.pe]
Posted At: 06 June 2000 18:37
Posted To: informix
Conversation: Sysprocplan locked
Subject: Sysprocplan locked
I use 7.3 for NT 4.0. My clients frecuently receive this message :
SQL error -211 !Cannot read system catalog
(sysprocplan) ISAM error:154Isam error: Lock timeout Expired
This is generated by programs (PowerB + SPL) that have left a
transaction opened (a Begin), then I have to kill these processes to
resolve the problem. I want to know why "sysprocplan" is locked,
why a client that is processing a transaction locked so much this
table, how could I avoid it.
Thanks in Advanced.