RE: OEM 9i delete database Catch-22
Date: Sat, 12 Dec 2009 10:14:23 -0500
Good one, Tom. I was about to suggest a fresh install of OEM as least amount of work to accomplish the goal. But I think dropping and possibly adding a node back beats that.
I still might consider a fresh install of OEM if all the dbs still in service could talk to the latest, greatest release. But that depends on who is paying for the effort and whether they want the cleanest forward looking environment or the least cost to clean up right now.
Did that solve it for you, Dan?
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Mercadante, Thomas F (LABOR) Sent: Friday, December 11, 2009 11:43 AM To: daniel.fink_at_optimaldba.com; oracle-l_at_freelists.org Subject: RE: OEM 9i delete database Catch-22
If you drop the node, everything goes away with prejudice.
You can always rediscover the node if you still have databases that you want to monitor. If you have events on those databases, you will have to recreate the events.
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Daniel W. Fink
Sent: Friday, December 11, 2009 11:25 AM To: oracle-l_at_freelists.org
Subject: OEM 9i delete database Catch-22
I've inherited an older OEM install with some nodes/databases that are invalid. When I try to drop the database, it complains about events that are registered. So I deregister the event...and it shows as pending. It is my understanding that it will remain in this state until it communicated with the agent on the node...but the node does not exist.
I'm RTFMing, but not finding the answer to manually removing or reconfiguring a database.
It's been many years since I dealt with OEM 9i and events, though I have a vague recollection that it was less than intuitive how to fix problems.
http://www.freelists.org/webpage/oracle-l Received on Sat Dec 12 2009 - 09:14:23 CST