-211 errors during update statistics

IDS version 9.40.UC2 Solaris 8 I need help here. Whenever update statistics runs, we get -211 errors in the application log. During this time the application is essentially "hung" since the sysprocplan table is locked. My only recourse is to bounce the engine, since this is a 24/7 app, and being down while update stats completes is not an option. Is there a way to get around this -211 error? BTW - I'm using the dostats program Terrence

Terrence, Firstly, the -211 error you're receiving indicates a problem with on of the tables in your system catalog. Essentially, the guilty table is unreadable. What would be very helpful at this juncture, is to know the specific ISAM error which accompanies the -211, since the effect of the error depends on the statement that is being executed and the particular table involved. Take a look at the finderr command output for a more detailed explanation. As for dostats, if 'none of the above' helps, you may want to consider re-compiling it with debugging. The may give you some additional info' not already available. BTW, are you getting any indications of errors in your log file? What about memory dump files in /tmp? Larry Beckley Database Administrator Claremont University Consortium Claremont, CA --- "Terrence Mu...." <terrence@wagerworks.com> wrote: > IDS version 9.40.UC2 > Solaris 8 > > I need help here. Whenever update statistics runs, we get -211 > errors in the > application log. During this time the application is essentially > "hung" since > the sysprocplan table is locked. My only recourse is to bounce the > engine, > since this is a 24/7 app, and being down while update stats > completes is not > an option. Is there a way to get around this -211 error? > > BTW - I'm using the dostats program > > > > > > > Terrence > > > > __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/

I had a similar problem to this back in 1995 on 7.11 IDS with a Powerbuilder frontend. What turned out to be my problem was; when the stored procedure acceses a table htat has had its statistics updated, an update statistics of the stored procdure is automaticly initiated by the stored procdure itself. In the case I was working on, the pitcular stored procedure was a data retrivial only. As it was coming from a prowerbuiled front end application that would always put the user into a transaction, the row in sysprocplan would remain locked by the first user after an update statistics until that user issued a commit work in a different part of the application. It took some work to get the applications developers to see what the problem was. I don't recall the entire "cure" it has been too many years. I believe that running update statistics on the stored procedure directly after the update statistics of the table relieved most of the pain. George -----Original Message----- From: Larry Beckley [mailto:lcbeckley@yahoo.com] Sent: Monday, December 15, 2003 2:15 PM To: ids@iiug.org Subject: Re: -211 errors during update statistics [2357] Terrence, Firstly, the -211 error you're receiving indicates a problem with on of the tables in your system catalog. Essentially, the guilty table is unreadable. What would be very helpful at this juncture, is to know the specific ISAM error which accompanies the -211, since the effect of the error depends on the statement that is being executed and the particular table involved. Take a look at the finderr command output for a more detailed explanation. As for dostats, if 'none of the above' helps, you may want to consider re-compiling it with debugging. The may give you some additional info' not already available. BTW, are you getting any indications of errors in your log file? What about memory dump files in /tmp? Larry Beckley Database Administrator Claremont University Consortium Claremont, CA --- "Terrence Mu...." <terrence@wagerworks.com> wrote: > IDS version 9.40.UC2 > Solaris 8 > > I need help here. Whenever update statistics runs, we get -211 > errors in the > application log. During this time the application is essentially > "hung" since > the sysprocplan table is locked. My only recourse is to bounce the > engine, > since this is a 24/7 app, and being down while update stats > completes is not > an option. Is there a way to get around this -211 error? > > BTW - I'm using the dostats program > > > > > > > Terrence > > > > __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/

In some version the implicit reoptimization of the query plan in sysprocplan is the problem. This can only be avoided by setting "set optimization low" before the SPL is called. Gerd Larry Beckley wrote: >Terrence, > >Firstly, the -211 error you're receiving indicates a problem with on >of the tables in your system catalog. Essentially, the guilty table >is unreadable. What would be very helpful at this juncture, is to >know the specific ISAM error which accompanies the -211, since the >effect of the error depends on the statement that is being executed >and the particular table involved. Take a look at the finderr command >output for a more detailed explanation. > >As for dostats, if 'none of the above' helps, you may want to >consider re-compiling it with debugging. The may give you some >additional info' not already available. > >BTW, are you getting any indications of errors in your log file? What >about memory dump files in /tmp? > >Larry Beckley >Database Administrator >Claremont University Consortium >Claremont, CA > >--- "Terrence Mu...." <terrence@wagerworks.com> wrote: > > >>IDS version 9.40.UC2 >>Solaris 8 >> >>I need help here. Whenever update statistics runs, we get -211 >>errors in the >>application log. During this time the application is essentially >>"hung" since >>the sysprocplan table is locked. My only recourse is to bounce the >>engine, >>since this is a 24/7 app, and being down while update stats >>completes is not >>an option. Is there a way to get around this -211 error? >> >>BTW - I'm using the dostats program >> >> >> >> >> >> >>Terrence >> >> >> >> >> >> > > >__________________________________ >Do you Yahoo!? >New Yahoo! Photos - easier uploading and sharing. >http://photos.yahoo.com/ > > > > -- Gerd Kaluzinski Tel. :+49-(0)7541-585-5000 Manager Consulting Fax :+49-(0)7541-585-5500 BYTEC GmbH mailto:support@bytec.de Hermann-Metzger-Str.7 http://www.bytec.de 88045 Friedrichshafen