Hi, Please can anyone advise how to tackle the issue of the agent cache file growing big.. sometimes upto 3 GB? Particularly I've seen this file grow on one server which hosts SQL 2005, is a cluster node and also hosts IIS. Regards, Adhokd

Yup This used to happen before CU1 Do you have the right CU in your environment? At least CU2, but CU3 is out there too http://blogs.technet.com/b/kevinholman/archive/2010/04/30/opsmgr-2007-r2-cu2-rollup-hotfix-ships-and-my-experience-installing-it.aspxPaul Keely

Hi, Thanks for reply. Why does the cache file grows so big though? Is there any other way to overcome this as there are only 2 to 3 servers on which I've seen this. Regards, Adhokd

Well do you have the right CU installe on them? It was a known issue that was fixed in CU1Paul Keely

Hi, there is also another issue which happens on all kind of Windows Servers with the storage engine of the jet database: http://support.microsoft.com/default.aspx?scid=kb;en-us;981263. Could be that it is a mix of both: a SCOM Agent issue AND the jet database issue. Best regards, Marnix Wolf (Thoughts on OpsMgr)

yeah CU 1 is applied already Adhok

This particular agent shows healthy in SCOM console. Adhok

Does Marnix's KB apply to you? If not its quite strange. If it doesnt I would look to flush the health service cache and if that does not work Id go for a reinstall. As a rule of thumb the EDB should not be more then about 150 mbPaul Keely

Even though SP1 is applied and the Agent is still available, the issues with the DB remains. The hotfix really addresses that issue. I have seen it before where the DB really got oversized. After the hotfix for the Jet DB engine all was well again.Best regards, Marnix Wolf (Thoughts on OpsMgr)

I've not applied the hotfix now.. I'll check whether I can do it as I don't own the server.. I'll get back to you on this Adhok

Thanks for your help guys.. I think the problem has resolved. Its been 24 hrs and the .edb hasn't gone above 150 mb. I didn't apply the hotfix as I wasn't allowed to do so.. I reinstalled the agent and that helped. I'll check for any other dev box if it gives the same problem and will try the hotfix on that. Adhok