Present day growth of Internet, Operating Systems and Industry necessitates round the clock up time of the database. Programmers / DBAs must always be aware of system failures and periodicity or exact time of failure and they must be ready with solutions to correct the problems.
Oracle Enterprise Manager (OEM) Framework is designed to solve these problems efficiently, with a comprehensive set of tools available. The Framework can be configured to manage the Database via a web based interface.
The Oracle Enterprise Management Framework is divided into these functional areas:
Managed Targets: Objects such as Databases, Application Servers, Web Servers, Applications and Oracle agents (Oracle Net listener and Connection Manager) are the objects called Managed Targets administered using OEM framework. They can be added or deleted when needed.
Management Service: A Java-based web component that is the actual interface used to monitor and control managed targets.
Oracle Management Repository A storage of configuration and monitoring information collected about the managed targets.
It comprises two tablespaces in an Oracle Database that contain information about administrators, targets, and applications that are managed within Enterprise Manager.
Oracle Enterprise Manager 10g Grid Control Enterprises that must manage many databases, application servers, web servers, and other components can use the Enterprise Manager Grid Control. The EM Grid Control is a web-based user interface that communicates with and centrally manages all the components within the Oracle enterprise. EM Grid Control can be used to monitor and administer the entire computing environment from a centralized location, including hosts, databases, listeners, application servers, HTTP servers, and web applications.
Oracle Enterprise Manager 10g Database Control
The EM Database Control is a web based component of the Enterprise Management Framework for managing Oracle Database 10g Release 2 (10.2). It allows Administrator Cluster (RAC) environment.
Application Server Control The Application Server Control is a web-based component of Enterprise Manager that monitors the Oracle Application Server 10g (9.0.4). The Application Server Control allows you to monitor and administer a single Oracle Application Server instance, a collection of Oracle Application Server instances, or Oracle Application Server Clusters.
If Oracle Enterprise Management Framework is used to administer Oracle Database(s) it
is accomplished in two ways:
-- using Oracle Enterprise Manager Grid control to centrally administer all of the databases.
-- using Oracle Enterprise Manager Database Control to manage each database individually.
In either case, stopping and starting necessary agents to use these tools is to be clearly understood.
An agent process (that runs on each Managed Target server) is to be started on each server that is to be available to the Framework.
The agent collects information about the managed target and then communicates with the central management service, which maintains the information about the managed target.
EMCTL command-line utility is used to start and stop the Oracle management agent. To start the agent, use the emctl start agent command.
Instead of using a centralised framework, each individual target database can be administered using Enterprise Manager Database Control.
To start the Database Control Agent issue the emctl start dbconsole command.
In a Unix environment, the emctl program can be found in your ORACLE_ HOME/bin directory.
To stop the Database Control agent, use the emctl stop dbconsole.
To view view the status of the agent, use the emctl status dbconsole command.
Using Database Control
After the Database Control agent is started, we are ready to use web-based tool.
Enter the following URL in your browser.
http://hostname:portnumber/em (default value for port number is 5500). Database login screen will appear. Enter user ID and password. After successful login, we can perform administrative tasks from the console.
When your database is first created, the initial login user ID is SYS, SYSTEM, or SYSMAN.
Just like we have started agent on Oracle server (emctl start agent) (and emctl start dbconsole), a server-side listener process must be started in order for clients to connect to a database through iSql*Plus.
Run the following command on the Windows server:
On Unix Server:
run the following command:
Default port number is 5560.
$ORACLE_HOME/bin/> isqlplusctl stop
Obtaining a List of Ports Used by the Oracle Components: view the portlist.ini file located in the $ORACLE_HOME/install directory on Unix or %ORACLE_HOME/install directory on Windows.
|Ultra Search HTTP port number||5620|
|iSQL*Plus HTTP port number||5560|
|Enterprise Manager Console HTTP Port (orcl)||5500|
|Enterprise Manager Agent Port (orcl)||1830|
After the process is started, iSQL*Plus can be accessed by entering the following URL in web browser (Default port number is 5560).
Login screen will appear and by entering your user ID and password, connection to Database is established.
Use of iSQL*Plus tool is similar to use of SQL*Plus.
Then we will be able to run commands and load and save scripts. Enter one or more commands in the Workspace box and click the Execute button. If you enter multiple commands in this box, each command is run in order. Output to these queries is displayed in a results panel at the bottom of the screen when the query is complete.
By clicking on History tab, the last 10 commands summary is displayed. This number (10) can be changed by clicking the Preferences icon and modifying History Size.
iSQL*Plus can be configured to allow connections to the database with SYSOPER or SYSDBA privileges.