Error 211

Hello, When I start with DBACCESS two SQL queries using the same stored procedure, the first query I start is brutally stopped when I start the second query. I obtain the following Error message : Error -211, Cannot read system catalog (sysprocauth). Has someone an idea of what's going wrong ? Thanks in advance for your help. Gilles Bollecker. Liebherr France.

Liebherr France wrote: > When I start with DBACCESS two SQL queries using the same stored procedure, > the first query I start is brutally stopped when I start the second query. I > obtain the following Error message : > Error -211, Cannot read system catalog (sysprocauth). > Has someone an idea of what's going wrong ? What does your stored procedure do? I think that if it does anything which causes the procedure plan to be altered, it has to lock the procedure, which would cause another user to receive an error message. In this case, it looks a bit like maybe your procedure grants permissions to itself, or possibly another procedure, hence the error on sysprocauth (not one I've seen before, but theoretically possible, I suppose). June -- june_t@hotmail.com Grounded in Palo Alto, living on M&M's (plain)

Here is the source code of my stored procedure --------- create procedure sp_baa_date12(in_field char(10)) returning char(6); define t_date_12 = in_field[1,4] || in_field[6,7]; return t_date_12; end procedure ------ The 2 queries using a the same time this procedure look like : SELECT sp_baa_date12(column1) FROM table1 I have just read an article telling that : "If the stored procedure does not contain any DML statements, it will be reoptimized every time it is executed". My opinion : The query plan seems to be updated each time the stored procedure is called meaning temporary locking of stored procedures system tables. What do you think about this ? If this is the explanation of the problem, can I avoid automatic re-optimization of my stored procedure ? Hope that you can help me. Gilles Bollecker. June Tong a 'crit dans le message <79dq34$st1$3@news-2.news.gte.net>... >Liebherr France wrote: > >> When I start with DBACCESS two SQL queries using the same stored procedure, >> the first query I start is brutally stopped when I start the second query. I >> obtain the following Error message : >> Error -211, Cannot read system catalog (sysprocauth). >> Has someone an idea of what's going wrong ? > >What does your stored procedure do? I think that if it does anything which >causes the procedure plan to be altered, it has to lock the procedure, which >would cause another user to receive an error message. In this case, it looks a >bit like maybe your procedure grants permissions to itself, or possibly another >procedure, hence the error on sysprocauth (not one I've seen before, but >theoretically possible, I suppose). > >June >-- >june_t@hotmail.com >Grounded in Palo Alto, living on M&M's (plain) > >