Skip to content

Latest commit

 

History

History

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 

README.md

layout default
title DBA AWR Latch Summary | Oracle EBS SQL Report
description Summary of latch statistics such as misses and wait times for a specified snapshot time interval
keywords Oracle EBS, Oracle E-Business Suite, SQL report, Blitz Report, Diagnostic Pack, Enginatics, DBA, AWR, Latch, Summary, dba_hist_snapshot, dba_hist_latch
permalink /DBA%20AWR%20Latch%20Summary/

DBA AWR Latch Summary – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Summary of latch statistics such as misses and wait times for a specified snapshot time interval

Report Parameters

Date From, Date To, Level of Detail, Request Id (Time Restriction), Time Restriction, Diagnostic Pack enabled, Container Data

Oracle EBS Tables Used

dba_hist_snapshot, dba_hist_latch

Report Categories

Diagnostic Pack, Enginatics

Related Reports

DBA AWR Latch by Time, DBA AWR CPU vs Wait Time Summary, DBA AWR PGA History, DBA SGA+PGA Memory Configuration, DBA AWR Blocking Session Summary, DBA AWR Wait Class by Time, DBA AWR SQL Performance Summary, DBA AWR Wait Event Summary, DBA AWR System Metrics Summary

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output DBA AWR Latch Summary 26-Nov-2018 223201.xlsx
Blitz Report™ XML Import DBA_AWR_Latch_Summary.xml
Full SQL on Enginatics www.enginatics.com/reports/dba-awr-latch-summary/

Executive Summary

The DBA AWR Latch Summary report provides an aggregated view of latch statistics over a specified period. While the "Latch by Time" report shows trends, this report is useful for identifying the "Top N" latches causing the most pain overall. It summarizes misses, sleeps, and wait times to highlight the most contended memory structures.

Business Challenge

  • Top Contributors: "Which latch is responsible for 80% of our concurrency wait time?"
  • Tuning Prioritization: Deciding which area to focus on (e.g., Shared Pool vs. Buffer Cache) based on latch statistics.
  • Efficiency Analysis: High "Misses" but low "Sleeps" might indicate efficient spinning, whereas high "Sleeps" indicates severe contention.

Solution

This report aggregates latch statistics for the selected timeframe.

Key Features:

  • Gets: Number of times the latch was requested.
  • Misses: Number of times the latch was not obtained on the first try.
  • Sleeps: Number of times the process had to yield the CPU while waiting.
  • Wait Time: Total time spent waiting.

Architecture

The report queries DBA_HIST_LATCH.

Key Tables:

  • DBA_HIST_LATCH: Historical latch statistics.

Impact

  • Targeted Optimization: Focuses tuning efforts on the specific memory structures causing bottlenecks.
  • Configuration Tuning: Can suggest changes to initialization parameters (e.g., increasing SHARED_POOL_SIZE or DB_CACHE_SIZE) to relieve latch pressure.
  • Code Optimization: Helps identify application patterns (like hard parsing) that stress specific latches.

Useful Links

© 2026 Enginatics