6 Copyright © 2006, Oracle. All rights reserved. Monitoring Grid Control

Copyright © 2006, Oracle. All rights reserved Objectives After completing this lesson, you should be able to: Monitor the availability of Grid Control components Monitor the performance of Management Server, Repository, and Agent Identify log and trace files for all Grid Control components Identify the various commands to manage Grid Control components Start and shut down the Grid Control framework Discuss backup of Oracle Management Service (OMS) and repository Monitor the EM Website Web application

Copyright © 2006, Oracle. All rights reserved Monitoring Grid Control Framework The Grid Control framework must function efficiently in order to manage and monitor the targets efficiently. When monitoring the Grid Control framework, you should: Examine management repository operations Ensure that management services are functioning properly Check management agent performance

Copyright © 2006, Oracle. All rights reserved Monitoring the Repository You can track space usage in the repository: Look for unusual trends. Ensure that space remains for continued operation.

Copyright © 2006, Oracle. All rights reserved Repository Operations You can get an overview of the status and performance of the DBMS jobs with the Repository Operations page.

Copyright © 2006, Oracle. All rights reserved Management Services The Management Services page gives you information about the health and configuration of all Management Services. You can monitor management services for: –Errors –Files pending load –Oldest file to load

Copyright © 2006, Oracle. All rights reserved Management Service Status

Copyright © 2006, Oracle. All rights reserved Management Agents

Copyright © 2006, Oracle. All rights reserved Home Directories You install the following three Oracle Home directories when you install Grid Control: Management Service home directory ( $OMS_HOME ) Management Agent home directory ( $AGENT_HOME ) Management Repository home directory ($ORACLE_HOME )

Copyright © 2006, Oracle. All rights reserved Management Service Home Directory binsysmanopmnj2eeApachewebcache config log emd bin logs OC4J_EM log Apache logs archive Management Service Home ( OMS_HOME )

Copyright © 2006, Oracle. All rights reserved Viewing OMS Log Files Individual log files are generated for each OMS subcomponent: Oracle Web Cache Oracle HTTP Server (OHS) Oracle Application Server Containers for J2EE (OC4J) Oracle Process Monitor and Notification Server (OPMN) OHS Web Cache OC4J EM OMS

Copyright © 2006, Oracle. All rights reserved

Copyright © 2006, Oracle. All rights reserved Management Repository Home Directory binsysmanhost_name_sidoc4jnetwork adminsysman config j2ee log Oracle Database 10g Home ( ORACLE_HOME ) trace log emd

Copyright © 2006, Oracle. All rights reserved Viewing Repository Log Files You can see the repository log files when you have problems with: Connectivity Availability

Copyright © 2006, Oracle. All rights reserved Management Agent Home Directory binsysman config log admin Management Agent Home ( AGENT_HOME ) emd

Copyright © 2006, Oracle. All rights reserved Viewing Agent Log Files You can see the agent log files when you have problems with: Connectivity Throughput Target discovery

Copyright © 2006, Oracle. All rights reserved Repository sqlplus lsnrctl OMS opmnctl Agent emctl AS Control emctl Component Control Utilities Controlling the Grid Control Framework OHS Web Cache OC4J EM OMS AgentsRepository

Copyright © 2006, Oracle. All rights reserved Controlling the Repository Database Listener The repository database listener is controlled by the Listener Control utility ( lsnrctl ): Start listener: $ORACLE_HOME/bin/lsnrctl start Stop listener: $ORACLE_HOME/bin/lsnrctl stop Check status: $ORACLE_HOME/bin/lsnrctl status Check services: $ORACLE_HOME/bin/lsnrctl services

Copyright © 2006, Oracle. All rights reserved Controlling the Repository Database The repository database is controlled with sqlplus : Begin a sqlplus session with sqlplus / as sysdba. Start the database with startup. Stop the database with shutdown immediate. $ sqlplus / as sysdba Connected to: Oracle Database 10g Enterprise Edition Release Production With the Partitioning, OLAP and Data Mining option

Copyright © 2006, Oracle. All rights reserved

Copyright © 2006, Oracle. All rights reserved Controlling OMS Oracle Management Service may be controlled using: Oracle Process Monitor and Notification Control ( opmnctl ) Enterprise Manager Control ( emctl ) Oracle Enterprise Manager 10g Application Server Control

