Chatta subito con l'assistenza
Chat con il supporto

Foglight for Oracle (Cartridge) 5.7.5.41 - 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) Reviewing Overall Activity Reviewing RAC Historic Activity Oracle Activity Drilldown Pluggable Databases Drilldown Storage Drilldown Reviewing Configuration Settings Reviewing the Alert and Error Logs Reviewing ASM Instances Reviewing Exadata-related Information
Administering Foglight for Oracle Reporting Reference Glossary

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:

•
What caused a specific activity?
•
What were the resource and load demands of today's instance activity compared with that of a previous day?
•
Is an instance imposing different load levels now than previously?
•
How do we explain the difference in a SQL performance compared with a previous period?
•
What are the differences in program characteristics over two periods that caused different performance?
•
After identifying the different resource usage, you can use compare to identify what caused this difference: Usage pattern? Different SQL behavior? Environmental problem?

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.

Reviewing Overall Activity

The Oracle Overview page provides an overall view of the RAC or instance status for the selected time range, through the views and tools listed below.

* 
NOTE: The ASM (Automatic Storage Management) and archiving components are enabled only when being used by the monitored instances. Monitoring the ASM-related data is possible only when the ASM instance is installed and configured. For details, see Using Foglight for Oracle .

Monitoring Current Activity

The Real-time Status pane provides the indicators listed below for monitoring the current activity of either the selected instance/RAC node or the entire RAC, in Whole Cluster view.

•
Sessions (no.) — displays the total number of currently running sessions, distributed to inactive sessions (that is, sessions that did not initiate an SQL call to Oracle), and active sessions.
•
CPU (%) — displays the percentage of CPU that was consumed on the Oracle host by all processes (Total) or by Oracle processes only (Oracle).
•
Memory (%) — displays the percentage of RAM that was consumed on the Oracle host by all processes (Total) or by Oracle processes only (Oracle)
•
Up Since — identifies the date and time when the instance/RAC node was last started. If the database is not running this area reads Database is down, and a popup is available, displaying the database status.
* 
IMPORTANT: In Whole Cluster view, this indicator displays data regarding the most recently started RAC node.
•
Response Time — the response time, in milliseconds, of the instance or RAC node.
* 
IMPORTANT: In Whole Cluster view, this indicator displays the maximum (slowest) response time among all of the cluster nodes.
•
Blocked Sessions (no.) — the total number of sessions waiting for a lock held by another session.
•
Avg. Virtual. Overhead — displays the percentage of CPU that is unavailable to this virtual machine because it is being utilized either by other virtual machines or by VMware itself.
* 
IMPORTANT: The virtualization overhead metric holds value only for virtual hosts running on VMware ESX servers, and had their VMware connection profile defined using the Databases Administration dashboard. For more information, see Defining the VMware Connection Profile .
Clicking the average virtualization overhead indicator displays the Virtualization Resource Utilization popup. This popup shows the CPU usage by both the virtual machine and the ESX host, as well as the memory sharing and swapping between all powered-on virtual machines on the host.

Monitoring Current Storage

The Real-time Storage pane enables monitoring of the current storage utilization by means of the following indicators:

•
Total — displays the total amount of datafile storage available (used and free), in megabytes
•
Free — displays the amount of free storage as a percentage
•
Autoextensible — indicates if at least one datafile in the database is autoextensible:
•
No — none of the datafiles in the database are autoextensible
•
Yes — at least one datafile in the database is autoextensible
•
Archive Space — if archiving is configured, displays the following indicators of storage-related information about the most critical archive destination, that is, the archive destination with shortest time to failure:
•
Cylinder — shows the amount of used archive destination memory
•
Time to Failure (hours) — indicates the estimated time to failure in hours, based upon the rate of archiving
* 
IMPORTANT: If the archive files reside on a disk that is managed by ASM, the Archive Space cylinder is disabled and the indication ASM agent is required appears. To retrieve archive data, the ASM instance should be installed and configured. For instructions, see Using Foglight for Oracle .
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione