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?

Where are your databases defined? If the database is defined in the root dbs and the tables are defined elsewhere, then you might be hitting the systables quit a bit. What does onstat -g dic look like? There is a max length of each of the dictionary chains. If all of the hash chains are full, then you might be opening quite a few of the systables constantly to get the dictionary information into the cache. Are you using HDR??? "B. Dana" wrote: > 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?