On Wed, 21 May 2003 16:01:40 -0800, "David E. Grove"
<david_grove@correct.state.ak.us>
>We run a 24x7 operation, managing the state's prison system.
>
>To avoid users getting -211 (sysprocplan) errors, I created a cron job that
>runs 'update statistics high', immediately followed by 'update statistics
>for procedure' every night. But, users still get occasional -211
>(sysprocplan) errors. These occasional errors usually occur while the
>"update statistics" jobs are actually running. The 'update statistics high'
>takes about an hour, and the 'update statistics for procedure' takes about 7
>minutes. Since running "update statistics" is the fix, and the errors
>happen during the fix, what might I do to? I'd like to eliminate -211
>errors. Does anyone have any suggestions?
>
>We have about 1000 tables and 1000 stored procedures in our database.
I've been seeing similar problems, although the version of software
we're using has plenty of programs which UPDATE STATS on tables they may
modify heavily.
But, I've seen other installations of the same version which didn't
suffer so much from this problem. I also don't think there are enough
UPDATE STATS in these programs to account for all the -211 errors we're
getting.
What else could cause this?
The ISAM error is -107 if that helps.