I've had problems trying to use OEM (9.0.1) to monitor clustered databases. The problem is that each database is set up in it's own resource group, therefore each has it's own virtual hostname. Even though I may have several databases all running on the same physical host, they all have different virtual hostnames that move with the database when it fails over to another node in the cluster. When you discover a node, it picks up all of the databases on the node and registers them with the OMS as being on that node. Once one of them fails over it's no longer on that node and can't be monitored from OEM anymore. I'm sure others on this list are using this type of failover for high availability. How did you get around it?
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Chuck Hamilton INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
