Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: OEM Implementation Plan

RE: OEM Implementation Plan

From: Mercadante, Thomas F <>
Date: Mon, 18 Oct 2004 10:08:34 -0400
Message-ID: <C9995D8C5E0DDA4A8FF9D68EE666CE07A7F9A0@exchsen0a1ma>


We are using OEM and home-grown scripts to monitor our database. Since the home-grown scripts are working, we have not felt the need to convert them to OEM scripts. We use OEM to monitor database up/down and alert log messaging. We also use it on a limited basis to check for things like archive log disk getting full, and running an archivelog backup to clear that condition.

You need the Oracle agent running on the servers for it to work properly. It works ok. We have had times when the console just simply loses contact with the agent. Rediscovering the node sometimes fixes the problem. But other times, we had to delete the node and redicsover. And when this happens, all of the events need to be recreated. Kind of a pain, but it can be fixed.

Good Luck.

Tom Mercadante
Oracle Certified Professional

-----Original Message-----

From: Kline.Michael [] Sent: Monday, October 18, 2004 8:07 AM
Subject: FW: OEM Implementation Plan

We're getting ready to think about OEM due to tight funds. We could really use something for DB2, Sql Server and Oracle, but that doesn't look to promising right now. So, we're hoping OEM may do for most of the "major" things. Perhaps some of you have already got into that and have the "This works" and the "This will work when pigs fly" type scenarios that you've already worked through.

I was the ideas man for "Empirical Director" but that's gone now. For now I've been using summary reports that are generated 1-2 times a day and they track tablespace growth, no room for next extent, I/O activity, tablespaces < 30%, scan the alert log, and several other things. They get emailed. It's manual, but the "manual" makes sure it gets done. Outlook dumps them into a specific folder so "other" things are not overwhelmed by the logs.

If you have some pointers, thank you very much.

Michael Kline
Database Administration
Outside 804.261.9446
Cell 804.744.1545

-----Original Message-----

 Subject: OEM Implementation Plan

HI Gang,
This is the first communication on our OEM plan. The objective of this plan is to design, configure and deploy OEM to automate, diagnose and manage some of our production support responsibilities. The implementation design and configuration phases will be planned by reviewing the responses to several research questions. I would like each of you who wish to contribute to send me your views on the questions. I will compile a consensus opinion and redistribute. Please judge the appropriateness and completeness of the questions. If you feel an additional question is necessary to fully understand an issue, please propose. Thank you in advance for your help.

Design Questions:

What functions should OEM be expected to perform?

Should OEM repositories be distributed (by subject areas) or centralized (one repository)?

RLA Randall L. Anderson
Team Lead, Oracle

The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer.

-- Received on Mon Oct 18 2004 - 09:04:14 CDT

Original text of this message