Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Art S. Kagel — — source: Informix-list mailing list archive (1991-1998)
andy lennard wrote:
>
> An aside to this. On Solaris 2.6, 7.23.UC4 we had a problem with loads
> of 'dirty' flags caused by 'update table' statements. 7.30.UC3 seems to
> have it fixed.
> The dictionary rose from the default 310 entries to 1088, and
> onstat -g mem gave dictpool as 386Mb after 30 days.
The dictionary does not grow dynamically. It is fixed size unless you
have an early version which had a bug which caused the engine to do all
manner of weird things if the dictionary table (or even a single bucket)
filled up. If you see any buckets with more entries than the "Maximum
list size:" your version has the bug. The fix is to upgrade and the
workaround is to increase the size of the table so it does not overflow.
Search the CDI archives at the IIUG WEB site for "DD_HASH" for other
posts on how to do that. Yes 7.24UC5 and 7.30 have the fix.
>
> > Can't find anything in the manuals for onstat -g dic -- except that the
> > command exists. Does anyone know what the dirty? column means?
The dirty column indicates whether that dictionary entry was loaded
from a definition of the table that is no longer valid, in effect the
table has been altered in some way to invalidate the dictionary entry
and noone has accessed the entry since so it has not been reloaded.
If the table was altered there may be a new entry in another bucket so
the old one is marked dirty so sessions know to either rehash to find a
'clean' version in cache or to reload cache with the new version.
Art S. Kagel
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.