Hi Folks

I'm having all sorts of issues with Health Centre (DB2 AD Client V8.2 on Win 2K SP4 monitoring UDB WSE V8.2 on Solaris 2.8), for instance:

- when using DB2 HC to reconfigure global health indicator settings on instance1/box1, I get sometimes get a msg stating 'Admin Server not found' when trying to add/change an OS script. If I connect DB2 HC to instance2/box2 I have no problems, and on reconnecting to instance1/box1 I then have no problems there either. I've recreated the das on box1, but it made no difference.

- when using DB2 HC to monitor for all possible states of tablespace indicator ts.ts_op_status on all tablespaces in all databases in an instance, I saw db2fmp start using all available CPU on the Solaris box, ie db2fmp running at 97% CPU. I've also seen it do this when running db2 update alert cfg from the Solaris command line to set global defaults for all Health Mon indicators. However, I can't reproduce this at will. This a really alarming one!

I have PMRs open with the IBM Support Centre, but no progress so far. Has anyone else experienced these problems when using DB2 Health Centre/Health Monitor? Anybody got any other funnies we should be aware of? Any suggestions on what may be the cause of these problems or how to circumvent them?

Grateful for your advice or views.

Regards,
Jerry




NOTICE
This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank.


DB2 & UDB email list listserv db2-l LazyDBA home page