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.
Doug Johnson — — source: Informix-list mailing list archive (1991-1998)
First of all, thanks to the newsgroup responders but so far no
breakthroughs here or from Informix. I'll post the fix when found.
Some new info:
I created a smaller table (6 million rows) and have been watching active
tblspaces with "onstat -tr 10" during various unique and non-unique
"create index" commands.
At the beginning, things look normal with 14 to 24 active tblspaces (out
of the 2000 specified).
Then "something happens" and "active" explodes to > 300 with npages=32
and nused=npdata=nrows=0 and nextns=1; (See onstat -t for brief
descriptions). Informix then calms down and (I'm guessing) consolidates
these unused tblspaces because the number of active migrates back down to
20-30 and npages slowly grows from 32 to 64 to 128 to 256 to 512 to 1024
to 2048 to 4096 to 8192. nused, npdata and nrows stay at 0. nextns ranges
from 1 to 10.
Any insights as to why Informix "flash creates" hundreds of entries
pointing to unused 32 page tblspaces? If Informix really needs all of
these tblspace pages, any way to inform it to allocate fewer but larger
tblspaces? Thanks.
Doug Johnson
EMC
johnson_doug@emc.com
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.