Copyright © 2006, Oracle. All rights reserved opmnctl Use the Oracle Process Monitor and Notification Control utility ( opmnctl ) to: Start and stop all OMS components Start and stop individual OMS components Check the status of OMS components Few examples: $OMS_HOME/opmn/bin/opmnctl startall $OMS_HOME/opmn/bin/opmnctl stopall $OMS_HOME/opmn/bin/opmnctl startproc ias-component=OC4J $OMS_HOME/opmn/bin/opmnctl stopproc process-type=OC4J_EM $OMS_HOME/opmn/bin/opmnctl status -l

Copyright © 2006, Oracle. All rights reserved emctl Use the Enterprise Manager Control utility ( emctl ) to: Start and stop required OMS components Administer Oracle Enterprise Manager 10g Application Server Control $OMS_HOME/bin/emctl start oms $OMS_HOME/bin/emctl stop oms $OMS_HOME/bin/emctl status oms $OMS_HOME/bin/emctl start iasconsole $OMS_HOME/bin/emctl stop iasconsole

Copyright © 2006, Oracle. All rights reserved Application Server Control

Copyright © 2006, Oracle. All rights reserved Starting Application Server Control Use emctl command to start, stop, or check the status of Application Server Control. Make sure that you are in OMS_HOME before issuing the commands. $OMS_HOME/bin/emctl start iasconsole $OMS_HOME/bin/emctl stop iasconsole $OMS_HOME/bin/emctl status iasconsole

Copyright © 2006, Oracle. All rights reserved OMS Home Page

Copyright © 2006, Oracle. All rights reserved Starting, Stopping, and Restarting the OMS

Copyright © 2006, Oracle. All rights reserved Controlling Management Agent Use the Enterprise Manager Control utility ( emctl ) to: Start, stop, and monitor status Force uploads to the management repository $AGENT_HOME/bin/emctl start agent $AGENT_HOME/bin/emctl stop agent $AGENT_HOME/bin/emctl status agent $AGENT_HOME/bin/emctl upload $AGENT_HOME/bin/emctl clearstate agent

Copyright © 2006, Oracle. All rights reserved Starting the Grid Control Framework To start the Grid Control framework, perform the following steps: 1.Start the repository database listener. 2.Start the repository database. 3.Start the OMS. 4.Start the agent on the OMS/repository server. 5.Start the agents on the managed servers. Agents OHS Web Cache OC4J EM OMS Repository

Copyright © 2006, Oracle. All rights reserved Stopping the Grid Control Framework To stop the Grid Control framework, perform the following steps: 1.Stop the agents on managed servers (optional). 2.Stop the agent on the OMS/repository server. 3.Stop the OMS. 4.Stop the repository database. 5.Stop the repository database listener. OHS Web Cache OC4J EM OMS Agents Repository

Copyright © 2006, Oracle. All rights reserved Keeping Grid Control Healthy To keep your Grid Control framework healthy, perform the following tasks: Check the OMS and repository errors page and resolve the causes of all errors. Check and resolve all warnings and alerts. –Adjust thresholds when needed to prevent frequent “oscillation” of warnings and alerts. Check and resolve all metric collection errors. –Agents not configured correctly can stress Grid Control systems. Watch for monitored targets that are always listed with a down status.

Copyright © 2006, Oracle. All rights reserved Backing Up Grid Control To back up Grid Control, you must back up its three important components: Repository: Use any standard database tools for the backup. OMS: Back up the binaries and configuration files. Agents: Back up the binaries and configuration files.

Copyright © 2006, Oracle. All rights reserved Monitoring the EM Website Web Application

Copyright © 2006, Oracle. All rights reserved Summary In this lesson, you should have learned how to: Monitor the availability of Grid Control components Monitor the performance of Management Server, Repository, and Agent Identify log and trace files for all Grid Control components Identify the various commands to manage Grid Control components Start and shut down the Grid Control framework Back up OMS and repository Monitor the EM Website Web application

Copyright © 2006, Oracle. All rights reserved Practice 6 Overview: Monitoring Grid Control This practice covers the following topics: Monitoring the Repository and OMS Working with the Agent

Copyright © 2006, Oracle. All rights reserved