0348-0353

Previous Table of Contents Next

Page 348

TIP

Always start the Oracle Enterprise Manager console before using any other products. Start the other products by following these steps:
1. Click a database.

2. Click the appropriate folder for the current need.

3. Right-click the object (such as a data file). This will show the pop-up menu.

4. Click the Related Tools menu option.

5. Click the appropriate tool.

Although it is possible to open the other managers without opening the console, it ends up being much more time-consuming . Every time a manager is opened separately, the user must log in to the database. With some managers, the user must also log in to the repository. Finally, some managers will not function at all until the console is running. Using the console avoids all of the extra logins and error messages.

NOTE

Right-clicking any database in the Navigator window will give the full list of managers under the Related Tools menu. This will save an extra step after the user becomes familiar with OEM.

The Map Window

The Map window allows the DBA to organize objects such as databases, listeners, and nodes into groups that may be easier to use in a spatial setting. The window is initially completely blank. A map may be created by selecting Create Map from the Map menu. (See Figure 15.4.)

After choosing a map name , the user may click Use Background Bitmap to display a bitmap in the background of the Map window. This bitmap may be a standard Oracle bitmap that includes Asia, Europe, Japan, USA, and the world. The bitmap may also be a custom bitmap created with a bitmap editor such as Microsoft Paint. After the user clicks OK, the map is displayed in the Map window. The user may drag and drop objects from the Navigator window into the Map window. (See Figure 15.5.)

Page 349

Figure 15.4.
Create a New Map
dialog box.



Figure 15.5.
The Oracle Enterprise
Manager console with a
map of the USA.

The Job Control Window

The Job Control window has three tabs. The Active Jobs tab shows which jobs have been submitted but not yet completed. The Job History tab shows jobs that have run in the past. The Job Library tab shows jobs that the user has saved to the library for future use.

Page 350

NOTE

Many jobs rely on Simple Network Management Protocol (SNMP) to function properly. Investigate SNMP settings on the database servers if jobs are submitted but never
actually run.

Clicking Create Job from the Job menu will create a new job. (See Figure 15.6.)

Figure 15.6.
The General tab of the
Create Job dialog box.

The General tab provides the name, description, and destination of the job. It also allows the job to be specified as a fixit job. A fixit job will be run only in response to a problem in the database. This particular job will perform a weekly export of the database HPSERVER.

The Tasks tab shows a list of all available actions that the job may perform. (See Figure 15.7.) This list is quite inclusive. It includes export, import, SQL*Plus, operating system commands, and more. Just about any possible task may be scheduled as a job.

The Parameters tab displays the parameters for all of the options that were picked in the Tasks tab. In the case of this particular job, the parameters for exporting from a database are displayed. (See Figure 15.8.)

The Schedule tab determines when the job is to be executed. The job may be run immediately, once in the future, or periodically. This particular job will be run every Sunday at 7:01 p.m. (See Figure 15.9.)

Page 351

Figure 15.7.
The Task tab of the
Create Job dialog box.



Figure 15.8.
The Parameters tab of
the Create Job dialog
box.



Figure 15.9.
The Schedule tab of the
Create Job dialog box.

Page 352

The Event Management Window

The Event Management window of OEM allows agents to monitor the activity of the databases. The user may set defined limits to

• Have the agent notify the user of a possible problem
• Have the agent automatically execute a fixit job

Event management can occur on the node, the listener, or the database. Table 15.2 shows all of the options for each service type.

Table 15.2. Event Management options.

Service Type	Events	Description
Node	UpDown	Node is up or down.
CPU Utilization	CPU utilization is high
CPU Load	CPU load is high
CPU Paging	Paging rate is high
Disk Full	Disk is full
Swap Full	Swap area is full
Database	Alert	New errors are in the alert file.
	User Blocks	Database users have been blocked.
	UpDown	Database is up or down.
	Probe	A new database connection cannot be made.
	Buffer Cache	Buffer cache hit ratio is low.
	Chain Row	Chained rows exist.
	Data Dictionary Cache	The data dictionary miss ratio is high.
	Disk I/O	Disk I/O is high.
	Library Cache	Library cache miss ratio is high.
	Net I/O	SQL*Net I/O rate is high.
	SysStat Table	Value of V$SYSSTAT parameter is high.
	SysStat Table Delta	Difference between V$SYSSTAT parameter and defined value.
	Response Time	Response time of user program is slow.

Page 353

Service Type	Events	Description
	Datafile Limit	Exceeds data-file limit.
	Lock Limit	Exceeds lock resource limit.
	Process Limit	Exceeds process limit.
	Session Limit	Exceeds session limit.
	User Limit	Exceeds user limit.
	Archive Full	The archive device is full.
	Chunk Small	Contiguous free space is too small.
	Dump Full	The dump destination device is full.
	Maximum Extents	Segments are reaching maximum extents.
Listener	UpDown	SQL*Net Listener is up or down.

TIP

Consider supplementing monitoring scripts with the event-management system. Scripts are run on a periodic basis. Although they are good at noticing trends or problems that give early warning, they are almost worthless for problems that arise in a short period of time. For example, a segment might only have a few extents when the scripts are run the night before. During the day, a batch job is run that loads data into the table. This table may reach maxextents in a very short period of time. The nightly scripts would not report a problem; however, the event management of OEM would notice the problem and solve it or notify the DBA immediately.

Backup Manager

The Backup Manager allows the user to perform the following tasks:

• Back up tablespaces
• Take tablespaces offline/online
• Create backup scripts
• Start up or shut down the database
• Restrict user sessions
• Perform online backups

Previous Table of Contents Next