Dear Winger, EDM Pool sizing issues show up as excessive I/O due to paging. High CPU usage does not necessarily mean that you have a space problem, it may simply mean that alot is going on. The EDM pool is used for caching internal structures used by DB2 programs. This includes DBDs, SKCTs, CTs, SKPTs, and PTs. It also includes the authorization cache for plans and packages, as well as the cache for dynamic SQL mini-plans. As a general rule, you should shoot for an 80 percent hit rate with the EDM pool; this means that only one out every five times should a structure need to be loaded from disk into the EDM pool. What other tools do you use to monitor DB2 Resources?

Dear Winger, EDM Pool sizing issues show up as excessive I/O due to paging. High CPU usage does not necessarily mean that you have a space problem, it may simply mean that alot is going on. The EDM pool is used for caching internal structures used by DB2 programs. This includes DBDs, SKCTs, CTs, SKPTs, and PTs. It also includes the authorization cache for plans and packages, as well as the cache for dynamic SQL mini-plans. As a general rule, you should shoot for an 80 percent hit rate with the EDM pool; this means that only one out every five times should a structure need to be loaded from disk into the EDM pool. What other tools do you use to monitor DB2 Resources?