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.
Bernstein, Rick — — source: Informix-list mailing list archive (1991-1998)
Have you moved your logical logs and physical log into different
dbspaces? If not, that will explain high I/O activity in rootdbs.
-----Original Message-----
From: B. Dana [mailto:bgdana@hotmail.com]
Sent: Tuesday, August 29, 2000 16:13
To: informix-list@iiug.org
Subject: Why is rootdbs busy?
According to onstat -g iof, rootdbs appears to be the busiest chunk in
the system with 10
times more dskwrite than any other chunk. The performance guide states
that "When
you do not specify dbspaces in the DBSPACETEMP parameter or the client
DBSPACETEMP environment variable, Dynamic Server places all temporary
tables
in the root dbspace." There are four temp dbspaces and they are defined
in the onconfig
file. I have seen activity on all of those spaces with onstat -g iof
and using the OS monitor
command while creating indexes. If the client sets DBSPACETEMP to a
nonexistent
dbspace or does not set it, will sorts and temporary tables default to
rootdbs?
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.