Installing The Grid Control Oracle Enterprise Manager OEM
We need to install the Grid control by downloading the software from Oracle's web site or by using the appropriate CD. Installing Grid Control consists of two steps:
1) Installing the OEM Grid Control software on the host from which we intend to use the Grid Control console.
2) Installing the Management Agent on each of the hosts we want to monitor.
Installing the Grid Control Component :
Installing Grid Control is similar to the installing of Oracle Server software. We must make sure we have the DISPLAY variable set up properly if we're using a UNIX/Linux system
Steps in the Installation Process:
1) Log in to the host as the Oracle software owner and mount the Oracle database 10g CD. Change directory to the CD, and execute the runInstaller script.
$ ./runInstaller
2) At the Welcome window, click Next
3) Accept the default operating system(OS) group name. Click Next
4) A seperate window asking us to run the root.sh UNIX script will appear. Leave this window open, and open a new terminal window
5) Execute orainstRoot.sh as the root user in the terminal window, as shown here:
$ cd $ORACLE_BASE/oraInventory
$ su
$ ./orainstRoot.sh
$ exit
6) Once we run the orainstRoot.sh script, we have to go back to the Oracle Universal Installer window and click Continue
7) In the specify File Locations window, choose the directory for the OEM files and click Next
8) In the select a product to install window we can install the OEM Grid Control in an existing Oracle database or we can create a new database. We can also choose to install a Management Service or Management Agent from this window. Click Next.
When we choose to install the grid Control using a new database, Oracle will create a ew Oracle Database 10g database on our server. If we wnt to install using an existing Oracle database, our database must be version 9.2 or higher.
9) The Oracle Universal Installer will make the necessary prerequisite checks, after which we click Next
10) Choose a password for the default SYSMAN user and click Next
11) Select passwords for the SYS,SYSTEM and DBSNMP users in the new database and click Next
12) In the next window, we have the option of setting up the MetaLink and Proxy information. These are optional and have no bearing on the functioning of Grid Control. Once we makeur choice, click Next
13) In the Database Identification window that appears next, choose the SID and the Global Database Name for the database. Click Next
14) In the Database File location window, specify the location for all the database files and click Next
15) Review the list of components that are going to be installed in the Summary screen that appears , and click Install
16) We'll now see a series of windows indicating the progress of the installation. We'll be asked to run the root.sh script again as the root user. Log in as root user in a separate window and run the root.sh script again as a root user. Log in as a root user in a separate window and run the root.sh script. Then go back to the installation window and click OK
17) The Configuration Assistant window will show the status of the various configuration assistants, such as the Oracle Database Configuration Assistant. There can be n(n=1...any) configuration assistants in a system. After the new oracle database is created, we'll see the following message:
The Oracle Agent will now be installed on the same machine as the database that was just created. This database will then be available through Grid Control to manage its environment.
Click OK.
18) When the Setup privileges window appears, open a new terminal window and run the orainstRoot.sh script yet again. Once the script completes, go back to the installer window and click Next. The Configuration assistants window will appear again and the Agent Configuration Assistant will install the Oracle Agent.
19) We'll see an end of installation message from the Installer, along with the list a port numbers we can use to access the Grid control, the Oracle Application server that's installed as a part of the Grid Control installation, and the Oracle database that was created to host the Grid Control
20) Click Exit to end the installation
Installing and Deploying the OEM Management Agent :
Use the following steps to install the OEM Management Agent on each server we want to monitor:
1-7 ) Start the Oracle Universal Installer and perform the first seven steps as in the preceding section.
8) In the select a Product window, choose the Additional Management Agent installation type and click Next
9) Specify the name of our host server in the next page and click Next
10) click Next, after reading the security warning (regarding secure HTTP mode) and then click OK
11) Review the summary window and click Next to start the actual agent installation process
12) Once our installation completes, click Yes to exit the Oracle Universal Installer
13) Verify that our databases and hosts can be seen by the newly installed Management Agent. we can do this by logging in to the Grid Control and clicking the Target tab. We'll see all the discovered hosts. Click on any host and then click on databases. We should now be able to view all our Oracle databases that are running on that host. Once we successfully install the agents on our servers , we can use the information they collect to monitor all our oracle databases, hosts, web servers and listeners.
Grid Control Manage Enterprise OEM GRid Control Enterprise Management
The Grid Control homepage provides an overall view of the entire enterprise. Use this as our starting point when we 're evaluating the health of our database, since it provides information about the entire Oracle environment, not just the database. The home page shows us the following things :
Status :
Provides the status of the monitored Oracle targets, including the availability and open alerts for each target.
Targets include hosts, databases, web servers and listeners.
Critical Patch Advisories :
Displays a visual summary of any patch advisories and the affected Oracle homes.
Deployment Summary :
Provides a summary of our entire system configuration, including hardware and software.
Resource Center :
Provides links to the Oracle Documentation, release notes, support and the Oracle Technology Network(OTN).The Grid Control homepage contains the tabs that offer links to the following entities:
Targets :
Targets include the host servers, databases, application servers, web applications, and groups
Deployments :
The Deployments home page has sections for critical patch advisories, deployments, configuration, patching, cloning, and policies( managing policy violation)
Alerts :
This page will tell us if any of our targets are down
Jobs :
The Job activity page contains information on all scheduled, running, and finished jobs in our database.
Management system :
This page contains information about the Management service and the Management Repository. It provides details about the general health of OEM, availability, backlogs, and alerts about the OEM itself and all the targets. At the top (and the bottom) of the grid control home page we'll find additional links to the following pages:
Setup:
This setup page is similar to the setup page in the Database Control.
Preferences :
The preferences page is where we can change preferred credentials, including the password of the SYSMAN account.
Help :
This page provides details about each of the pages in the Grid Control.
Logout :
This link will log out you of the Grid control.
Monitoring Our Entire system With The Grid Control :
We can use the Grid control to monitor not only the Oracle databases, but also web applications, host performance, application servers, and database groups. The Grid control has all the features of the Database Control, as regards the management of databases;in addition, we can manage all other parts of our system.
Monitoring Web Applications:
In order to view our web applications through the Grid control, select Web Applications from the View drop-down list on the home page. We can perform the following tasks from the Web applications home page:
1) Review web application alerts: We can use the Grid Control to view alerts regarding our web applications. Whenever an application fails to perform according to a preset performance policy threshold, Grid Control will alert us. We specify the alerts when we create our web applications. In order for the Grid Control to monitor the application , we must add the target to OEM.
2) Monitor transaction performance : The Grid control will monitor our web application to see if they are conforming to availability and service-level requirements. We can monitor and track key transaction performance indicators like average page response, slowest page and the response time(in milliseconds). We can go to transaction Playback page and view the summary and breakdown of the time spent on each web page in our application.
3) Analyze Page Performance : Using Grid Control we can track the web server response time and correlate this information with the response times of URLs from various users. We can also perform end-user performance review of the slow URLs.
Monitoring Host Performance:
We can monitor host performance an track configuration changes through the grid control. We can reach the Host home page by clicking on the Targets tab and then selecting the host we want to investigate. The Host home page summarizes the availability and status of the host. From the host home page, we can navigate to the performance and configuration areas:
Performance : We can use the Grid Control to view host performance, including CPU usage, memory, disk I/O, etc. We can view current CPU load and swap utilization on our system without using operating system tools like sar and top.
Configuration : We can view the hardware and software configuration on the host. If we wish, we can perform side-by-side comparison of any two hosts on our system. This enables us to identify the differences between a development and production server. We will see the differences in operating system patches, packages, and Oracle software versions.
Monitoring Web Applications :
We can monitor the application servers in our environment by clicking the Targets tab and then clicking the Web application link. We'll see a list of all the Web Applications in our system here, and we can click on a specific application to examine its performance. In addition to monitoring our web applications, we can also monitor the web servers used by our applications, including the Oracle Application Server instances.
Managing Groups :
The Groups sub-tab under the Target tab lists all the groups defined in the Grid Control. The grid control's group capability lets us organize our databases and hosts into related groups. For example we can collect all our production databases into one group called as production databases. Groups let us run our job in all related targets with a single command. In addition, we can view all alerts and configuration policy violations in our production databases separately from the development and test databases.
We can perform the following tasks from the Groups page :
1) Add, remove and configure groups
2) Access a group's home page
3) View alerts and policy violations for a group
OEM Database express:
Oracle enterprise manager is a database tool that helps with database administration. This is a GUI. This comes as part of Oracle database 12c toolset and can be installed as part of database install. Lets look at some interesting facts about Oracle enterprise manger database express in Oracle 12c
1) By checking the option to install this can be installed as using database configuration assistant
2) Default port taken by enterprise manager is 5500
3) This portal can be accessed via http://:5500/em
4) This tool helps us manage all the database activities. However we can’t perform tasks like STARTUP as this depends on a database in open mode
5) XMLDB is a mandate to make use of this tool. Port number can be changed using dbms_xdb_config.sethttpsport();
6) This is not for cloud control management and that happens using enterprise manager cloud control
