Chat now with support
Chat with Support

Foglight for Oracle (Cartridge) 5.9.3.10 - 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

Parallel

The Parallel collection provides information about the instance’s parallel executions.

Oracle

Realtime Collection

20

Online

60

Offline

300

Active Parallel Sessions (11i)

Number of active parallel sessions

Active Serial Sessions (11i)

Number of active sessions that were serialized

DDL Statements Parallelized

Number of DDL statements that were executed in parallel

DML Statements Parallelized

Number of DML statements that were executed in parallel

Parallel operations Downgraded

Total number of times parallel execution was requested but execution was downgraded

Parallel Operations Downgraded 1 to 25 Pct

Number of times parallel execution was requested but execution was downgraded up to 25% due to insufficient parallel execution servers

Parallel Operations Downgraded 25 to 50 Pct

Number of times parallel execution was requested but execution was downgraded 25% or more as a result of insufficient parallel execution servers

Parallel Operations Downgraded 50 to 75 Pct

Number of times parallel execution was requested but execution was downgraded 50% or more as a result of insufficient parallel execution servers

Parallel Operations Downgraded 75 to 99 Pct

Number of times parallel execution was requested but execution was downgraded 75% or more as a result of insufficient parallel execution servers

Parallel Operations Downgraded to Serial

Number of times parallel execution was requested but execution was serial as a result of insufficient parallel execution servers

Parallel Operations not Downgraded

Number of times parallel execution was executed at the requested degree of parallelism

Parallel QC (11i)

The number of parallel query coordinators

Parallel Slaves (11i)

The number of parallel slaves

PQ Servers Busy

The number of servers that were simultaneously executing SQL queries and DML statements.

PQ Servers Busy Percent

The percent of busy parallel servers within the total number of parallel servers

PQ Servers Idle

The number of currently idle parallel servers

PQ Servers Limit

The maximum allowed number of parallel servers

Queries Parallelized

Number of SELECT statements executed in parallel

PGA Statistics

The PGA Statistics collection collects information about the use of the PGA memory.

Oracle

Realtime Collection

20

Online

60

Offline

300

PGA Aggregate Target

The value of the PGA Aggregate Target parameter in bytes.

The pga_aggregate_target parameter, which was introduced in Oracle 11g, defines the total amount of memory available in Oracle for allocation to the PGA memory structure.

If the value of this parameter is set correctly, all work areas executed by the system since start-up are processed exclusively in the PGA memory, requiring no extra passes. In such a case, the PGA hit percent’s value is 100%, and Oracle does not need to allocate extra memory to the PGA. However, when this value is set too small, the hit percent’s value decreases, and Oracle may need to perform one or more extra memory allocations.

PGA Hit Percent

The PGA cache hit ratio (as a percentage).

When the value of this metric is 100%, it indicates that all work areas executed by the system processed the entire input data exclusively via 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.

PGA Overallocation Count

The number of extra PGA memory allocations that were carried out during the specified time range.

Over-allocating PGA memory can happen if the value of the dynamic initialization parameter, PGA_AGGREGATE_TARGET, which is set to all server processes, is too small to allow executing all work area workload (operations) exclusively in the PGA memory. Such a scenario requires Oracle to allocate extra PGA memory.

Ideally, the PGA cache hit ratio should be close to 100%, resulting in an extremely small number (close to zero) of PGA overallocations. High values of the PGA Overallocation Count metric indicate the need to increase the value of PGA_AGGREGATE_TARGET.

Pluggable Databases Information

This collection contains general information about pluggable databases.

Oracle

Realtime Collection

3600

Online

3600

Offline

3600

PDB ID

The identifier used for the pluggable database.

PDB

The name of the pluggable database.

Cloned From PDB Name

Indicates from which pluggable database the selected pluggable database is cloned.

Created Time

The time when the pluggable database was created.

Share

The portion of the system's CPU resources that is allocated to the pluggable database.

Pluggable Databases State

This collection contains the status, state, and startup time for pluggable databases.

Oracle

Realtime Collection

300

Online

900

Offline

900

PDB ID

The identifier used for the pluggable database.

PDB

The name of the pluggable database.

PDB Availability

Status of the pluggable database, expressed as a percentage.

Open Mode

State of the pluggable database.

Open Time

Startup time of the pluggable database.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating