|Oracle® Enterprise Manager Concepts
10g Release 1 (10.1)
Part Number B12016-01
An Oracle Enterprise Manager administrator account can be created for daily administration work.
Optional software used to secure the communication line between the Oracle Management Service and the Oracle Management Repository. When Enterprise Manager is installed "out-of-box," the communications between the Oracle Management Service and Oracle Management Repository are not secure.
See Oracle Management Agent .
An optional network-object server invoked by the network software. The AIJSERVER receives after-image journal records from the master database and forwards them across the network to the LRS process on the standby database.
Indicator signifying a particular metric condition has been encountered. An alert is triggered when one of the following conditions is true:
A metric threshold is reached.
The availability of a monitored service changes. For example, the availability of the host changes from up to down.
A metric-specific condition occurs. For example, an alert is triggered whenever an error message is written to a database alert log file.
The percentage or amount of scheduled time that a computing system provides application service.
Software installed when you install an Oracle Management Agent. The Beacon software can be enabled to monitor the availability and performance of network components (a host computer or an IP traffic controller) from more than one location, or Web pages and Web applications from multiple network locations.
Allow Enterprise Manager administrators to suspend any data collection activity on one or more monitored targets. This allows administrators to perform scheduled maintenance on targets and excluding these special-case situations from the data analysis in order to get a more accurate, long-term picture of a target's performance.
Includes these categories of configuration information:
Database and instance properties
System Global Area parameters
Control files information
Redo logs information
Rollback segments information
Database options information
A group consisting only of database targets where multiple instances – for example, all production databases – can be collected into a group and efficiently monitored on a single screen. Database groups enable you to quickly identify databases that are down, most bottle necked or have the most severe alert status.
Configuration information stored in the Management Repository for the set of hosts and targets that comprise your enterprise.
Ability to reconfigure a computing system to utilize an alternate active component when a similar component fails.
Ability of a computing system to withstand faults and errors while continuing to provide the required services.
Can include targets of the same type (for example, all your production databases) or include targets of different types (for example, all targets comprising your business's application). A benefit of the Group target type is the Summary Metric, which is only available for this type of group.
See target home page.
Includes these categories of configuration information:
Hardware (including memory, CPU, I/O device, and network interface information) for the host.
Operating system (including installed patches) for the host.
Other installed software registered with the operating system on the host. For example, this could include information about Veritas data storage management software installed on the host.
Installed Oracle software on the host, including (but not limited to) installed products and their components, patch sets, and interim patches applied using OPatch.
A group consisting only of host targets where you can view the general overview of the state of the hosts that make up the group.
A second running computing system that is ready to pick up application processing in the event that the primary computing system fails. That is, the secondary system takes over the processing at the point where the original computing system stopped and the secondary system continues the processing.
An abbreviation for Java 2 Platform Enterprise Edition. J2EE is an environment for developing and deploying enterprise applications.
The LCS process is a database server that synchronizes the master and standby databases. The LCS process synchronizes the database by automatically sending any after-image journal records (received since the last checkpoint interval) to the LRS process on the standby database. As soon as the databases are in sync, the ALS process on the master database is converted to a log ship server (LSS) process, and the LCS process terminates.
See Oracle Management Agent .
Unit of measurement used to report the health of the system.
See fault tolerance.
Oracle Enterprise Manager is the Oracle integrated management solution for managing your computing environment.
The Enterprise Manager Web-based application for managing Oracle Application Server 10g (9.0.4). The Application Server Control is installed and available with every Application Server 10g installation.
From the Application Server Control, you can monitor and administer a single Oracle Application Server instance, a farm of Oracle Application Server instances, or Oracle Application Server Clusters.
The Application Server Control relies on various underlying technologies to discover, monitor, and administer the Oracle Application Server environment.
The Application Server Control Framework consists of the Application Server Control and its underlying technologies:
Oracle Dynamic Monitoring Service (DMS)
Oracle Process Management Notification (OPMN)
Distributed Configuration Management (DCM)
A local version of the Oracle Management Agent specifically designed to gather monitoring data for the Application Server Control.
The Enterprise Manager Web-based application for managing Oracle Database 10g Release 1 (10.1). The Database Control is installed and available with every Oracle Database 10g installation.
From the Database Control, you can monitor and administer a single Oracle Database instance or a clustered database.
The Database Control relies on various underlying technologies to discover, monitor, and administer the Oracle Database environment.
The Database Control Framework consists of the Database Control and its underlying technologies:
A local version of the Oracle Management Service designed to work with the local database or clustered database
A local Oracle Management Repository installed in the local database and designed to store management data for the Database Control
A local version of the Oracle Management Agent designed to provide monitoring data to the local Management Service
Enterprise Manager Web-based user interface for centrally managing your entire computing environment. The Grid Control is installed from a separate CD–ROM that is part of the Oracle Database 10g Release 1 (10.1) CD–ROM Pack.
From the Grid Control, you can monitor and administer your entire computing environment from one location on the network. All the services within your enterprise, including hosts, databases, listeners, application servers, HTTP Servers, and Web applications, are easily managed as one cohesive unit.
The Grid Control relies on various underlying technologies to discover, monitor, and administer your computing environment.
The Grid Control Framework consists of the Grid Control and these underlying technologies:
One or more Oracle Management Services
The Oracle Management Repository
Remove Oracle Management Agents, installed on each monitored host.
The Oracle Management Agent is responsible for monitoring all targets on the host, for communicating that information to the middle-tier Management Service, and for managing and maintaining the host and the products installed on the host.
Two tablespaces in an Oracle database that contain information about administrators, targets, and applications that are managed within Enterprise Manager.
The Management Service uploads to the Management Repository the monitoring data it received from the Management Agent. The Management Repository then organizes the data so that the data can be retrieved by the Management Service and displayed on the Grid Control.
A J2EE Web application that renders the user interface for the Grid Control, works with all Management Agents in processing monitoring and job information, and uses the Management Repository as its data store.
An installation of Oracle Enterprise Manager which provides immediate value. The required components are embedded with the installation, a default SYSMAN account is created and configured to receive e-mail notifications, targets are automatically discovered, default monitoring levels and data collections automatically enabled, and for all supported targets, e-mail notifications are set up with default rules defining the targets and conditions for which SYSMAN will receive notifications.
A right to perform management actions within Enterprise Manager such as view any target and add any target in the enterprise or a right to perform operations on a target such as maintaining and cloning the target. Types of privileges are defined by Oracle.
Duplicate or extra computing components that protect a computing system.
Ability of a computing system to operate without failing. Reliability is measured by mean-time-between-failures (MTBF).
See standby database.
Collection of predefined Enterprise Manager target or system privileges created by super administrators as a means of facilitating the granting of multiple privileges or roles to users. Roles limit target access and access to specific management features.
Measure of how well the software or hardware product is able to adapt to future business needs.
Optional software used to secure the communications between the Management Service and the Management Agent. When Enterprise Manager is installed "out-of-box," the communications between the Management Service and Management Agent are not secure. Encrypted communications between the Management Agent and Management Service over HTTPS ensures the privacy of data sent from one computer to another.
Read-only database on the standby node. The standby database, also referred to as the replicated database, is physically identical to the master database. In the event of catastrophic failures, data modification activities "fail over" to the standby database such that it becomes the new master database.
Enterprise Manager administrator account that has the ability to create, modify and delete any Enterprise Manager administrator; create any role in the system; perform any action on any target in the system, and see all areas of the Management System tab.
Defined in a Group to obtain overall performance information for one target type within the Group; though, you can have multiple summary metrics. For example, one for host, one for databases, and so on.
By default during the installation of Oracle Enterprise Manager, one super administrator account is created with the user name of SYSMAN. The SYSMAN account should be used to perform infrequent systemwide, global configuration tasks such as setting up the environment. Other administrator accounts can be created for daily administration work. The SYSMAN account is:
Owner of the Management Repository schema
Default Enterprise Manager super administrator
User name used to login to Enterprise Manager the first time
Allows a user to perform systemwide operations. For example, the VIEW ANY TARGET system privilege allows the administrator to view any target on the system, including Oracle Management Agents and Oracle Management Services.
A single component that you can monitor or configure with Enterprise Manager. Examples of a target include:
Single Oracle 10g database
Group of databases that provide your worldwide customers with product information
Oracle Application Server or an instance of Oracle HTTP Server
Web application that your customers visit to investigate or buy your products
Sun Solaris host computer, including its memory, disks, and CPU
Server load balancer switch that controls the Internet traffic for a set of Web servers
Enterprise Manager can manage all these targets. A complete list of the target types you can manage is included in Oracle Enterprise Manager Grid Control Installation and Basic Configuration.
When the Oracle Management Agent starts up after installation, automatic target discovery occurs. During discovery, the targets located on the Oracle Management Agent machine are discovered and added to Enterprise Manager to be monitored and administered. Which targets are added automatically is dependent on how the Oracle Management Agent is installed.
Contains general information about the selected target. From a target home page, you can drill down to more detailed performance information.
Allows an administrator to perform operations on a target. For example, the View target privilege allows the administrator to view properties, inventory, and monitor information about a target.
Boundary values against which monitored metric values are compared. The comparison determines whether an alert should be generated.