Art S. Kagel wrote:
> Correct, it means that one or more of the system catalog tables has been
> modified, through proper channels like an ALTER, UPDATE STATISTICS,
> or CREATE/DROP INDEX statement, and the cached values are no monger
> valid. The new values are not automatically loaded in case the table
> is no longer being actively accessed, but will be reloaded as needed.
>
Can this cause the 710 error (table has been altered, dropped or renamed...)?
> BTW the other thing to look for in the onstat -g dic report is the
> "Total number of dictionary entries:" at the bottom versus the product
> of the "Number of lists:" and "Maximum list size" at the top. If these
> are close you may need to increase the size of the data dictionary
> cache to prevent the cache from thrashing.
How?
Thanks.