Re: Oracle 10G: Grid Control Install Problems. 64 Bit Windows

From: Hans Forbrich <forbrich_at_yahoo.net>
Date: Sun, 11 Jul 2004 16:37:05 GMT
Message-ID: <R0eIc.24619$Rf.22445@edtnps84>

Louis Frolio wrote:

>
>
> Daniel, you are right in that Oracle has done a terrible job
> explaining all of this. I still don't know if I can use one server
> running 10g and oem to manage several nodes running several instances
> of Oracle? The only thing I have been able to do so far is get OEM
> to manage the node on which it lives, I cannot seem to find the
> ability to add targets etc? This is all on Windows. I opened an
> iTar, hopefully but doubtfully an analyist at Oracle support will be
> able to make heads or tails of this for me.

(I am not an Oracle employee - the following is my interpretation.) Based on my observations, let me try the following explanation:

What is OEM
Oracle Enterprise Manager is a framework for creating and using management applications. WHen you start OEM, you implicitly start the framework and the entire set of "applets" you can access in that context.

This is true as of OEM 1.0, and follows with each major release.

The OEM releases were introduced at the following time frames:

OEM 1.x matches roughly to Oracle database 8.0 appears to have been written in C
OEM 2.x to database 8.1.x (Oracle8i Release x)
OEM 9i == OEM 3 matches database Oracle9i appears to have been rewritten in Java
OEM 4 matches Oracle10g database AND App Server 9iR2 appears heavily JSP/Servlet oriented B) What is OEM repository
When managing a database, Oracle uses a repository to handle the schema to pr4sent OEM-specific information and possibly collect data for further analysis. OEM can run in one of two modes :
1. that repository is inside the database/instance being managed, or
2. that repository is in a central location.

The repository always exists!

C) What are the intelligent agents

If mode 2, you have the ability to handle a large number of databases and instances in a single central location. The challenge is keeping the central repository in sync, which is handled by remote 'intelligent agents' designed to collect appropriate data from the 'target' database and store it in the central repository.

With OEM 1-3, only one agent exists per host and that agent has the ability to collect basic data and interact with all supported database versions.

D) What is the OMS

With a central repository, some objectives include concurrent DBA access, concurrent data collection, and possibly scheduling specific monitoring and managing responses such as alerting administrators who are not connected.

The Oracle Management Server is a background process with the following major functions:

coordinate administration requests for immediate data access either through the repository or through the appropriate intelligent agents
manage job scheduling (event)
monitor response to invoke a corresponding activity (job)
interface to the appropriate alerting technology (page, mail, etc.)
What is the OEM 4 / OEM 10g "instance control"

OEM 10g control is logically equivalent to the older OEM 'stand-alone' (non-OMS) console. It is the single point of access to control a specific database/app-server/collab-suite/etc. 'instance'.

The control is an OC4J-based set of JSP/servlet user interfaces (apparently to EJBs) that have the responsibility of user interface and handling administration requests (similar to the IA).

For each application serer instance you get an "app server control". Apparently for each database instance, you get a "database control". So there is a one-to-one relationship between a control and a controlled instance.

The control is accessed by browser at http://{host}:{port} - for app erver, the first app servver's control is generally at port 1810.

F) What is the OEM 4/10g Grid Control

For OEM 10g, Oracle has rewritten the OMS to be an OC4J application. The 10g Grid Control Console is a new front end for the OMS. It's purpose is to consolidate the information from a number of regular "instance controls", using Management Agents, and then allow access to the appropriate "instance controls".

OEM Grid Control therefore is the replacement to the old centralized OMS. There are a lot of differences, and I suspect that Grid Control may also simply redirect to the "instance control" for some operations.

G) Some of my thought processes.

OEM 10g Grid control is

accessed from a browser
runs in OC4J
can reside on any supported (Linux/unix) host
consoldates the info from a number of 'instance' controls
stores it's info in a 9.2.0.4 or higher DB (any supported OS)
needs Management Agents as operational proxy's

Since I happen to believe in centralized management, I would look at Grid Control for any Oracle shop with > 2 instances. The grid control management server and console would be on a Linux box. I believe in a central "administrator's" database to hold all the various repositories (OEM repository, app server infrastructure, various tools such as Discoverer EUL, Worflow, etc.), and that could be on any convenient relatively low-cost box - even Windows.

Hope this helps a bit.
/Hans Received on Sun Jul 11 2004 - 11:37:05 CDT