Re: Oracle database status web page

nilanjan wrote:

> 1. Doesnt this involve running some Oracle Intelligent agent or such
> on the remote databases ? I think I saw messages like that when I was
> playing with OEM with a Management repository on my local machine.
> Trying to solve this issue. It could not discover other nodes as
> Intelligent Agent was not running on those other database instances

> (which I do not control)

Yes, OEM uses the Oracle Agent. This is actually a small piece of code, supplied by Oracle, that gathers a variety of stats about all the Oracle products running on the system. (A lot of people go out of their way to do a subset of the things the agent does, generally burning more CPU cycles than the agent.)

Although I agreee that there are issues with agent & OEM, each version I've seen since OEM 1.2 has been noticably better. I think it's acceptable now, especially is you use the 9.2 OEM & repository (which can monitor down the versions).

Alternately, SNMP? (but also check out recent security advisories.)

>
> 2. Also this would involve the Web Portal running OEM ( where I do not
> have control either) I can only give them the web page or program to
> implement.
>

OEM provides a self contained web portal.

>
> 3. Again this involves creating another Repository database , so that
> adds another failure point and dependency. What if the repository
> itself was down or the Oracle Apache machine was down ??
>

And the list goes on. However, if Oracle DBAs use the OEM (after all it was designed as a DBA tool), then the likelyhood of it being down undetected for long is relatively small. If it's that critical, the Oracle environment be made more robust - repository is a database so use RAC, etc. A lot depends on whose neck should be on the line when a problem occurs; yours or Oracle's?

As I said, I think OEM satisifes the requirements. Your reasons are certainly legitimate, although in certain organizations they might not be very strong.

/Hans Received on Wed Apr 02 2003 - 22:26:37 CST