Chat now with support
Chat with Support

Foglight for Oracle (Cartridge) - User Guide

Installing and Configuring Agents Using Foglight for Oracle
Viewing the Databases Dashboard Assigning Instances to Users Selecting an Instance to Monitor Foglight for Oracle Overview Dashboard Overview view Advisories view SQL Performance Investigator (SQL PI) Oracle Activity Drilldown Pluggable Databases Drilldown Storage Drilldown Reviewing Configuration Settings Reviewing the Alert Log Reviewing Monitored Data Guard Environments Reviewing ASM Instances Reviewing Exadata-related Information
Administering Foglight for Oracle Reporting Reference Glossary

Viewing Execution Plans

This view presents the execution plan of a selected SQL and the cost of it. A Historical execution plan can be generated and will present any two views of the execution plan.

There are two ways to access the Execution Plan History dialog:

The execution plan dashboard displays the following content.

Resolving Date — Displays all the execution date and time of the selected statement.

Type — Displays the type of the execution plan.

Plan Hash Value — Displays the plan hash value of the execution plan

The execution plan is contains 3 tabs:

By clicking the Generate Plan button the execution plan is generated and can be viewed. By clicking on the Compare Plan button a pop up will appear that allows comparing all available execution plans of the selected SQL statement.

Comparing Performance

Use the SQL PI Compare where differences in period activity illustrate underlying performance and monitoring issues. It helps you determine whether a comparison occurrence is an isolated incident or a sign of a potentially significant performance problem.

Compare can be access from the Performance tree.

The comparison can be of whole instances or selected dimension breakdowns (such as user or SQL). Use Compare to address questions such as:

The upper panes graphically displays the Workload or any other selected resource.

The middle Activity section displays the dimensions which were significant elements of the difference. Expanding the individual lines displays the dimension members which caused the difference and the composing metrics whose differences exceed the specified threshold.

Use the set of performance related metrics (defined by the chosen resource) to help you explain the difference in resource consumption; for example, a rise in I/O Wait might be explained by a rise in the quantity of physical reads.

Use the Comparison Parameters section in order to enter all the desired information for the cooperation. For example, time range, instance, dimension, time frames, resource.

Oracle Activity Drilldown

Use the Oracle Activity drilldown to carry out the operations described in the following topics:

Viewing the Foglight for Oracle Real-time Summary Page

Viewing the Foglight for Oracle Real-time Summary Page

The following image displays the main elements of the Foglight for Oracle real-time summary page. The table that follows the image identifies each element, and provides a link to display more information, corresponding to the logical dataflow within Foglight for Oracle Instance Homepage.

The main groups (panes) of gathered icons and gauges, which represent the main activity areas in the Oracle connection process, are as follows:

Components representing instance data flow — the main activity area in the Foglight for Oracle Instance Homepage includes several panes and flows that represent the data flow in the Oracle operation. The dataflow is represented in a top-down design, that is, from the session to the physical disk storage.

Use the Instance identification indicators to identify the instance, its type and its operation period.

These indicators are:

The indicators included in the Instance pane provide various details about the instance. All of the indicators display real-time behavior, color-coded for severity.

The Sessions pane monitors all session types, that is: system, user, and Oracle sessions. Use this pane to view the response time compared with the number of sessions and the instance’s level of activity. A high response time value may result from a long queue, that is: an overly high percentage of active users.

Long queues can indicate one of the following issues:

The Sessions pane displays the total number of sessions, distributed according to the following distinctions:

The parameters in this pane lead to the Activity > Sessions panel. For details, see Viewing Detailed Sessions Data .

The Client applications represented graphically in the Sessions pane communicate with Oracle by sending and receiving network packets and by submitting SQL statements for execution by Oracle. The flows, described in the following table, help indicate performance issues if their values are too low.

The rate per second of calls (both user and recursive) that executed SQL statements.

The rate at which network packets are being received by Oracle from Client applications.

When this icon’s color is yellow, clicking it displays text that describes the deviations that triggered this display, along with a representation of the rate at which Oracle is encountering network packet errors.

The rate at which network packets are being sent from Oracle to Client applications.

When this icon’s color is yellow, clicking it displays text that describes the deviations that triggered this display, along with a representation of the rate at which Oracle is encountering network packet errors.

Use the Data Guard section for monitoring Oracle Data Guard on primary databases. This section displays the gap between the last archive log on the primary database and last applied archive log on the standby database.

Oracle Data Guard can be configured as either physical or logical standby. For details about the preparations required for monitoring each of these setups, see Monitoring the Data Guard physical standby and Working with logical standby (SQL Apply) .

As Oracle Data Guard supports physical standby databases that use Redo Apply technology, use this section to monitor the rate of applying redo log files on standby database instance.

Click Verify Connectivity

The Workload chart displays the workload of the average active sessions, plotted over time.

The workload can be plotted as either:

To display the wait events breakdown, click the arrow to the right of the Breakdown link.

The Process Activity pane enables the monitoring of the processes ran by the Oracle instance, using performance indicators such as the total number of blocked processes and the rate per second of parses that are carried out during the most recent sample.

The Process Activity pane displays the following parameters.

The number of statements executed during the most recent sample.

The average number of blocked processes that were collected during the specified time range.

Blocked processes are processes that are waiting for another process to release a resource that the process is currently locking. Such processes can sometimes result in bottlenecks.

The Blocked Process indicator changes its color when one or more processes become blocked.

Total number of parse calls. This figure is the total of both hard parse calls (calls that require loading the SQL source code into RAM for parsing) and soft parse calls.

The number of currently running transactions.

For further details, see Reviewing Instance Usability .

To communicate with the Oracle memory, the Oracle processes use logical reads and soft and hard parses, represented as flows in the homepage.

The Memory Activity session provides a view on the Oracle instance’s memory utilization, as described in the following table.

Total (MB)

The actual size currently allocated to the System Global Area (SGA) memory.

Buffer Cache (MB)


The amount of memory currently allocated to the buffer cache. The buffer cache, which is used for caching frequently accessed data blocks, is normally the largest memory cache used by Oracle.

Shared Pool (MB)

The size of the shared pool. The shared pool caches SQL statements, PL/SQL programs, object definitions, and session memory for MTS sessions. Performance can improve when the shared pool is sized properly, thereby avoiding re-parsing and reloading.

Buffer Cache Hit (%)

The percentage of block requests, which found the block in the buffer cache, out of the entire block requests (including requests that required disk reads).


The effectiveness of the library cache, computed by comparing the number of queries submitted to Oracle server for execution, which found the parsed execution plan in the library cache (soft parsing), with the entire number of queries submitted during the specified time range (including queries that required the parsing of a new statement, also known as “hard parsing”).

Total (MB)

The actual size currently allocated to the Program Global Area (PGA) memory.

PGA Hit (%)

The percentage PGA cache hit ratio.

When the value of this metric is 100%, it indicates that all work areas executed by the system processed the entire input data using exclusively the PGA memory, thereby making optimal use of this memory. Any lower value indicates that at least one work area required one or more extra passes over the input data.

The Storage pane contains the components listed below, which display storage status. The information shown in this pane is aggregated to the RAC level.

If archiving is configured, the following indicators display storage-related information about the most critical archive destination, that is: the archive destination with shortest time to failure.

This section contains the following indicators:

If storage is managed using Automatic Storage Management (ASM), and the ASM instance is installed and configured, the following indicators display storage-related information about ASM:

The Disk Activity section displays the following indicators:

The real-time summary page contains flows and graphic images that are used for tracking physical I/O activity, as listed below.

All of the indicators display real-time behavior, color-coded for severity. Clicking each indicator displays a popup, which shows the metric’s value, plotted over time.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating